Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Test-Driven Development methodology and patterns. Triggers on: "tdd", "test first", "write tests", "failing test", "red green refactor", "test driven", "test before", "coverage", "unit test", "feature test", "widget test". Provides TDD patterns for Laravel (PHPUnit/Pest), Flutter, and Vue (Vitest/Jest).
npx claudepluginhub anilcancakir/claude-code-plugins --plugin implementation-plannerHow this skill is triggered — by the user, by Claude, or both
Slash command
/implementation-planner:skills/tddThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guidelines for effective Test-Driven Development.
Guides implementing Test-Driven Development (TDD) with RED-GREEN-REFACTOR cycle, property-based testing, and mutation testing across any language. Includes when to apply and anti-patterns.
Guides the RED-GREEN-REFACTOR cycle for test-driven development, including AAA pattern, test prioritization, and anti-patterns. Useful when writing tests before code or implementing new features.
Share bugs, ideas, or general feedback.
Guidelines for effective Test-Driven Development.
"Write a failing test before you write the code that makes it pass."
- Kent Beck
┌─────────┐
│ RED │ Write failing test
└────┬────┘
│
┌────▼────┐
│ GREEN │ Write minimal code to pass
└────┬────┘
│
┌────▼────┐
│REFACTOR │ Clean up, keep tests green
└────┬────┘
│
└──────► Repeat
Write a test that FAILS because the code does not exist yet.
Something is wrong:
Investigate before proceeding.
Write the MINIMUM code to make the test pass.
"Make it work, make it right, make it fast." (We're in "make it work" phase)
Improve code quality while keeping tests green.
| Type | Tests | Speed | Confidence |
|---|---|---|---|
| Unit | Single class/function | Fast | Low |
| Integration | Multiple components | Medium | Medium |
| Feature/E2E | Full flow | Slow | High |
/\
/ \ E2E Tests (few)
/----\
/ \ Integration Tests (some)
/--------\
/ \ Unit Tests (many)
/____________\
| Area | Minimum | Target |
|---|---|---|
| Business Logic | 90% | 100% |
| Services | 85% | 95% |
| Controllers | 80% | 90% |
| UI Components | 70% | 85% |
Writing tests after implementation - you lose the design benefits of TDD.
Testing HOW code works instead of WHAT it does.
Mocking everything - you're testing your mocks, not your code.
Tests that test too much - hard to debug when they fail.
Tests that sometimes pass, sometimes fail - erode trust in test suite.