Skill

tdd

This skill should be used when the user asks to 'do TDD', 'test-driven development', 'red green refactor', 'write a failing test first', or wants to implement a feature using test-driven development.

npx claudepluginhub 45ck/prompt-language --plugin prompt-language

Tool Access

This skill is limited to using the following tools:

ReadWriteEditBashGrepGlob

Preview

Implement the requested feature using strict TDD: red, green, refactor.

Supporting Assets

examples/multi-ecosystem.md

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Stars3

Forks0

Last CommitApr 10, 2026

Actions

View Source View Plugin View on GitHub View README

Test-Driven Development

Implement the requested feature using strict TDD: red, green, refactor.

Use this when adding or changing behavior. Do not use this to recover an already failing test suite (use fix-and-test) or to perform behavior-preserving cleanup only (use refactor).

What to do

Read the feature requirement from the argument.

Add or update one test that expresses the next behavior slice.

Run the targeted test and confirm it fails first (red).

Implement the smallest change to pass that test (green).

Refactor with all tests still green before starting the next slice.

Flow

flow: retry max 5 run: npm test if command_failed prompt: Read the test failures. If no test exists yet for the feature, write one (red phase). Otherwise fix the implementation to make it pass (green phase). Only write minimum code needed. end end done when: tests_pass lint_pass

Rules

Always create the failing test before implementation for new behavior.

The test must fail before you write implementation code. If it passes immediately, the test is not testing the new behavior.

Write the minimum code to pass. Do not over-engineer.

Once green, refactor for clarity. Do not add new behavior during refactor.

Examples

For language-specific TDD loop command examples, see examples/multi-ecosystem.md.

Test-Driven Development

Implement the requested feature using strict TDD: red, green, refactor.

Use this when adding or changing behavior. Do not use this to recover an already failing test suite (use fix-and-test) or to perform behavior-preserving cleanup only (use refactor).

What to do

Read the feature requirement from the argument.
Add or update one test that expresses the next behavior slice.
Run the targeted test and confirm it fails first (red).
Implement the smallest change to pass that test (green).
Refactor with all tests still green before starting the next slice.

Flow

flow:
  retry max 5
    run: npm test
    if command_failed
      prompt: Read the test failures. If no test exists yet for the feature, write one (red phase). Otherwise fix the implementation to make it pass (green phase). Only write minimum code needed.
    end
  end

done when:
  tests_pass
  lint_pass

Rules

Always create the failing test before implementation for new behavior.
The test must fail before you write implementation code. If it passes immediately, the test is not testing the new behavior.
Write the minimum code to pass. Do not over-engineer.
Once green, refactor for clarity. Do not add new behavior during refactor.

Examples

For language-specific TDD loop command examples, see examples/multi-ecosystem.md.