What problem does it solve? Writing code before tests leads to unverified behavior, biased tests written after the fact, and regressions that slip into production. This Skill enforces a strict test-driven development discipline so every feature and bugfix is proven by a failing test before any implementation code exists. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the full TDD cycle with mandatory verification steps, including watching each test fail for the right reason before writing minimal code to pass. - Anti-Rationalization Guardrails: Catalogs common excuses for skipping TDD (such as "I'll test after" or "too simple to test") and explains why each one fails, keeping the workflow honest. - Testing Anti-Pattern References: Companion references cover testing mock behavior, test-only methods in production classes, incomplete mocks, and mocking without understanding dependencies. - Use Case: When fixing a bug where an empty email is accepted, write a failing test asserting the rejection, watch it fail, implement the minimal validation, verify it passes, then refactor while keeping tests green. ## Quick Start Use the test-driven-development skill to implement this feature by writing a failing test first, then the minimal code to make it pass.
