Test Driven Development

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

43 stars 13 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lifangda/claude-plugins

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lifangda/claude-plugins --skill test-driven-development
Manual install
git clone --depth 1 https://github.com/lifangda/claude-plugins.git /tmp/claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/claude-plugins/cli-tool/skills-library/development-workflows/test-driven-development ~/.claude/skills/test-driven-development

Personal 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)

## Overview

Write the test first. Watch it fail. Write minimal code to pass.

**Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.

**Violating the letter of the rules is violating the spirit of the rules.**

## When to Use

**Always:**
- New features
- Bug fixes
- Refactoring
- Behavior changes

**Exceptions (ask your human partner):**
- Throwaway prototypes
- Generated code
- Configuration files

Thinking "skip TDD just this once"? Stop. That's rationalization.

## The Iron Law

```
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
```

Write code before the test? Delete it. Start over.

**No exceptions:**
- Don't keep it as "reference"
- Don't "adapt" it while writing tests
- Don't look at it
- Delete means delete

Implement fresh from tests. Period.

## Red-Green-Refactor
Read the full skill on GitHub

Details

Skill name
test-driven-development
Path
cli-tool/skills-library/development-workflows/test-driven-development/SKILL.md
License
MIT
Repo updated
29 October 2025
Copies
Found in 2 GitHub repos

FAQ

What does the Test Driven Development skill do?

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

How do I install the Test Driven Development skill?

Claude Code plugin: /plugin marketplace add lifangda/claude-plugins. 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 lifangda/claude-plugins, which has 43 GitHub stars and 13 forks.

Related skills

Video Downloader

43

lifangda/claude-plugins

Downloads videos from YouTube and other platforms for offline viewing, editing, or archival. Handles various formats and quality options.

Images, Video & Audio13

Aeon

43

lifangda/claude-plugins

Time series machine learning toolkit for classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use this skill when working with temporal data, performing time series analysis, building predictive models on sequential data, or implementing workflows that involve distance metrics (DTW), transformations (ROCKET, Catch22), or deep learning for time series. Applicable for tasks like ECG classification, stock price forecasting, sensor anomaly detection, or activity recognition from wearable devices.

Learning & Education13

Algorithmic Art Generation

43

lifangda/claude-plugins

Create algorithmic art using p5.js with seeded randomness, flow fields, and particle systems. Use when you need to generate generative art, create computational aesthetics, or build interactive artistic visualizations. Automatically activates when discussing: "generative art", "algorithmic art", "p5.js visualization", "computational aesthetics".

Images, Video & Audio13

Adversarial Review

42

robbyt/claude-skills

Have Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (

Software Development

Hard Call

40

ArogyaReddy/alirezarezvani-claude-skills

/em -hard-call — Framework for Decisions With No Good Options

Software Development11

API Review

42

robbyt/claude-skills

This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions",

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.