What problem does it solve?
It helps you develop software more reliably by using test-driven development, so behavior is validated through integration-style tests rather than fragile implementation details.
Core Features & Use Cases
- Red-Green-Refactor loop: Guides you to write a failing test, implement the minimal code to pass, then refine design without breaking tests.
- Behavior-first testing: Emphasizes tests that verify public interfaces and observable outcomes, making them resilient to refactors.
- Tracer-bullet workflow: Encourages vertical slicing (one test at a time) to reduce “horizontal slicing” anti-patterns and avoid speculative test coverage.
- Mocking boundaries: Teaches when to mock (system boundaries like external APIs, databases, time/randomness, filesystem) and when not to.
Quick Start
Use this skill when you’re fixing a bug or building a feature and want to ensure the change is verified by an end-to-end integration-style test that would still pass after refactoring.