Test Driven Development
neolabhq/context-engineering-kitWrite a test before writing any code. Watch it fail. Then write just enough code to make it pass. This is called test-driven development or TDD. It helps you build software that works correctly from the start.
By seeing the test fail first, you know the test is checking the right thing. You never add code without a failing test. This rule keeps your code focused and your tests meaningful.
There are three steps in TDD. First you write a failing test. Then you write the simplest code to pass it. Finally you clean up your code without changing what it does. Repeat this cycle for every small change.
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