What problem does it solve? Code written before tests often ships with undetected bugs, and tests written after implementation only confirm what was built rather than what was required. This Skill enforces a strict test-first discipline so every feature and bugfix is proven by a failing test before implementation begins. ## 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. - Anti-Rationalization Guardrails: Provides explicit rebuttals to common excuses for skipping TDD, plus red flags that signal when to delete code and start over. - Testing Anti-Pattern Reference: A companion guide covering mock misuse, test-only production methods, incomplete mocks, and tests written as an afterthought. - 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, and confirm the whole suite passes. ## Quick Start Ask the AI to implement a new feature or bugfix using strict test-driven development with a failing test written first.