MANDATORY for any work on Go files (*.go). Load this before editing, reviewing, or creating any *.go file. Go coding conventions and style guide covering naming, error handling, testing, HTTP handlers, caching, concurrency, and observability.
Rewrite text to be more concise, clear, and direct without losing critical information. Inventories load-bearing details first, rewrites, then audits the rewrite to verify nothing essential was dropped — for a plan, technical guide, agent instructions, or any…
Write or improve technical documentation. Applies documentation best practices: brevity, focusing on why and what rather than how, simple visualizations, modularization, and decoupling from volatile code. Use when writing new documentation from scratch, or…
Code review using specialized subagents. Analyzes behavior and tests, security, reliability, and maintainability. Use when reviewing a remote PR or local code, including unpushed/uncommitted changes. Pass --plan or --plan=<path> to check the diff against an…
Create git commits with intelligent file grouping. Use when committing changes or drafting a commit message.
Turn the plan already worked out this session into a mechanical, TDD-shaped task list a cheaper agent can execute without exploring — verbatim tests, verbatim code, and a runnable check per task. Writes to docs/tasks/.
Surface systemic patterns from an investigation as codified conventions, anti-patterns, or skill improvements.
Continue working through a project plan. Finds the next actionable slice and implements every task in it.