@mattpocockuk I have a set of skills to work on a single plan document so I just need /clear. Other agents can instantly start working on the plan doc.
@sarahwooders Because MCP is compact. It can explain what the interface do and give an exact validator altogether. Otherwise, you have to iterate how the skills written, how API throws an error so agent can trouble shoot by itself. I'd say, MCP first and replace API or CLI with a proper skill.
Screw loop engineering, screw Claude tag. Been confronting low quality code quite often since Claude start using other GPUs. Low quality is totally fine for me. I just hate the approach, "fire and forget". They should encourage review AI's outputs more easily rather than hiding.
People should control the context when they use AI, but most don't. They just spray and pray, firing off prompts until one happens to hit the target. I guess even a broken clock is right twice a day. But what a waste of water and electricity. I guess that's how the world breaks.
@ben_sage I have released an app for it today if you're interested... It works for me for 4 months since I made its prototype.
https://t.co/w1qfPCBLi3
It heavily rely on my issue tracking app though, but it is OSS so you can grasp the gist if you want to hack it your self.
Released an OSS app for ai coding with Claude Code but not for vibe coding. No more delusion, no more cognitive overload.
APP: https://t.co/ST1w9vEobb
Github: https://t.co/lwRIZe3QBD
#claude#claudecode
The custom context generation is insanely working well. I can just clear context anytime I want. Still agents know where they are and what they need to do next immediately in every fresh session.
Working on 2 projects, using 3 session concurrently. Still barely using 30% of daily token limit of Claude's $100 plan. Refactoring code / Context management FTW.
People should not use /compact of Claude Code.
You must control how to summarize your context. /compact doesn't know what should be summarized and what should be discarded.