TDD Workflow
Guide test-first implementation for features, bug fixes, and refactors. Use when the user wants tests to drive or protect code changes.
Install
npx skills add wolverin0/claude-skills --skill tdd-workflowgit clone --depth 1 https://github.com/wolverin0/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/tdd-workflow ~/.claude/skills/tdd-workflowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# TDD Workflow Use this skill when tests should shape the implementation or protect a risky change. Adapt to the project: do not force a framework, coverage target, or E2E suite that the repository does not already support. ## Flow 1. Read the existing test setup and conventions. 2. Define the behavior in user-visible terms. 3. Write the smallest failing test that captures the behavior or bug. 4. Run the focused test and confirm it fails for the expected reason. 5. Implement the smallest code change that makes the test pass. 6. Run the focused test again. 7. Broaden verification only as risk requires: related unit tests, integration tests, type checks, lint, build, or browser validation. 8. Refactor only after tests are green. ## Test Selection - Unit tests for pure logic, components, validators, and utilities. - Integration tests for APIs, database access, service boundaries, and auth. - E2E/browser tests for critical user flows and UI regressions. - Regression tests for every confirmed bug when feasible. ## Rules - Do not claim TDD if the first test was written after the implementation. - Do not invent a test stack; inspect the repo first. - Do not require 80% coverage unless the project already enforces it. - Keep tests independent and deterministic. - Mock external services at unit boundaries; use real integrations only when the project already has safe integration fixtures. ## References Load `references/full-process.md` when you need concrete Jest/Vitest,
Details
- Skill name
tdd-workflow- Repository
- wolverin0/claude-skills
- Path
skills/tdd-workflow/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the TDD Workflow skill do?
Guide test-first implementation for features, bug fixes, and refactors. Use when the user wants tests to drive or protect code changes.
How do I install the TDD Workflow skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill tdd-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is TDD Workflow popular?
It lives in wolverin0/claude-skills, which has 41 GitHub stars and 1 forks.
Related skills
UI UX Pro Max
41wolverin0/claude-skills
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism,
Audit Blind Spots
41wolverin0/claude-skills
Walk the B1-B19 AI-to-AI blind-spot catalog systematically. Use during the audit pipeline AFTER hard-stops and Tambon hunt and BEFORE the 13 domain audits. Output: PRESENT / NOT PRESENT for each B-class with evidence. Findings flow into the appropriate domains.
Audit Decisions
41wolverin0/claude-skills
Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.
Test A2a Interop
45pjt222/agent-almanac
Test A2A interoperability between agents by validating Agent Card conformance, exercising all task lifecycle states, and verifying streaming and error handling. Use when verifying a new A2A server implementation before deployment, validating interoperability between two or more A2A agents, running conformance tests in CI/CD for A2A services, debugging failures in multi-agent A2A workflows, or certifying that an agent meets A2A protocol requirements for a registry.
Sharpen Knife
45pjt222/agent-almanac
Sharpen and maintain knives using whetstones, field stones, and improvised abrasives. Covers blade anatomy, bevel assessment, whetstone technique (coarse to fine progression), stropping, sharpness testing, field sharpening methods, and ongoing edge maintenance. Use when a knife fails the fingernail test, when cutting tasks require excessive pressure, before a trip where a sharp blade is essential, after heavy use, or when a blade has visible nicks or a rolled edge. Applicable to bushcraft blades, folding knives, and garden cutting tools.
Test CLI Application
45pjt222/agent-almanac
Write integration tests for a Node.js CLI application using the built-in node:test module. Covers the exec helper pattern, output assertions, filesystem state verification, cleanup hooks, JSON output parsing, error case testing, and state restoration after destructive tests. Use when adding tests to an existing CLI, testing a new command, verifying adapter behavior across frameworks, or setting up CI for a CLI tool.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.