How does this skill handle bug fixes?

It requires writing a failing test that reproduces the bug before any fix is implemented. This proves the fix works and prevents the bug from ever returning via regression.

Why is watching the test fail mandatory?

Watching a test fail (the Red phase) confirms that the test is actually checking the right behavior and isn't passing by accident or due to a typo.

What is the 'Iron Law' in 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 must be deleted and started fresh to ensure the test truly validates the behavior.

Does this skill work with any testing framework?

Yes, the principles are framework-agnostic and can be applied to Jest, Vitest, Pytest, or any other automated testing tool.

Can I use this skill for refactoring?

Yes, it is ideal for refactoring. The TDD cycle ensures that you only clean up code once you are in the 'Green' state, allowing you to change structure while keeping behavior stable.

Test-Driven Development (TDD) Superpowers

Name: Test-Driven Development (TDD) Superpowers
Author: franroa

byfranroa

Seguridad y Pruebas

Enforces a strict Red-Green-Refactor cycle to ensure all code is verified by failing tests before implementation.

Acerca de

This skill transforms Claude into a highly disciplined TDD practitioner, enforcing the 'Iron Law' of writing failing tests before any production code. It provides a structured framework for the Red-Green-Refactor workflow, helping developers eliminate technical debt, discover edge cases early, and build highly reliable software. By requiring that tests fail before they pass, it guarantees that your test suite actually verifies behavior rather than just providing empty coverage.

Características Principales

Strict enforcement of the Red-Green-Refactor development cycle
Minimalist code implementation strategies to pass tests efficiently
Mandatory verification of failing tests to prevent false positives
Structured refactoring guidance to maintain clean code architecture
0 GitHub stars
Comprehensive TDD checklists for bug fixes and new feature development

Casos de Uso

Implementing new features with high confidence and minimal regressions
Safely refactoring legacy codebases by establishing a robust test safety net
Reproducing and fixing bugs by creating failing test cases first

Acerca de

Características Principales

Strict enforcement of the Red-Green-Refactor development cycle
Minimalist code implementation strategies to pass tests efficiently
Mandatory verification of failing tests to prevent false positives
Structured refactoring guidance to maintain clean code architecture
0 GitHub stars
Comprehensive TDD checklists for bug fixes and new feature development

Casos de Uso

Implementing new features with high confidence and minimal regressions
Safely refactoring legacy codebases by establishing a robust test safety net
Reproducing and fixing bugs by creating failing test cases first