Write your tests before you write your code. That is the core idea behind test-driven development. This workflow helps you follow that rule every time.
You will create unit tests, integration tests, and end-to-end tests. The goal is at least 80% coverage. Every bug fix or new feature starts with a failing test.
A plan file can guide your work. The skill checks for safety and keeps a record of your progress. You will also create Git checkpoints after each step.
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