12 posts tagged #slash-commands.
Write the exact verification step into the feature spec your agent loads, so 'done' means the test passed and the result is on the table — not that the code compiled.
Agent-driven file discovery burns turns and fills the window with wrong guesses. A parameterized priming command loads exactly the right files in one deterministic shot — reserve probabilistic search for when you genuinely don't know where to look.
A single giant root rules file dilutes the agent's attention. Split persistent context into a broad root plus directory-scoped files the agent loads by what it's touching — and push task-specific instructions into commands.
An MCP server exposes resources, tools, and prompts — context the app pulls, actions the model takes, workflows the user invokes. Wiring them to the right controller is how the agent reads your conventions instead of guessing them.
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 and carries its own rubric grades reality instead.
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, and the workflow stops varying with your mood.
Turn each reported agent failure into a committed synthetic scenario, then replay it headlessly on every change. The bug becomes a permanent guardrail instead of a one-time patch.
When the window fills, agents cut corners and auto-compaction throws away the wrong things. Author a handoff file, eyeball it, and restart in a clean session you control.
Build your review as a headless command with an explicit tool allowlist, and the exact check you run by hand becomes the exact gate that runs on every pull request. One definition of 'acceptable,' two surfaces.
Ship your team's recurring workflows as server-side MCP prompts that pre-load their own data as embedded resources. A teammate types a slash command, fills one argument, and gets an expert prompt with the context already attached.
A rules file is write-once and rots; auto-memory saves corrections but on its own judgment, in its own store. Add the human-gated curation layer the vendors leave open: a command that counts corrections and proposes durable edits, a hook that resolves conflicts, so corrections compound instead of contradicting.
Your debugging ability isn't intelligence, it's a procedure — and procedures are exactly what you can write down once and hand to an agent. Bootstrap the whole library with a meta-skill.