tdd
Installation
SKILL.md
Test-Driven Development
Build one behaviour at a time: a failing test, the least code that passes it, then proof that the test can fail. Never write the tests in bulk. A batch of tests describes behaviour you imagine, not behaviour you have seen.
1. Read the project's test rules
Read the coding standard and the review checklist (docs/coding-standard/ and
docs/code-review-checklist/, or single files such as CODING_STANDARD.md,
CODING_STANDARDS.md, and CODE_REVIEW_CHECKLIST.md in an older project), and CLAUDE.md or AGENTS.md,
if they exist. Read two or three existing tests to learn the runner, the file
layout, and the naming. The project's rules win. The defaults in step 4 apply
only where the project says nothing.