Can I use this for fixing existing bugs?

Absolutely. The recommended workflow is to write a test that reproduces the bug (Red), then write the fix (Green), ensuring the bug is verified and protected against regressions.

What happens if a test passes immediately?

If a test passes immediately, you are testing existing behavior or the test is flawed. You must fix the test so it fails correctly before writing implementation code.

Why does this skill require deleting code written before a test?

Writing code before a test violates the core principle of TDD. If you didn't see the test fail first, you have no proof the test is actually verifying the new behavior rather than passing by coincidence.

Is this skill compatible with all programming languages?

Yes, this skill provides domain-specific guidance for the TDD methodology which is language-agnostic and can be applied to any framework like Jest, Pytest, or Vitest.

Test-Driven Development (TDD) Superpowers

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

byAlabamaMike

Security & Testing

Enforces a strict test-first development workflow to ensure code reliability and eliminate technical debt.

About

This skill transforms Claude into a disciplined TDD practitioner, mandating that every line of production code is preceded by a failing test. By adhering to the rigorous Red-Green-Refactor cycle, it ensures that your tests actually verify behavior rather than just implementation, resulting in higher code quality, better architectural design, and a robust suite of regression tests. It is an essential tool for developers who prioritize long-term maintainability and want to ensure their code is 'proven' to work through automated verification.

Key Features

Mandatory verification of test failure before implementation
Automated verification of regression safety during refactoring
0 GitHub stars
Prevention of over-engineering via the YAGNI principle
Strict Red-Green-Refactor cycle enforcement
Guidance on writing minimal code to satisfy requirements

Use Cases

Safely refactoring complex logic while maintaining existing behavior.
Implementing new features with high confidence and built-in documentation.
Reproducing and fixing bugs by starting with a failing test case.

About

Key Features

Mandatory verification of test failure before implementation
Automated verification of regression safety during refactoring
0 GitHub stars
Prevention of over-engineering via the YAGNI principle
Strict Red-Green-Refactor cycle enforcement
Guidance on writing minimal code to satisfy requirements

Use Cases

Safely refactoring complex logic while maintaining existing behavior.
Implementing new features with high confidence and built-in documentation.
Reproducing and fixing bugs by starting with a failing test case.