tdd

Guide developers through test-driven development with test-first and red-green-refactor cycles.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/nkabbara/dotfiles --skill tdd-nkabbara
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/nkabbara/dotfiles/tree/main/exact_dot_agents/exact_skills/exact_mattpocock/exact_tdd
Command: npx skills add https://github.com/nkabbara/dotfiles --skill tdd-nkabbara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates the implementation of test-driven development (TDD) practices, ensuring that code is built with thorough testing from the start, which enhances code quality and reliability.

Core Features & Use Cases

  • Test-First Approach: Encourages writing tests before writing code, leading to better design and functionality.
  • Red-Green-Refactor Cycle: Guides through the process of writing a failing test, making it pass, and then refactoring the code.
  • Seam Identification: Helps in determining the public boundaries to test, ensuring that internal details are not over-tested.
  • Anti-Pattern Avoidance: Provides guidance on common pitfalls to avoid in TDD, such as implementation-coupled tests and tautological tests.
  • Use Case: Ideal for developers who want to ensure that their code is robust and maintainable, especially when working on complex features or when refactoring existing code.

Quick Start

Use the tdd skill to begin implementing test-driven development by writing a test for the new feature you're about to develop.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I implement test-driven development for new features?

Test-driven development is implemented by writing a failing test before writing code, making the test pass, and then refactoring. This test-first approach leads to better design and functionality.

What is the red-green-refactor cycle in software testing?

The red-green-refactor cycle in software testing involves writing a failing test (red), making the test pass with minimal code (green), and then refactoring the code for better quality without changing behavior.

How do I identify seams for testing without over-testing internal details?

Identifying seams for testing involves determining the public boundaries of your code to test. This ensures you validate necessary functionality without over-testing internal implementation details.

What are common test-driven development anti-patterns to avoid?

Common test-driven development anti-patterns to avoid include implementation-coupled tests and tautological tests. Avoiding these pitfalls ensures your tests are robust and maintainable.

Does test-driven development work for refactoring existing code?

Test-driven development works well for refactoring existing code by ensuring robustness and maintainability. It guides you to establish reliable tests first, securing code quality before making changes.