skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Testing & QA / TDD Skill by @mattpocock
The skill is the skills/engineering/tdd folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Test-driven development.
Test-driven development with attention to what makes a good test, where to place seams, common anti-patterns and the rules of the red-green-refactor loop. It suits building features or fixing bugs test-first, and integration tests.
The original SKILL.md is organised into these sections:
Written and maintained by @mattpocock. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# Test-Driven Development 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. ## What a good test is 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](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines. ## Seams: where tests go …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.