What problem does it solve? Developers often write production code first and add tests afterward, which produces tests that pass immediately and prove nothing about correctness. This Skill enforces strict test-driven development so every feature, bug fix, and refactor is backed by a test that was seen to fail first. ## Core Features & Use Cases - Red-Green-Refactor Workflow: Guides the full TDD cycle—write a failing test, verify it fails for the right reason, write minimal code to pass, then refactor while keeping tests green. - Anti-Pattern Detection: Ships a testing-anti-patterns reference covering mock misuse, test-only production methods, incomplete mocks, and tests written as an afterthought. - Excuse Countering: Provides concrete rebuttals to common rationalizations like "I'll add tests later" or "I already tested manually." - 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 confirm the suite passes. ## Quick Start Ask the AI to implement a new feature or fix a bug using strict test-driven development with a failing test written before any production code.
