Strict TDD Workflow State Machine FAQs

Question 1

What happens if a TDD rule is violated?

Accepted Answer

The AI enters a 'VIOLATION' state, flags the error (such as writing implementation before a test), explains the mistake, and seeks user permission to recover to the correct state.

Question 2

How does the state machine governance work?

Accepted Answer

Claude must prefix every single message with its current TDD state (e.g., 🔴 TDD: RED). This ensures the AI remains focused on the specific TDD phase and doesn't skip critical steps like verification or refactoring.

Question 3

Which testing libraries are compatible with this workflow?

Accepted Answer

This skill is specifically optimized for Vitest and vitest-mock-extended, though the core TDD principles can be adapted to other JavaScript/TypeScript testing frameworks.

Question 4

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

Accepted Answer

The Iron Law states that no production code can be written without a failing test first. If code is written prematurely, the skill mandates that it must be deleted and started fresh from a test.

Question 5

Does it support dependency injection?

Accepted Answer

Yes, the skill enforces the fn(args, deps) pattern, ensuring that dependencies are mocked using vitest-mock-extended for isolated and predictable unit tests.

Strict TDD Workflow State Machine

Key Features

Use Cases

Strict TDD Workflow State Machine

Key Features

Use Cases