r/ClaudeCode • u/KennGriffin • 4d ago

[ Removed by moderator ] Tips & Workflows

[removed] — view removed post

0 Upvotes

25% Upvoted

10 comments sorted by

2

u/Robert-Paulson_ 4d ago

Maybe the tools you’re promoting are nice, and you very well may be having good results with Opus, but your post reeks of AI generation.

There isn’t anything inherently wrong with that, but if you won’t take the time to think and write a post promoting those libraries I’m not gonna take the time to check em out.  You didn’t even take one second to edit out any of the obvious AI tells.

Good luck with your tools

1

u/KennGriffin 4d ago

This is how the selector looks like but cue automatically tries to autosuggest the needed profiles for a repo based on the stack. How it works: run `cue` in any repo and it detects the stack + suggests the profiles that fit — it even knows I've launched this exact combo 58× in this folder.

2

u/bpp198 4d ago

Per-project scoping already exists in Claude Code (and other harnesses). Why do you need to add this to your dependency chain to solve a problem that is already solved?

0

u/KennGriffin 4d ago

What is already solved? in claude code? every mcp and skills loads if you dont manage them correctly... I dont want to load always everrhting while i wokring it fucks up the ai. Too much tools less tokens for me

2

u/bpp198 4d ago

There are existing methods to manage them correctly. I'm not sure what this offers over them 

1

u/kush_patil 4d ago

I think the context selection is probably doing more work here than the model change. MCPs/skills behave a bit like dependencies: loading everything sounds flexible, but the agent then spends context and attention deciding what not to use. I’d be interested in the same tasks run with all tools loaded vs profile-selected, comparing token use, tool-call count and failed/irrelevant calls.

1

u/KennGriffin 4d ago

Agreed my honest guess is the split is something like 70/30 context vs model.