Code development follows a test-first approach called test-driven development or TDD. You always write the tests before the actual code. This skill enforces that rule to make sure every feature, bug fix, or refactor has thorough tests.
The process requires 80% or higher coverage across unit tests, integration tests, and end-to-end tests. It also creates Git checkpoints after each stage so you can track progress. A plan file can give you the starting point, but the skill checks it for safety before using it.
This workflow helps you build reliable software with fewer bugs. It works for new features, bug fixes, refactoring, and adding API endpoints. Every piece of code is backed by proof that it works correctly.
Global
mkdir -p ~/.claude/skills/tdd-workflowProject
mkdir -p .claude/skills/tdd-workflowSource 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
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
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
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