Is TDD slower than normal coding?

While it may feel slower initially, TDD is faster in the long run because it significantly reduces time spent on debugging, manual verification, and fixing regressions.

What happens if a test passes immediately during the RED phase?

If a test passes immediately, it means you are testing existing behavior or the test is invalid. The skill will prompt you to fix the test until it fails for the right reason.

Why does this skill insist on deleting code written before tests?

This prevents 'tests-after' bias. Writing tests for existing code often results in tests that pass by default without ever proving they can catch a failure, which defeats the core purpose of TDD.

Can I use this skill for bug fixes?

Absolutely. The skill requires you to write a failing test that reproduces the bug first, ensuring the fix actually works and preventing that specific bug from ever returning.

Does this skill support specific testing frameworks?

The TDD methodology is language-agnostic. It works with any test runner (like Jest, Pytest, or Vitest) that your project is configured to use.

Strict Test-Driven Development (TDD)

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

byfranroa

Seguridad y Pruebas

Enforces a rigorous Red-Green-Refactor workflow by requiring failing tests before any production code is written.

Acerca de

This skill transforms Claude into a disciplined TDD practitioner, ensuring that every line of production code is preceded by a failing test. It strictly enforces the 'Iron Law' of TDD: if you didn't watch the test fail, you don't know if it actually verifies the intended behavior. By following the systematic Red-Green-Refactor cycle, it helps developers eliminate technical debt, discover edge cases early, and produce highly reliable, self-documenting codebases. It is an essential tool for high-stakes feature development, bug fixing, and refactoring where verification and design clarity are non-negotiable.

Características Principales

Systematic bug reproduction through failing test cases
0 GitHub stars
Mandatory verification of failing tests before implementation
Strict enforcement of the Red-Green-Refactor cycle
Comprehensive verification checklists for every unit of work
Promotes writing minimal code to satisfy requirements (YAGNI)

Casos de Uso

Safely refactoring existing legacy code while maintaining functional parity
Reproducing and fixing complex bugs systematically to prevent regressions
Implementing new features with high confidence and minimal technical debt

Acerca de

Características Principales

Systematic bug reproduction through failing test cases
0 GitHub stars
Mandatory verification of failing tests before implementation
Strict enforcement of the Red-Green-Refactor cycle
Comprehensive verification checklists for every unit of work
Promotes writing minimal code to satisfy requirements (YAGNI)

Casos de Uso

Safely refactoring existing legacy code while maintaining functional parity
Reproducing and fixing complex bugs systematically to prevent regressions
Implementing new features with high confidence and minimal technical debt