What problem does it solve? Code written before tests often passes tests immediately, proving nothing about correctness. This Skill enforces strict test-driven development so every feature and bugfix is backed by a test that was watched failing first, eliminating unverified production code and common testing anti-patterns. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides writing a failing test, verifying it fails for the right reason, implementing minimal code, and refactoring while staying green. - Anti-Pattern Detection: Identifies testing mock behavior, test-only methods in production classes, incomplete mocks, and mocking without understanding dependencies. - Rationalization Countering: Provides concrete rebuttals to common excuses like "I'll test after" or "deleting code is wasteful." - 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 Use test-driven development to implement this feature, writing a failing test first before any production code.
