🧪
QualityRust

Test-Driven Development

by peintune

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

195 stars12 forkson peintune/runjamAdded 2026/09/06+26% in starsRepository updated 2026/09/04
View source on GitHubDownload repo ZIP
agentagent-managerai-agentai-codingclaude-codecodex-clicoding-assistantdesktop-appdeveloper-toolsgemini-clillmlocal-firstopen-sourcerustskilltaurivue3
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/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-development ~/.claude/skills/test-driven-development

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/peintune/runjam.git

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

In this catalog

Source file
src-tauri/builtin-skills/test-driven-development/SKILL.md in peintune/runjam
Installs to
~/.claude/skills/test-driven-development
Collection
One of 13 skills cataloged from this repository
Category
Quality — 1745 skills

What Test-Driven Development does

Test-Driven Development uses a red-green-refactor cycle before implementation code is written. Use it for new features, bug fixes, and behavior-changing refactors.

Test-Driven Development is cataloged under Quality on DirSkills. Test-Driven Development comes from a repository tagged agent, agent-manager, ai-agent, ai-coding and claude-code.

Documentation

README

Test-Driven Development (TDD)

Rule

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.

When to Use

Always for:

  • New features
  • Bug fixes
  • Refactoring with behavior changes

Skip only for:

  • Config file changes
  • Documentation updates
  • Non-functional changes (formatting, comments)

Process

  1. Red: Write a failing test
  2. Green: Write minimal code to pass
  3. Refactor: Clean up while keeping tests green

Anti-Patterns

  • Writing implementation before the test
  • Skipping the "watch it fail" step
  • Writing tests that are too coupled to implementation
  • Testing framework behavior instead of your code

Frequently asked about Test-Driven Development

  • What else does peintune publish alongside Test-Driven Development?

    Test-Driven Development is one of 13 skills that DirSkills catalogs from peintune/runjam, the repository it ships in. Its siblings there include Brainstorming, Code Review and Finishing A Development Branch. 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 peintune in that same repository. The rest of the collection is listed on the peintune/runjam page.

  • How does Test-Driven Development compare to other Quality skills?

    Test-Driven Development ranks #1550 by stars among the 1745 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.

More from peintune/runjam

Test-Driven Development is one of 13 skills cataloged on DirSkills from peintune/runjam.

See all 13 skills →
💡
5h ago

Brainstorming

Brainstorming guides a collaborative design process before implementation. Use it to clarify requirements, explore approaches, and write a spec before any code or behavior changes.
AI Engineering
19512
🔍
5h ago

Code Review

Code Review provides structured reviews of code changes for bugs, security issues, performance problems, and best-practice gaps. Use it when reviewing a diff and you need severity-tagged, actionable feedback without rewriting the code.
Quality
19512
✅
5h ago

Finishing A Development Branch

Finishing A Development Branch helps you prepare completed work for merge with cleanup, testing, linting, documentation updates, and a structured pull request. Use it before pushing a branch for review.
Quality
19512
🎨
5h ago

Frontend Design

Frontend Design provides guidance for distinctive UI direction when building new interfaces or reshaping existing ones. Use it to choose typography, palette, layout, and a coherent aesthetic that avoids templated defaults.
Frontend
19512
📊
5h ago

Mermaid

Mermaid renders Mermaid diagrams as SVG or ASCII art for flowcharts, sequence diagrams, state diagrams, class diagrams, and ER diagrams. Use it when you need to create or preview diagrams from Mermaid text.
Automation
19512
📄
5h ago

PDF

PDF extracts text and tables, creates and merges PDFs, and splits, rotates, or watermarks pages. Use it when Claude needs to fill forms or process PDF documents at scale.
Automation
19512

More Quality skills

Test-Driven Development is one of 1745 Quality skills cataloged on DirSkills, ranked #1550 by stars among them.

Browse all Quality skills →
⏱️
3w ago

Benchmark

Benchmark measures performance baselines, detects regressions before and after PRs, and compares stack alternatives for pages, APIs, and builds.
Quality
239.8K36.4K
⏱️
3w ago

Benchmark Optimization Loop

Benchmark Optimization Loop turns vague performance goals into a bounded, measured optimization process. Use it when asked to make something faster, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.
Quality
239.8K36.4K
🔌
3w ago

API Design Patterns

API Design Patterns provides conventions and best practices for designing consistent REST APIs. Use it when creating endpoints, reviewing contracts, handling pagination, error responses, status codes, filtering, or versioning.
Quality
239.8K36.4K