Test Driven Development
addyosmani/agent-skillsWrite a failing test before you write any code. This is the heart of test-driven development. The test proves what the code should do. Then you write the minimum code to make it pass. This way every line of code is verified and safe.
When a bug appears, do not fix it right away. First write a test that shows the bug exists. Watch it fail. Then fix the code until the test passes. This proves the bug is gone and stops it from coming back.
Good tests are a superpower. They let you change code with confidence. They catch mistakes early. They make your software reliable and easy to improve.
Add Test Driven Development skill to your workflow
Global
mkdir -p ~/.claude/skills/test-driven-developmentProject
mkdir -p .claude/skills/test-driven-developmentSource Repository
More Testing & QA Claude Code Skills
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