What problem does it solve? Code written before tests often ships with unverified behavior, and tests written after implementation pass immediately without proving they actually catch bugs. This Skill enforces a strict test-first discipline so every behavior change is backed by a test that was watched failing before any production code exists. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the full cycle of writing a failing test, verifying it fails for the right reason, writing minimal code to pass, and refactoring while staying green. - Testing Anti-Pattern Detection: Identifies and corrects common mistakes such as testing mock behavior, adding test-only methods to production classes, incomplete mocks, and mocking without understanding dependencies. - Rationalization Countermeasures: Provides concrete rebuttals to common excuses for skipping TDD, plus a verification checklist and red-flag list that trigger starting over. - Use Case: When fixing a bug where an empty email is accepted, write a failing test asserting the rejection error, watch it fail, implement the minimal validation, and confirm the suite passes before refactoring. ## Quick Start Ask the AI to implement a new feature or bugfix using strict test-driven development, writing the failing test first before any production code.
