Test Driven Development
Apply Test-Driven Development to drive outside-in design in small steps. Centers on the London/mockist school (Freeman & Pryce's GOOS, Sandro Mancuso's outside-in teaching) with Kent Beck's classical foundations and Mark Seemann's pragmatic heuristics. Covers sociable vs solitary unit tests and when to prefer each (anticipated refactoring → sociable). Use when starting a new feature, designing object interactions, building a vertical slice end-to-end, deciding what to test next, choosing the test boundary before refactoring, or rescuing a design that resists testing.
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill test-driven-developmentgit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/test-driven-development ~/.claude/skills/test-driven-developmentPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test-Driven Development for Outside-In Design Use TDD when starting any non-trivial feature, designing how objects collaborate, growing a system in small verifiable steps, or letting tests reveal design problems before they become expensive. This skill emphasizes **outside-in TDD** — driving the design from the user-visible boundary inward, one failing test at a time. ## Core Philosophy **TDD is a design technique, not a testing technique.** The tests are a side effect; the real product is a design that is easy to change. If tests pass but the design is rotten, TDD has failed regardless of coverage. **Listen to the tests.** Difficulty writing a test is feedback about the design, not the test. Hard-to-test code is hard-to-change code. **Small steps beat large leaps.** The discipline is to take the smallest step that visibly progresses toward the goal. Speed comes from never being stuck or rolling back significant work. **Red, Green, Refactor — in that order, every time.** Skipping a phase compounds into rot. **Outside-in over inside-out** (when the design is non-trivial). Start from the user-facing boundary and let each test pull the next collaborator into existence. This avoids speculative infrastructure and ensures every piece exists because something needs it. --- ## The TDD Cycle (Beck)
Details
- Skill name
test-driven-development- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/test-driven-development/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Test Driven Development skill do?
Apply Test-Driven Development to drive outside-in design in small steps. Centers on the London/mockist school (Freeman & Pryce's GOOS, Sandro Mancuso's outside-in teaching) with Kent Beck's classical foundations and Mark Seemann's pragmatic heuristics. Covers sociable vs solitary unit tests and when to prefer each (anticipated refactoring → sociable). Use when starting a new feature, designing object interactions, building a vertical slice end-to-end, deciding what to test next, choosing the test boundary before refactoring, or rescuing a design that resists testing.
How do I install the Test Driven Development skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Driven Development popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Test Fixer
8Freddy-CHEN-ux/00_claude_skills
MANDATORY when: tests fail, CI fails, CI/CD fails, ci.yml fails, user provides CI log URL. Investigates failures, fixes iteratively until passing.
Test Data Patterns
5vnovakovits/claude-skills
Apply the family of test arrangement patterns — Test Data Builder (Nat Pryce & Steve Freeman, GOOS 2009), Object Mother (Peter Schuh, popularised by Martin Fowler 2006), Arrange-Act-Assert (Bill Wake, 2001), Given-When-Then (Dan North, 2006), and chained Test Fixtures — that keep test setup readable, expressive, and robust to change. Covers fluent builders with sensible defaults, semantic builder methods, the Builder + Mother combination, AAA vs GWT, when to introduce a builder, anti-patterns (constructor-with-twelve-params, mystery guests, irrelevant setup), and the project's `Fixture.Given()
Test Runner
8Freddy-CHEN-ux/00_claude_skills
MANDATORY skill for running tests and lint after EVERY code change. Focuses on adherence to just commands and running tests in parallel. If tests fail, use test-fixer skill.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.