A green build is the weakest 'done' - and your agent's first choice.
Write the exact verification step into the feature spec your agent loads, so 'done' means the test passed - not that the code compiled.
#slash-commands
12 posts tagged #slash-commands.
When you know where the context lives, stop letting the agent guess.
Agent-driven file discovery burns turns and fills the window with wrong guesses. A parameterized priming command loads exactly the right files in one shot.
Your 600-line rules file is teaching the agent to ignore you.
A single giant root rules file dilutes the agent's attention. Split context into a broad root plus directory-scoped files it loads by what it's touching.
Three control axes are sitting in the MCP spec. Most teams use one.
An MCP server exposes resources, tools, and prompts - context the app pulls, actions the model takes, workflows the user invokes. Most teams wire only one.
Stop describing your work to the agent. Hand it the diff.
Asking an agent to review what you say you did grades your spin, not your code. A small MCP server that reads the live diff grades reality instead.
If you can't reproduce the agent's failure, your fix is a guess.
Turn each reported agent failure into a committed synthetic scenario, then replay it headlessly on every change. The bug becomes a guardrail, not a patch.
If you can describe your workflow, it isn't a workflow - it's a habit.
The correction you keep re-typing into the chat is a missing command. Fold the recurring ritual into one parameterized verb backed by a rules file.
An agent watching its context fill rushes the ending. Take the wheel.
When the window fills, agents cut corners and auto-compaction throws away the wrong things. Author a handoff file, eyeball it, restart in a session you control.
The best prompt your team writes is the one nobody writes twice.
Ship your team's recurring workflows as server-side MCP prompts that pre-load their own data. A teammate types a slash command and the context is attached.
Your local review and CI gate are one check. Stop maintaining two.
Build your review as a headless command with a tool allowlist, and the check you run by hand becomes the gate on every pull request. One rule, two surfaces.
An Agent That Can't Forget Is Worse Than One With No Memory
A rules file is write-once and rots; auto-memory saves corrections on its own judgment. Add the human-gated layer between them so corrections compound.
A Skill That Writes Your Skills
Your debugging ability isn't intelligence, it's a procedure - and procedures are exactly what you write down once and hand to an agent. Start with a meta-skill.