A Claude Code plugin that ships a TDD knowledge base as an on-demand knowledge skill, distilled from cover-to-cover readings of Kent Beck's Test-Driven Development: By Example (2003) and Vladimir Khorikov's Unit Testing: Principles, Practices, and Patterns (2020). It answers the WHY behind test design decisions: when to mock, what makes a good test, classical vs London school, observable behavior vs implementation details, test doubles, coverage metrics, testable architecture, and more.
Invoke it with /tdd:principles <question or concept>, or let Claude load it
automatically when you ask a test design question.
- Routing table. A hub SKILL.md routes each question to one of fourteen author-attributed reference files (Beck methodology, Khorikov four pillars, test doubles, testable architecture, integration testing, anti-patterns, worked examples, and more), so only the relevant slice loads.
- Quick decision guide. One-line answers to the twelve most common test design questions, with no reference file load needed.
- Author attribution throughout. Shared concepts carry attributed
sections with synthesis where the authors overlap; single-author concepts
are named
{concept}-{author}.md.
This skill is knowledge (WHY behind testing decisions), not workflow (HOW to run tests). It never runs, scaffolds, or filters tests. Your project's own test tooling and conventions own that; this skill informs the design decisions those workflows execute.
/plugin marketplace add melodic-software/claude-code-plugins
/plugin install tdd@melodic-softwareThis plugin has no userConfig. It is a pure knowledge skill: nothing to
configure, no state, no scripts, no network access.
MIT (SPDX-License-Identifier: MIT).