Dev Rc

Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.

Look up how Claude Code itself works — hooks, skills, subagents, MCP, plugins, settings — from the official docs, so answers come from the c...

Design better agents, skills and hooks for Claude Code, checking the current spec instead of guessing at fields.

Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.

Close out a session — summarise what changed, capture what was learned, and prepare the commit.

Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.

Run the project's own tests, linter, type checker and build, and report what actually failed.

Audit the code for vulnerabilities, leaked secrets and risky dependencies before it ships.

Save a project fact, decision or gotcha so your next session already knows it.

Hand off an unfinished session to the next one — what's done, what's next, what's blocked.

Navigate your projects. Get context, paths, status. Use when needing project overview or finding specific work.

Write the spec before the code, then check the built thing against it — so agents build what was agreed, not what they invented.

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests,...

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold e...

Use when you need to resolve an in-progress git merge/rebase conflict.

A relentless interview that asks every frontier question at once, round by round.