When should I skip TDD while using this skill?

TDD should be used always for features and fixes. Exceptions are rare (like throwaway prototypes) and should involve a human partner's decision.

What is the benefit of writing 'minimal' code in the GREEN phase?

Writing the simplest code possible prevents YAGNI (You Ain't Gonna Need It) and over-engineering, ensuring the codebase remains clean and focused solely on requirements.

What is the Iron Law in this TDD skill?

The Iron Law states that no production code can be written without a failing test first. If code is written before a test, it must be deleted and reimplemented from the test forward.

How does the skill handle bug fixes?

When a bug is found, the skill requires writing a test that reproduces the bug. You must watch that test fail before writing the minimal code necessary to fix it.

Why is watching the test fail (RED phase) mandatory?

If you don't see a test fail, you cannot be certain it is testing the right thing or that it wouldn't pass regardless of your changes. Failure proves the test's validity.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: martin-janci

bymartin-janci

•

Seguridad y Pruebas

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

This skill transforms Claude into a disciplined TDD practitioner, strictly adhering to the 'test-first' methodology for all features and bug fixes. It enforces the 'Iron Law' of no production code without a failing test, guiding the AI through the cycle of writing failing tests, implementing minimal passing code, and refactoring while maintaining green status. By requiring failure verification before implementation, it prevents common pitfalls like post-hoc testing or over-engineering, resulting in more resilient, well-documented, and maintainable software architecture.

Características Principales

01Strict enforcement of the Red-Green-Refactor development cycle

02Focus on minimal code implementation to pass tests and avoid over-engineering

031 GitHub stars

04Comprehensive verification checklists to ensure feature completion and code quality

05Standardized bug reproduction through failing test cases

06Mandatory verification of test failure (Red) before writing implementation code

Casos de Uso

01Reliably fixing bugs by creating regression tests that reproduce the issue first

02Developing new features with 100% test coverage from the start

03Refactoring complex logic with a safety net of existing behavior-driven tests

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add martin-janci/claude-marketplace test-driven-development

For use in Claude.ai and ChatGPT

Download Skill