Test-driven development is a way to write code where you start with a test first. You write a test that shows what you want the code to do. Then you watch it fail. Then you write the smallest amount of code to make it pass. This simple cycle helps you catch mistakes early and build confidence in your work.
Many developers skip tests to save time. But that often leads to bugs and harder fixes later. With test-driven development you always have a safety net. Your tests prove your code works and they stay around to catch future problems. Seeing a test fail first is the key because it shows your test is actually checking something real.
This skill is for anyone who writes code. It works for new features, bug fixes, and even cleanup. Use it every time you change existing code or add something new. The only exceptions are one-time prototypes and generated code. Stick to the cycle of red, green, refactor and your code will be more reliable and easier to change.
Global
mkdir -p ~/.claude/skills/test-driven-developmentProject
mkdir -p .claude/skills/test-driven-developmentSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step