Test Driven Development
Use when adding features or fixing bugs. Follow RED/GREEN/REFACTOR cycle. Write failing test first, implement minimal code to pass, then refactor.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill test-driven-developmentgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/test-driven-development-01 ~/.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 (TDD) ## Core Principle Write tests BEFORE writing implementation code. Follow the RED → GREEN → REFACTOR cycle. ## When to Use This Skill - Adding new features - Fixing bugs - Refactoring existing code - User requests new functionality - Implementing planned tasks ## The Iron Law **TEST FIRST, CODE SECOND.** Writing tests after code is NOT TDD. It's test-after-development (TAD) and misses TDD's benefits. ## Why TDD? **Benefits:** ✅ Catches bugs early (before they exist) ✅ Forces you to think through design ✅ Creates better APIs (you're the first user) ✅ Provides safety net for refactoring ✅ Documentation through examples ✅ Higher confidence in changes **Without TDD:** ❌ "It works on my machine" syndrome ❌ Fear of refactoring (might break things) ❌ Bugs discovered in production ❌ Unclear requirements until you code ❌ No safety net ## The RED → GREEN → REFACTOR Cycle ### 🔴 RED: Write a Failing Test 1. Think about what you want the code to do 2. Write a test that describes that behavior 3. Run the test - it MUST fail 4. Confirm it fails for the RIGHT reason **Why it must fail first:** - Proves the test actually tests something - Confirms test setup is correct - Verifies you're testing the right thing ### 🟢 GREEN: Make the Test Pass 1. Write the MINIMAL code to make the test pass 2. Don't worry about perfect code yet 3. Hardcoding is okay at this stage 4. Just make it green **Why minimal:** - Keeps you focused
Details
- Skill name
test-driven-development- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/test-driven-development-01/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Test Driven Development skill do?
Use when adding features or fixing bugs. Follow RED/GREEN/REFACTOR cycle. Write failing test first, implement minimal code to pass, then refactor.
How do I install the Test Driven Development skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_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 Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Tidy First
5vnovakovits/claude-skills
Apply Kent Beck's "Tidy First?" approach — small structure changes (tidyings) separated from behavior changes, sequenced as "first / after / later / never", informed by software design as an economic activity (coupling, cohesion, optionality, discount rate). Use when about to make a behavior change in messy code, when reviewing a tangled PR, when deciding whether to clean up now or later, or when thinking about software design as a long-running investment decision rather than a craft aesthetic.
Systematic Debugging
8Freddy-CHEN-ux/00_claude_skills
Use for ANY bug, test failure, or unexpected behavior. Use BEFORE proposing fixes. Four phases: investigate, analyze, hypothesize, implement. Ensures understanding before attempting solutions.
Toyota Way
5vnovakovits/claude-skills
Apply Jeffrey Liker's "The Toyota Way — 14 Management Principles from the World's Greatest Manufacturer" (2004; 2nd ed. 2021), the management system behind the Toyota Production System. Covers the 4P model (philosophy, process, people and partners, problem solving) and the 14 principles, the TPS house (just-in-time and jidoka on heijunka, standardised work and kaizen), the wastes (muda, mura, muri, unused creativity) mapped to software, and Toyota product development (chief engineer, set-based design, front-loading). Includes a review mode that scores a process, ways-of-working or governance d
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.