What problem does it solve? Code written before tests often ships unverified, and tests written after implementation pass immediately without proving they catch real bugs. This Skill enforces a strict test-first discipline so every behavior change 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 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 like "I'll test after" or "deleting code is wasteful", plus red flags that signal when to delete code and start over. - 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 each. - 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 AI to implement your next feature or bugfix using strict test-driven development with a failing test written and verified before any production code.
