What problem does it solve? Code written before tests often ships with unverified behavior, hidden bugs, and tests that pass immediately without proving anything. This Skill enforces a strict test-first discipline so every line of production code is backed by a test that was watched failing first. ## Core Features & Use Cases - Red-Green-Refactor Cycle: Guides writing a failing test, verifying the failure, writing minimal code to pass, and refactoring while staying green. - Anti-Rationalization Guardrails: Counters common excuses like "I'll test after" or "deleting code is wasteful" with concrete reasoning and red-flag checklists. - Testing Anti-Patterns Reference: Covers testing mock behavior, test-only methods in production classes, incomplete mocks, and mocking without understanding dependencies. - 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, and confirm all tests pass before refactoring. ## Quick Start Ask the AI to implement the next feature or bugfix using strict test-driven development with a failing test written first.
