TD

Enforces a strict TDD workflow requiring tests for all features and bug fixes.

Install

mkdir -p .claude/skills/tdd-workflow-caovinhphuc && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19099" && unzip -o skill.zip -d .claude/skills/tdd-workflow-caovinhphuc && rm skill.zip

Installs to .claude/skills/tdd-workflow-caovinhphuc

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
171 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Write tests before implementing code
  • Ensure minimum 80% code coverage across test types
  • Validate RED state before production code changes
  • Implement minimal code to achieve GREEN state
  • Refactor code while maintaining GREEN tests

How it works

The skill guides development through a strict TDD cycle: writing failing tests, confirming the RED state, implementing minimal code to achieve a GREEN state, and then refactoring while ensuring tests remain GREEN. It emphasizes checkpoint commits for each stage.

Inputs & outputs

You give it
User journeys, failing tests, minimal code implementation
You get back
Passing tests, refactored code, and Git checkpoint commits

When to use tdd-workflow

  • Developing new features
  • Fixing production bugs
  • Refactoring code

About tdd-workflow

Guarantees that tests are written before code, ensuring comprehensive unit, integration, and E2E coverage across the development cycle.

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

When not to use it

  • When test-driven development principles are not followed
  • When complete test coverage is not a requirement
  • When tests are not executed to confirm RED or GREEN states

Limitations

  • Requires minimum 80% coverage (unit + integration + E2E)
  • Requires checkpoint commits for each TDD stage
  • Does not allow editing production code until RED state is confirmed

How it compares

This workflow enforces a disciplined TDD approach with explicit RED-GREEN-REFACTOR cycles and Git checkpoints, contrasting with development where tests are written after code or coverage is not strictly enforced.

Compared to similar skills

tdd-workflow side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
tdd-workflow (this skill)05moReviewIntermediate
vitest417moNo flagsIntermediate
svelte-expert1110moNo flagsIntermediate
implementing-cards73moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

vitest

antfu

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

41183

svelte-expert

Raudbjorn

Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.

11107

implementing-cards

bcollazo

Fill out the implementation of effects of different attacks, abilities, and trainer cards in this Pokemon TCG Pocket engine codebase.

790

zod-4

prowler-cloud

Zod 4 schema validation patterns. Trigger: When creating or updating Zod v4 schemas for validation/parsing (forms, request payloads, adapters), including v3 -> v4 migration patterns.

1260

csharp-pro

sickn33

Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.

953

write-unit-tests

tldraw

Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.

545

Search skills

Search the agent skills registry