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 fail first. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the full TDD cycle—write a failing test, verify it fails for the right reason, write minimal code to pass, then refactor while staying green. - Anti-Rationalization Guardrails: Provides explicit counters to common excuses like "I'll test after" or "deleting code is wasteful", with red flags that trigger a restart. - Testing Anti-Pattern Reference: Covers pitfalls such as 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 your next feature or bugfix using strict test-driven development with a failing test written first.
