TDD Enforcement FAQs

Question 1

Can I skip TDD for configuration or documentation?

Accepted Answer

Yes, the skill is designed to automatically ignore configuration files, documentation, type definitions (.d.ts), and migration files where TDD is not applicable.

Question 2

Does this skill work with any testing framework?

Accepted Answer

Yes, because it monitors file system activity and file paths rather than specific test syntax, it is compatible with any language or testing framework you use.

Question 3

What are the different enforcement profiles?

Accepted Answer

There are three levels: 'Minimal' disables enforcement, 'Standard' provides warnings when TDD is skipped, and 'Strict' blocks edits until a test file is created.

Question 4

How does the TDD Enforcement skill block unauthorized edits?

Accepted Answer

In 'Strict' mode, the skill uses a PreToolUse hook to detect if you are attempting to edit production files in the src/ directory without having first created or modified a test file in the current session.

Question 5

What is the Red-Green-Refactor cycle?

Accepted Answer

It is a development methodology where you write a failing test first (Red), implement the minimum code required to make that test pass (Green), and then clean up the code while keeping the tests passing (Refactor).

TDD Enforcement

Key Features

Use Cases

TDD Enforcement

Key Features

Use Cases