Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Security grade of this SKILL.md: SAFE · how we grade
How to install tdd
npx skills add mattpocock/skills --skill tdd -a claude-code
The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.
What the SKILL.md says
TDD is the red → green loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, the anti-patterns, and the rules of the loop. Every section applies on every cycle: consult them before and during the loop, not after. When exploring the codebase, read GLOSSARY.md (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching. Tests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. A good test reads like a specification: "user can checkout with valid cart" tells you exactly what capability exists, and it survives refactors because it doesn't care about internal structure. See tests.md for examples and mocking.md for mocking guidelines.
Other skills in mattpocock/skills
ask-mattAsk which skill or flow fits your situation. A router over the skills in this repo.
code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's doc…
codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportuniti…
diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throw…
domain-modelingBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or edi…
git-guardrails-claude-codeSet up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wa…
grill-meA relentless interview to sharpen a plan or design.
grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
grillingGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' tri…
handoffCompact the current conversation into a handoff document for another agent to pick up.
implementImplement a piece of work based on a spec or set of tickets.
implement-specImplement the result of /to-spec and /to-tickets in code.
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
migrate-to-shoehornMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests…
prototypeBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right…
researchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants…
scaffold-exercisesCreate exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold…
setup-matt-pocock-skillsConfigure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before f…
setup-pre-commitSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-com…