TDD-Driven Documentation FAQs

Question 1

How does TDD apply to writing documentation?

Accepted Answer

In this context, TDD involves running a subagent to see it fail a task (Red), writing the documentation (Green), and then refining the text to close loopholes while maintaining compliance (Refactor).

Question 2

What is the 'Iron Law' of skill creation?

Accepted Answer

The Iron Law states: 'No skill without a failing test first.' You must observe an agent fail without the skill to ensure the documentation addresses the right behavior.

Question 3

How do I optimize skills for Claude's context window?

Accepted Answer

Focus on token efficiency by moving heavy references to secondary files, using cross-references instead of repeats, and keeping frequently-loaded skills under 200 words.

Question 4

When should I create a skill versus a standard guide?

Accepted Answer

Create a skill when the technique isn't intuitively obvious, applies broadly across projects, and provides a reusable pattern that others would benefit from.

Question 5

What is a Claude Code Skill?

Accepted Answer

A skill is a specialized reference guide for proven techniques, patterns, or tools that enhances Claude's behavior when performing specific tasks across different sessions.

TDD-Driven Documentation

Características Principales

Casos de Uso

TDD-Driven Documentation

Características Principales

Casos de Uso