What problem does it solve? Developers often write production code before tests, producing tests that pass immediately and prove nothing about correctness. This Skill enforces a strict test-first discipline so every feature and bugfix is backed by a test that was watched failing before implementation. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the full cycle of writing a failing test, verifying the failure, writing minimal passing code, and refactoring while staying green. - Anti-Rationalization Guardrails: Lists common excuses for skipping TDD and the red flags that mean code should be deleted and restarted test-first. - Testing Anti-Pattern Reference: Companion reference covers testing mock behavior, test-only production methods, 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, and confirm the suite passes. ## Quick Start Ask the AI to implement the next feature or bugfix using strict test-driven development with a failing test written first.
