Commit
Commit the working tree with a repo-appropriate, value-communicating message, then scan the session for compound-worthy learnings.
Tickets
Break a spec, plan, or the current conversation into tracer-bullet ticket files alongside the spec, each declaring its blocking edges.
Teach
Teach the user a new skill or concept, within this workspace.
Improve Codebase Architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Simplify
Optional pre-review quality pass — behavior-preserving fixes for reuse, dead weight, altitude, and clarity. Bug hunting is /code-review's job.
Grill Me
Grill the user relentlessly about a plan, decision, or idea.
Compound Refresh
Garbage-collect the knowledge stores — audit docs/solutions/ and AGENTS.md against the current code.
General Code Style
Load before writing or editing any source file, in any language, the moment a task will create or modify code and before the first edit. Covers line breaks, the 100-character line limit, comments, and docblocks. The trigger is writing; a session that only reads code leaves it unloaded.
Compound
Capture this session's durable learnings and route each to the right knowledge store, every write user-gated. Use at loop end when the commit tail prompts a session scan, when diagnosing-bugs closes out a fix, or when the user wants to capture, remember, or write down a learning, convention, gotcha, or preference.
Typescript Code Style
Load before writing or editing any TypeScript or JavaScript file (.ts, .tsx, .js, .jsx), the moment a task will create or modify such code and before the first edit. Covers strictness, style, nullability, immutability, and assertion-based error handling. The trigger is writing; a session that only reads code leaves it unloaded.
Codebase Design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Resolving Merge Conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
Writing Great Skills
Load before writing or editing any file an agent will load and act on — a skill (SKILL.md), an AGENTS.md or CLAUDE.md, or a rules file. The vocabulary and principles that make those files predictable. A session that only reads them leaves this unloaded.
Handoff
Compact the conversation into a handoff document a fresh session can resume from.
Implement
Implement a spec or a single ticket, driving TDD at the seams agreed in the spec.
Code Review
The review gate — check the changes since a fixed point against the spec and the project's standards, in parallel subagents.
Diagnosing Bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Spec
Synthesize the current conversation into a spec at docs/specs/<feature>.md, test seams included.
Cs Code Style
Load before writing or editing any C# file (.cs), the moment a task will create or modify C# code and before the first edit. Covers language level, member declaration style, type choice, and naming. The trigger is writing; a session that only reads code leaves it unloaded.
Prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, explore what a UI should look like, or when a decision in a grill-me interview needs empirical evidence.