Test-Driven Development (TDD) Guardrail FAQs

Question 1

How does this skill handle bug fixes?

Accepted Answer

It requires the creation of a failing test that reproduces the bug before any fix is implemented, ensuring the bug is truly understood and prevented from recurring.

Question 2

Why does the skill insist on watching a test fail?

Accepted Answer

Watching a test fail (the RED phase) proves that the test is actually checking the intended functionality and isn't passing by accident or testing existing behavior incorrectly.

Question 3

What is the 'Iron Law' enforced by this skill?

Accepted Answer

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

Question 4

When is it acceptable to skip the TDD process?

Accepted Answer

TDD should always be used for features, bug fixes, and refactoring. Exceptions are only allowed for throwaway prototypes, generated code, or configuration files, and typically require human approval.

Question 5

Does this skill support specific testing frameworks?

Accepted Answer

While it uses TypeScript and npm in its documentation examples, the core principles of Red-Green-Refactor are language-agnostic and can be applied to any testing framework compatible with Claude Code.

Test-Driven Development (TDD) Guardrail

Key Features

Use Cases

Test-Driven Development (TDD) Guardrail

Key Features

Use Cases