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.
Engineering Blog
Technical insights into multi-agent orchestration, local protocols, and
developer-centric terminal workflows.
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.
You already have labeled data. It's the transcripts you throw away.
Every failed agent session is a labeled example of where your context falls short. Capture them, cluster them, and fix the top category once in your rules file.
A Second Opinion It Didn't Write
An agent reviewing its own plan shares its blind spots. Wire a different vendor's model in as a gate, and a fail verdict re-engages planning before any code.
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.
By the time you review the diff, the destructive call already ran.
Reviewing irreversible actions after the fact is too late. Split tools by reversibility, force a plan, and gate the destructive step behind a human interrupt.
Build the Glossary the Agent Wrote
Vague prompting isn't a skill gap you fix with longer prompts. It's a missing shared vocabulary - and the fix is a committed glossary, not a personal habit.
Cache the Explore
The codebase is your strongest steering signal - stronger than your prompt or your rules. Pay the exploration cost once, freeze it, and feed it to every run.
Commission the Skill, Don't Write It
You don't author a skill from a blank page. You send a subagent to research the problem once, and the research becomes the skill - a build artifact.