test-driven-development

What problem does it solve? Developers often write production code before tests, producing tests that pass immediately and prove nothing. This Skill enforces a strict test-first discipline so every feature and bugfix is backed by a test that was watched failing before implementation. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the full TDD cycle with mandatory verification that each test fails for the right reason before any implementation code is written. - Rationalization Countermeasures: Provides a catalog of common excuses ("too simple to test", "I'll test after") with concrete rebuttals to keep the workflow honest. - Testing Anti-Pattern Reference: Ships a companion reference covering mock-behavior testing, test-only production methods, incomplete mocks, and over-mocking, with gate functions to catch each. - 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, verify green, then refactor. ## Quick Start Ask the agent to implement a new feature or bugfix using strict test-driven development with a failing test written first.