When can I skip the TDD process?

TDD should always be used for new features, bug fixes, and refactoring. Exceptions are only permitted for throwaway prototypes, generated code, or configuration files.

Why is it mandatory to watch a test fail?

Watching a test fail (the RED phase) proves that the test is actually checking the intended behavior and that it won't pass by mistake or for the wrong reasons.

What is the 'Iron Law' of this TDD skill?

The Iron Law states that no production code should be written without a failing test first. If code is written before a test, it should be deleted and rewritten following the TDD cycle.

How does this skill handle the REFACTOR phase?

After achieving a GREEN state (passing test), the skill guides you to clean up duplication and improve names while ensuring all tests stay green, without adding new functionality.

Is TDD slower than traditional coding?

While it requires more upfront work, TDD is faster in the long run because it catches bugs immediately, prevents regressions, and serves as live documentation, reducing time spent on manual debugging.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: zoosewu

byzoosewu

보안 및 테스팅

Enforces a strict Red-Green-Refactor workflow to ensure high-quality code through mandatory test-first implementation.

소개

This skill provides an uncompromising framework for Test-Driven Development (TDD) within Claude Code, emphasizing the 'Iron Law' that no production code should be written without a failing test first. It guides developers through the complete software lifecycle—from defining behaviors with tests to writing minimal passing code and refactoring—ensuring that every line of code is purposeful, verified, and free from technical debt. By preventing rationalizations for skipping tests, it builds a foundation of systematic, automated verification that outperforms manual debugging and ad-hoc testing.

주요 기능

Mandatory failure verification to prevent false positives
0 GitHub stars
Strict Red-Green-Refactor cycle enforcement
Minimalist code implementation strategies to avoid over-engineering
Strategic guidance for handling bugs, refactoring, and complex test setups
Comprehensive verification checklists for production-ready code

사용 사례

Implementing new features with guaranteed test coverage and clear API design
Safely refactoring existing logic while ensuring no regressions are introduced
Fixing bugs by reproducing issues with failing tests before applying fixes

소개

주요 기능

Mandatory failure verification to prevent false positives
0 GitHub stars
Strict Red-Green-Refactor cycle enforcement
Minimalist code implementation strategies to avoid over-engineering
Strategic guidance for handling bugs, refactoring, and complex test setups
Comprehensive verification checklists for production-ready code

사용 사례

Implementing new features with guaranteed test coverage and clear API design
Safely refactoring existing logic while ensuring no regressions are introduced
Fixing bugs by reproducing issues with failing tests before applying fixes