Why does this skill insist on watching a test fail?

Watching a test fail confirms that the test is actually checking the intended behavior and isn't passing by accident or testing the wrong thing.

What if I find TDD is slowing me down?

The skill treats TDD as a pragmatic tool that saves time in the long run by reducing debugging hours, preventing regressions, and clarifying software design early.

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

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

Can I use this skill for bug fixing?

Yes. The skill mandates writing a failing test that reproduces the bug before implementing a fix, ensuring the bug is truly resolved and won't return.

Test-Driven Development (TDD)

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

byabudhahir

•

Security & Testing

Enforces a disciplined Red-Green-Refactor workflow to ensure all production code is verified by failing tests first.

About

This skill transforms Claude into a rigorous TDD practitioner, strictly adhering to the 'Iron Law' that no production code shall be written without a preceding failing test. It guides users through the essential cycle of writing minimal tests, watching them fail for the right reasons, implementing the simplest passing code, and refactoring for quality. By eliminating common rationalizations for skipping tests, this skill helps developers build highly reliable, self-documenting codebases that are resistant to regressions and easy to maintain.

Key Features

Comprehensive TDD verification checklists for feature completion
Specialized workflows for bug fixes using reproduction tests
Mandatory verification of failing tests before implementation
1 GitHub stars
Guidance on writing minimal, behavior-focused tests over implementation mocks
Strict enforcement of the Red-Green-Refactor development cycle

Use Cases

Developing new features with high confidence and minimal technical debt
Safe refactoring of complex logic while maintaining behavioral integrity
Fixing software bugs by first creating reproducible automated test cases

About

Key Features

Comprehensive TDD verification checklists for feature completion
Specialized workflows for bug fixes using reproduction tests
Mandatory verification of failing tests before implementation
1 GitHub stars
Guidance on writing minimal, behavior-focused tests over implementation mocks
Strict enforcement of the Red-Green-Refactor development cycle

Use Cases

Developing new features with high confidence and minimal technical debt
Safe refactoring of complex logic while maintaining behavioral integrity
Fixing software bugs by first creating reproducible automated test cases