New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

TDD Workflow

by cloudnative-co in cloudnative-co/claude-code-starter-kit

A skill your agent uses when the user explicitly asks for TDD or a tests-first workflow, or when developing a new feature with a test coverage requirement.

MITAuto-check passedTesting & QA

Install TDD Workflow

skills CLI
$ npx skills add cloudnative-co/claude-code-starter-kit --skill tdd-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cloudnative-co/claude-code-starter-kit tdd-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tdd-workflow .claude/skills/tdd-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tdd-workflow
GitHub stars
151
Token cost
~1.1k tokens
SKILL.md length
438 words
Files
4 (incl. scripts, references)
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user explicitly asks for TDD or a tests-first workflow, or when developing a new feature with a test coverage requirement.

  • Works in 10 steps: Tests BEFORE Code → Coverage Guidance → Test Types → …
  • The user explicitly asks for TDD
  • SKILL.md covers When to Activate, Core Principles, TDD Workflow Steps and Best Practices, plus 2 more sections
  • Runs Shell scripts from its folder; calls npm, pytest and bash

What it does

TDD Workflow is an agent skill from cloudnative-co/claude-code-starter-kit. Use this skill when the user explicitly asks for TDD or a tests-first workflow, or when developing a new feature with a test coverage requirement. Provides a structured red-green-refactor workflow with unit, integration, and E2E test guidance.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/test-templates.md`, `references/testing-mistakes.md` and `scripts/check-coverage.sh`).

It sits in Testing & QA, covering Test-driven development. The repository describes itself as: One-command setup of a complete Claude Code development environment with interactive wizard. The licence is MIT.

When your agent uses it

  • The user explicitly asks for TDD
  • A tests-first workflow
  • Developing a new feature with a test coverage requirement

Example prompts

  • “/tdd-workflow”

Requirements

  • Python 3
  • Node.js
  • A Bash shell

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Tests BEFORE Code
  2. Coverage Guidance
  3. Test Types
  4. Write User Journeys
  5. Generate Test Cases
  6. Run Tests (They Should Fail)
  7. Implement Code
  8. Run Tests Again
  9. Refactor
  10. Verify Coverage

What it can do on your machine

Read from SKILL.md and the folder at commit f00e7ce. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • npm
    • pytest
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TDD Workflow loads about 1.1k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 438 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from cloudnative-co/claude-code-starter-kit at commit f00e7ce, republished under its MIT licence (© cloudnative-co). 438 words, ~1,051 tokens.

Download SKILL.mdSave it as .claude/skills/tdd-workflow/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
tdd-workflow
description
Use this skill when the user explicitly asks for TDD or a tests-first workflow, or when developing a new feature with a test coverage requirement. Provides a structured red-green-refactor workflow with unit, integration, and E2E test guidance.
when_to_use
Use when the user explicitly requests TDD/tests-first development, or when building a new feature where test coverage is a stated requirement.

Test-Driven Development Workflow

This skill provides a structured TDD workflow for projects that adopt tests-first development.

When to Activate

  • The user explicitly asks for TDD or tests-first development
  • New feature work where test coverage is a stated requirement
  • Adding API endpoints or components under a coverage policy

For routine bug fixes or refactors, add focused tests for the changed behavior instead of invoking this full workflow (the /tdd command and tdd-guide agent remain available when you want it explicitly).

Core Principles

1. Tests BEFORE Code

Within this workflow, the default is to write tests first, then implement code to make tests pass.

2. Coverage Guidance
  • Coverage target follows the project's own standard (e.g., 80% as a common baseline); scale effort with the size of the change
  • Cover relevant edge cases
  • Test error scenarios
  • Verify boundary conditions
3. Test Types

Unit Tests - Individual functions, utilities, component logic, pure functions, helpers.

Integration Tests - API endpoints, database operations, service interactions, external API calls.

E2E Tests (Playwright) - Critical user flows, complete workflows, browser automation, UI interactions. Applies to web UI projects only.

TDD Workflow Steps

Step 1: Write User Journeys
As a [role], I want to [action], so that [benefit]

Example:
As a user, I want to search for markets semantically,
so that I can find relevant markets even without exact keywords.
Step 2: Generate Test Cases

For each user journey, create comprehensive test cases covering happy paths, edge cases, fallback behavior, and sorting/filtering logic.

Step 3: Run Tests (They Should Fail)

Use the project's test runner. Examples:

bash
npm test                      # Node.js
pytest                        # Python
bash tests/run-unit-tests.sh  # shell projects
# Tests should fail - we haven't implemented yet
Step 4: Implement Code

Write minimal code to make tests pass.

Step 5: Run Tests Again

Re-run the same test command (e.g., npm test, pytest):

bash
npm test
# Tests should now pass
Step 6: Refactor

Improve code quality while keeping tests green:

  • Remove duplication
  • Improve naming
  • Optimize performance
  • Enhance readability
Show full SKILL.md (173 more words)Show less
Step 7: Verify Coverage

Use the project's coverage tooling. Examples:

bash
npm run test:coverage   # Node.js
pytest --cov            # Python
# Verify coverage meets the project's target

Best Practices

  1. Write Tests First - Always TDD
  2. One Assert Per Test - Focus on single behavior
  3. Descriptive Test Names - Explain what's tested
  4. Arrange-Act-Assert - Clear test structure
  5. Mock External Dependencies - Isolate unit tests
  6. Test Edge Cases - Null, undefined, empty, large
  7. Test Error Paths - Not just happy paths
  8. Keep Tests Fast - Unit tests < 50ms each
  9. Clean Up After Tests - No side effects
  10. Review Coverage Reports - Identify gaps

Success Metrics

  • Coverage target met (per project standard, e.g., 80%)
  • All tests passing (green)
  • No skipped or disabled tests
  • Fast test execution (< 30s for unit tests)
  • E2E tests cover critical user flows
  • Tests catch bugs before production

References

These templates target JavaScript/TypeScript stacks; adapt the structure for other languages.

  • references/test-templates.md - Unit, integration, E2E, and mocking code templates (JS/TS)
  • references/testing-mistakes.md - Common pitfalls, file organization, coverage config, CI setup (JS/TS)

Remember: Give changed behavior a focused test. Tests are the safety net that enables confident refactoring, rapid development, and production reliability.

© cloudnative-co, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/tdd-workflow of cloudnative-co/claude-code-starter-kit.

  • SKILL.md
  • references/test-templates.md
  • references/testing-mistakes.md
  • scripts/check-coverage.sh

Open the folder on GitHubat commit f00e7ce

Compare with similar skills

TDD Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TDD Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TDD Workflow this skillcloudnative-co/claude-code-starter-kit151—~1.1kAutomated safety check: PassMIT
TDDfossasia/eventyay-interpretation1.6k28 repos~1.1kAutomated safety check: PassApache-2.0
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT
Test Driven Developmentfarm-fe/farm5.6k49 repos~2.5kAutomated safety check: PassMIT
Tapd Story PipelineTencentBlueKing/bk-bcs840—~2.6kAutomated safety check: PassCustom licence

Similar skills

  • TDD

    fossasia/eventyay-interpretation

    Test-driven development. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 28 repos~1.1k tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed

  • Test Driven Development

    farm-fe/farm

    A skill your agent uses when implementing any feature or bugfix, before writing implementation code

    5.6k GitHub starsUsed in 49 repos~2.5k tokens
    Testing & QAAuto-check passed

  • Tapd Story Pipeline

    TencentBlueKing/bk-bcs

    单需求实现流水线——把一个 TAPD 需求从零推进到代码提交。自动串联技术澄清、 开发计划、任务拆分、TDD 实现、架构/安全校验、代码提交六个阶段。

    840 GitHub stars~2.6k tokensUpdated 13 days ago
    Testing & QAAuto-check passed

  • Absolute Init

    maddhruv/absolute

    One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write .absolute.config.json (project…

    218 GitHub starsUsed in 1 repo~3k tokens
    Testing & QAAuto-check passed

More from cloudnative-co/claude-code-starter-kit

All 8 skills in this repo

  • Eval Harness

    cloudnative-co/claude-code-starter-kit

    Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles.

    151 GitHub starsUsed in 10 repos~1.3k tokens
    Auto-check passed

  • Web Content Extraction

    cloudnative-co/claude-code-starter-kit

    Web取得の標準前処理レイヤー。URL・公式ドキュメント・ブログ・ニュース・OSSページを読むときは、原則として毎回このSkillでDefuddleを使い本文をMarkdown/JSON化してから読む。生HTMLのまま要約・分析・比較・レビューしない。トリガー例: URLを読む/Webページ要約/OSS調査/公式Doc確認/記事解析/競合サイト確認/Web一次情報確認。

    151 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Project Guidelines Example

    cloudnative-co/claude-code-starter-kit

    Example project-specific skill template. An agent skill from cloudnative-co/claude-code-starter-kit.

    151 GitHub stars~446 tokensUpdated today
    Auto-check passed

  • Prompt Patterns

    cloudnative-co/claude-code-starter-kit

    Practical prompt patterns and techniques for effective Claude Code usage.

    151 GitHub stars~887 tokensUpdated today
    Auto-check passed

  • Verification Loop

    cloudnative-co/claude-code-starter-kit

    Comprehensive verification system for Claude Code sessions. An agent skill from cloudnative-co/claude-code-starter-kit.

    151 GitHub stars~733 tokensUpdated today
    Auto-check passed

  • Cloudnative Writing Baseline

    cloudnative-co/claude-code-starter-kit

    日本語の業務文書を作成・修正するときに使用する共通品質基準。事実性、確度、論理、簡潔さ、自然な日本語を守る。提案書、報告、技術説明、議事録、メール、Slack、要約、レビューに適用する。創作、広告コピー、コードや構造化データだけの生成には使用しない。

    151 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Categories

Questions about TDD Workflow

What does TDD Workflow do?

A skill your agent uses when the user explicitly asks for TDD or a tests-first workflow, or when developing a new feature with a test coverage requirement. TDD Workflow is an agent skill from cloudnative-co/claude-code-starter-kit. Use this skill when the user explicitly asks for TDD or a tests-first workflow, or when developing a new feature with a test coverage requirement.

When should I use TDD Workflow?

TDD Workflow fits situations like: the user explicitly asks for TDD; A tests-first workflow; developing a new feature with a test coverage requirement.

How do I install TDD Workflow in Claude Code?

Run `npx skills add cloudnative-co/claude-code-starter-kit --skill tdd-workflow -a claude-code`. Or copy the skill folder (skills/tdd-workflow in cloudnative-co/claude-code-starter-kit) into .claude/skills/tdd-workflow in your project. Claude Code loads it when a task matches its description.

How do I install TDD Workflow in Codex?

Run `npx skills add cloudnative-co/claude-code-starter-kit --skill tdd-workflow -a codex`. Or copy the skill folder (skills/tdd-workflow in cloudnative-co/claude-code-starter-kit) into .agents/skills/tdd-workflow in your project. Codex loads it when a task matches its description.

Can I use TDD Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cloudnative-co/claude-code-starter-kit --skill tdd-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tdd-workflow, .gemini/skills/tdd-workflow, .github/skills/tdd-workflow and .opencode/skills/tdd-workflow in your project.

What does TDD Workflow need to run?

Going by SKILL.md and its folder, TDD Workflow needs a shell for the scripts in its folder and the command-line tools its instructions call (npm, pytest and bash). Our summary lists: Python 3; Node.js; A Bash shell.

Does TDD Workflow access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is TDD Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does TDD Workflow use?

TDD Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TDD Workflow use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to TDD Workflow?

Skills that share tags, products or a category with TDD Workflow: TDD (fossasia/eventyay-interpretation, 1.6k stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD (sanity-io/sanity, 6.4k stars) and Test Driven Development (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TDD Workflow?

cloudnative-co (a GitHub organization) maintains it in cloudnative-co/claude-code-starter-kit, which has 151 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.

Source: cloudnative-co/claude-code-starter-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.