Test Driven Development
sickn33/antigravity-awesome-skillsWrite the test first. Watch it fail. Then write just enough code to make it pass. That is the heart of Test-Driven Development.
This method helps you build better software. You know your tests are correct because you saw them fail. Then you make them pass. It prevents bugs and keeps your code clean.
Follow the Red-Green-Refactor cycle. Red means write a failing test. Green means write minimal code. Refactor means clean up. Repeat for every new feature or bug fix.
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