tdd

Guide test-driven development through the red-green-refactor cycle with integration tests.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/remiconnesson/v0-video2md --skill tdd-remiconnesson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/remiconnesson/v0-video2md/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/remiconnesson/v0-video2md --skill tdd-remiconnesson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers build robust software by following the Test-Driven Development (TDD) methodology, ensuring code is reliable, maintainable, and meets user requirements.

Core Features & Use Cases

  • Red-Green-Refactor Loop: Guides the developer through writing a failing test, writing minimal code to pass, and then refactoring.
  • Integration Testing Focus: Emphasizes testing through public interfaces, making tests resilient to internal code changes.
  • Use Case: When starting a new feature or fixing a bug, use this Skill to ensure that the development process is guided by clear, verifiable tests from the outset.

Quick Start

Use the tdd skill to implement the user login functionality following the red-green-refactor loop.

Frequently Asked Questions about tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the red-green-refactor cycle in test-driven development?

Test-driven development uses integration tests to verify software behavior through public interfaces rather than internal implementation details. This approach makes tests resilient to internal code changes while ensuring features meet user requirements.

How do I start writing tests first when building a new feature?

Writing tests first when fixing a bug involves creating a failing test that reproduces the issue, then writing minimal code to make it pass. This Skill emphasizes avoiding horizontal slicing anti-patterns by focusing on vertical slices of functionality.

Should I use integration tests or unit tests for test-driven development?

Test-driven development should focus on integration tests that verify behavior through public interfaces. This approach makes tests resilient to internal code changes, unlike tests that rely on implementation details which break during refactoring.

How do I avoid horizontal slicing anti-patterns when writing tests first?

Avoid horizontal slicing anti-patterns by building vertical slices of functionality through the red-green-refactor cycle. This Skill emphasizes writing integration tests that verify behavior through public interfaces, ensuring each slice delivers complete user-facing value.