What problem does it solve? Developers often write production code first and add tests afterward, which produces 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 TDD cycle with mandatory verification that tests fail for the right reason before any implementation code is written. - Rationalization Detection: Lists common excuses for skipping TDD (manual testing, sunk cost, "too simple to test") and counters each with concrete reasoning. - Testing Anti-Pattern Reference: Ships a companion reference covering mock-behavior testing, test-only production methods, incomplete mocks, and over-mocking, with gate functions to catch violations. - Use Case: When fixing a bug where empty emails are accepted, write a failing test asserting the rejection, watch it fail, implement the minimal validation, verify green, then refactor. ## Quick Start Ask the assistant to implement a new feature or bugfix using strict test-driven development with a failing test written first.
