Apply test-driven development through red-green-refactor cycles with behavior-focused integration tests.
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill tdd-ayehiaa
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.claude/skills/tdd Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill tdd-ayehiaa
TDD helps you reduce regressions and increase confidence by forcing you to specify desired behavior as tests before (and alongside) implementing features or fixes.
Use case example: You’re fixing a checkout bug and want a test that proves the user-facing behavior (e.g., checkout completes and returns the correct status) while keeping the test resilient to internal refactors.
Ask for a TDD plan using the red-green-refactor loop for a specific feature or bug, then request one tracer-bullet test focused on public behavior and minimal implementation to make it pass.
High-intent search queries and answers about installing and using this skill.
Behavior-first integration testing exercises public interfaces and real code paths instead of relying on brittle implementation details. This approach ensures tests verify user-facing outcomes, keeping them resilient when you refactor underlying code structure.
The red-green-refactor cycle in test-driven development involves writing a failing test first (red), implementing the minimum code required to pass it (green), and then improving the design without altering behavior (refactor).
Applying TDD to fix a bug using vertical slices involves writing one behavior-focused test at a time as a tracer bullet. You then implement the minimal logic to pass that specific test before moving to the next slice, avoiding bulk implementation changes.
Avoid horizontal slicing when writing tests because writing many tests or implementation changes in bulk leads to TDD failure modes. A vertical, one-test-at-a-time tracer-bullet approach ensures steady progress and validates behavior incrementally.
Designing for testability involves structuring interfaces with dependency injection, returning results instead of causing side effects, and keeping surface areas small. Mocking boundaries should be defined to avoid coupling tests with internal implementation details.
az9713Automate end-to-end feature development with a red-green-refactor TDD loop.
walid-mosGuide Test-Driven Development with vertical slices and RED-GREEN-REFACTOR cycles.
bastani-incGuide test-driven development with red-green-refactor loops and behavior-focused validation.
AGMO-IncGuide teams through a RED-GREEN-REFACTOR cycle with failing tests before code.
