test-driven-development

What problem does it solve? Developers often write code before tests, producing tests that pass immediately and prove 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. ## 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: Counters common excuses like "I'll test after" or "deleting code is wasteful" with concrete reasoning and red-flag checklists. - 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 an empty email is accepted, write a failing test asserting the rejection error, watch it fail, implement the minimal validation, and confirm all tests pass before refactoring. ## Quick Start Ask the AI to implement a new feature or bugfix using strict test-driven development with a failing test written first.