What is the main rule of this TDD skill?

The 'Iron Law' requires that no production code is written without a failing test first. If code is written before a test, it must be deleted and rewritten to ensure the test actually verifies the behavior.

When should I use the Test-Driven Development skill?

It should be used for all new features, bug fixes, and refactoring tasks. Exceptions like throwaway prototypes or config files should be discussed with a human partner.

Why is it necessary to watch a test fail?

Watching a test fail ensures it is actually testing the intended behavior; if a test passes immediately, it doesn't prove that your new code is what made the difference or that the test is valid.

How does TDD help with refactoring?

Because you have a comprehensive suite of tests that passed during the 'Green' phase, you can safely clean up and optimize code during the 'Refactor' phase knowing any accidental breakage will be caught immediately.

Strict Test-Driven Development (TDD)

Name: Strict Test-Driven Development (TDD)
Author: seanGSISG

byseanGSISG

보안 및 테스팅

Enforces a disciplined Red-Green-Refactor workflow to ensure high-quality, bug-free code through test-first implementation.

소개

This skill empowers Claude to adhere to the rigorous standards of Test-Driven Development (TDD) by mandating that failing tests be written before any production code. It follows the 'Iron Law' of TDD, guiding users through the Red-Green-Refactor cycle to ensure that tests are meaningful, code is minimal and purposeful, and regressions are prevented. By strictly requiring a failure before a pass, this skill guarantees that tests are actually verifying behavior rather than just providing passive coverage, leading to more maintainable and resilient software architectures.

주요 기능

Mandatory test failure verification
0 GitHub stars
Enforced Red-Green-Refactor cycle
Clean refactoring guidelines
Minimalist production code implementation
Automated regression prevention

사용 사례

Fixing bugs by first reproducing them with failing tests
Refactoring legacy code while maintaining behavioral integrity
Implementing new software features with high reliability

소개

주요 기능

Mandatory test failure verification
0 GitHub stars
Enforced Red-Green-Refactor cycle
Clean refactoring guidelines
Minimalist production code implementation
Automated regression prevention

사용 사례

Fixing bugs by first reproducing them with failing tests
Refactoring legacy code while maintaining behavioral integrity
Implementing new software features with high reliability