Test-driven development is a simple way to build software. You write a test before you write any code. The test should fail at first. Then you write just enough code to make it pass. This keeps your code clean and works as expected.
This method is for anyone who writes code. It helps with new features, fixing bugs, and cleaning up old code. You always start with a failing test. If you skip this step, you might miss something important.
The whole process is called Red-Green-Refactor. First you write a failing test. Then you see it fail. Then you write the smallest amount of code to pass it. Finally you clean up the code. This cycle repeats for every small 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
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots