tdd

Set up Claude Code permission rules that make dangerous git commands (push, reset --hard, clean, branch -D, checkout ., restore .) ask the user before they run.

Write straight, succinct prose with no contrasts, no header sentences, no colons/semicolons/em-dashes, no jargon, plain noun headers, and one line per…

Write the simplest code that solves the problem, and optimize only after a measurement says so.

A way of writing code where invalid data cannot exist past the point it enters, every change goes back through the checks, and every failure is loud, early…

Grill the user, then write a reviewed implementation plan to a gitignored file at the repo root.

Build a throwaway prototype to answer a design question.

Shared vocabulary for designing deep modules.

Build and sharpen a project's domain model.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding…

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker…

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

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