What problem does it solve?
This Skill solves the common issue of shipping untested, bug-prone code that leads to costly post-release debugging, unexpected regressions, and unclear code behavior that is hard to maintain or modify.
Core Features & Use Cases
- Strict TDD Workflow Enforcement: Mandates the Red-Green-Refactor cycle for all feature development, bug fixes, and refactoring work, with clear rules to prevent skipping test-first steps.
- Anti-Pattern Protection: Includes guidance to avoid common testing mistakes like testing mock behavior instead of real functionality, adding test-only code to production classes, and writing incomplete mocks.
- Practical Guardrails: Provides verification checklists, red flag warnings, and debugging integration rules to ensure TDD is followed correctly even in complex scenarios.
Use Case: For example, when implementing a new payment processing feature, use this Skill to first write a failing test for the transaction validation logic, then implement the minimal code to pass the test, ensuring the feature works as expected before moving to the next step.
Quick Start
Use the test-driven-development skill to implement the new user notification feature by first writing a failing test for the push notification delivery logic, then writing the minimal code to pass the test.
