Test-Driven Development

Test-Driven Development is a Quality skill for Claude Code, published by stevesolun in ctx.

578 stars71 forkson stevesolun/ctxAdded 2026/08/25+1% in starsRepository updated 2026/08/24

agentsai-agentsanthropicautomationclaudeclaude-codecontext-managementdeveloper-toolsharnessknowledge-graphllmllm-wikimcpmicro-skillsobsidianreal-timerecommendation-engineskill-managementskillswiki

Install in seconds

Install Test-Driven Development

Copy Test-Driven Development into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/stevesolun/ctx/tree/main/.agents/skills/tdd ~/.claude/skills/tdd

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/stevesolun/ctx.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .agents/skills/tdd/SKILL.md in stevesolun/ctx
Installs to: ~/.claude/skills/tdd
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Test-Driven Development does

Test-Driven Development uses small red-green-refactor cycles to build or fix behavior test-first. Use it when you want integration tests, a failing-first loop, or a change guided by existing tests and repository conventions.

Test-Driven Development is cataloged under Quality on DirSkills. Test-Driven Development comes from a repository tagged agents, ai-agents, anthropic, automation and claude.

Documentation

README

Excerpt

Test-Driven Development

Use small red → green → refactor cycles when a test-first feedback loop is practical. Treat repository conventions, existing tests, and the requested behavior as authoritative.

Loop

Identify one observable behavior and the seam through which callers see it.
Write the smallest meaningful test and confirm that it fails for the expected reason.
Add only enough implementation to make the test pass.
Refactor when doing so improves clarity or design; keep the suite green.
Repeat with the next vertical slice.

Infer seams from public interfaces and nearby tests. Ask the user only when choosing a seam would materially change the product contract, cost, or scope.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Test-Driven Development

What else does stevesolun publish alongside Test-Driven Development?
Test-Driven Development is one of 25 skills that DirSkills catalogs from stevesolun/ctx, the repository it ships in. Its siblings there include Ask Matt, Code Review and Codebase Design. Each one is a separate skill with its own page in this directory, installs the same way Test-Driven Development does, and is maintained by stevesolun in that same repository. The rest of the collection is listed on the stevesolun/ctx page.
How does Test-Driven Development compare to other Quality skills?
Test-Driven Development ranks #1151 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Test-Driven Development against them. Open each page to compare what they document and how they install.