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 one failing test, verifying it fails for the right reason, implementing minimal code, and refactoring while staying green. - Rationalization Detection: Lists common excuses for skipping TDD ("too simple to test", "I'll test after") and counters each with concrete reasoning. - Testing Anti-Pattern 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 error, watch it fail, implement the minimal validation, and verify all tests pass before refactoring. ## Quick Start Use the test-driven-development skill to implement this feature by writing a failing test first, then the minimal code to make it pass.
