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

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

Does this skill allow for refactoring?

Yes, refactoring is the third step of the cycle. It encourages cleaning up code, improving names, and removing duplication only after the test is 'Green' (passing).

How does this skill handle bug fixes?

For bug fixes, the skill requires writing a failing test that reproduces the bug before any fix is applied, proving the fix works and preventing future regressions.

Why does this skill require watching a test fail first?

Watching a test fail ('Red' phase) proves that the test is actually testing the intended behavior and isn't passing by accident or because of existing code, ensuring the test is valid.

Can I skip TDD for simple tasks?

The skill advises against rationalizing shortcuts, as simple code can still break. Exceptions like throwaway prototypes should be cleared with a human partner.

Test-Driven Development (TDD) Workflow

Name: Test-Driven Development (TDD) Workflow
Author: rbergman

byrbergman

•

Seguridad y Pruebas

Enforces a strict Red-Green-Refactor cycle to ensure every line of production code is verified by a test that was proven to fail first.

The TDD skill implements a rigorous Test-Driven Development methodology within Claude Code, ensuring high-quality, reliable software through the 'Iron Law': no production code without a failing test first. It guides users through the mandatory Red-Green-Refactor stages, requiring verification that tests fail for the right reasons before implementation begins. This disciplined approach eliminates the bias of 'tests-after' development, prevents over-engineering via minimal code requirements, and provides a systematic framework for both feature development and bug fixing.

Características Principales

01Minimalist 'Green' implementation guidance to avoid over-engineering

02Mandatory 'Verify Red' checks to prevent false-positive tests

03Integrated bug reproduction workflow via failing test cases

04Strict enforcement of the Red-Green-Refactor cycle

051 GitHub stars

06Standardized verification checklists for feature completion

Casos de Uso

01Implementing new features with 100% verified test coverage

02Safely refactoring complex logic while maintaining green status

03Resolving production bugs by first creating a reproducible failing test

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add rbergman/dark-matter-marketplace tdd

For use in Claude.ai and ChatGPT

Características Principales

01Minimalist 'Green' implementation guidance to avoid over-engineering

02Mandatory 'Verify Red' checks to prevent false-positive tests

03Integrated bug reproduction workflow via failing test cases

04Strict enforcement of the Red-Green-Refactor cycle

051 GitHub stars

06Standardized verification checklists for feature completion

Casos de Uso

01Implementing new features with 100% verified test coverage

02Safely refactoring complex logic while maintaining green status

03Resolving production bugs by first creating a reproducible failing test

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add rbergman/dark-matter-marketplace tdd

For use in Claude.ai and ChatGPT