Claude Code Plugins

Community-maintained marketplace

Feedback

tdd-typescript

@settlemint/agent-marketplace
0
0

Default test workflow. RED-GREEN-REFACTOR cycle for all new TypeScript code.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name tdd-typescript
description Default test workflow. RED-GREEN-REFACTOR cycle for all new TypeScript code.
triggers implement, add.*feature, build.*feature, create.*function, new.*endpoint, write.*test, tdd
Enforce strict Test-Driven Development (TDD) workflow for TypeScript implementations. Every code change follows the RED-GREEN-REFACTOR cycle where tests are written BEFORE implementation code. This skill orchestrates the TDD phases and ensures test-first discipline. **The TDD Discipline**

TDD is not about testing—it's about design. Writing tests first forces you to think about the API, edge cases, and behavior BEFORE writing implementation code.

Three Laws of TDD:

  1. Write NO production code until a failing test exists
  2. Write ONLY enough test to demonstrate failure
  3. Write ONLY enough production code to pass the test

Coverage Requirements (Non-Negotiable):

Metric Minimum Critical Paths
Line coverage 80% 100%
Branch coverage 75% 100%
Function coverage 90% 100%

Coverage targets are minimum thresholds, not aspirational goals. See references/test-coverage-patterns.md for blocking criteria.

Context Isolation: Each phase (RED, GREEN, REFACTOR) runs with isolated context. The test writer cannot see implementation plans—this ensures genuinely test-first thinking rather than tests designed around anticipated code.

Phase Gates: Do NOT proceed to the next phase until the current phase verification succeeds:

  • RED → Test must FAIL before proceeding to GREEN
  • GREEN → Test must PASS before proceeding to REFACTOR
  • REFACTOR → Tests must STILL PASS after changes

See references/test-strategy-checklist.md for complete phase gate requirements.

**For any implementation task:**
  1. Read workflows/tdd-cycle.md and follow it exactly
  2. Use references/test-coverage-patterns.md for coverage targets and blocking criteria
  3. Use references/test-data-strategies.md for factories, fixtures, and mocks
  4. Use references/test-naming-conventions.md for consistent naming
  5. Use references/test-strategy-checklist.md for phase gates and governance

Invoke with: Any prompt containing "implement", "add feature", "build", or "create functionality"

| Workflow | Purpose | |----------|---------| | tdd-cycle.md | Complete RED-GREEN-REFACTOR cycle for feature implementation | | Reference | Content | |-----------|---------| | test-coverage-patterns.md | Coverage targets, blocking criteria, priority analysis, test categories | | test-naming-conventions.md | Naming conventions, test structure patterns | | test-data-strategies.md | Factories, fixtures, mocks, determinism patterns | | test-strategy-checklist.md | Phase gates, test pyramid, coverage matrix, anti-patterns | | project-setup.md | CLAUDE.md instructions and hook configuration for enforcement | **Works with:** `devtools:vitest` skill for test syntax and assertions

This skill handles the TDD WORKFLOW (when/what to test). The vitest skill handles TEST SYNTAX (how to write tests). Load both for full coverage.

TDD workflow complete when:
  • RED: Failing test written BEFORE any implementation
  • GREEN: Minimal code written to pass test
  • REFACTOR: Code improved while tests stay green
  • Coverage: 80%+ lines, 75%+ branches, 100% critical paths
  • Test data: Factories for dynamic, fixtures for edge cases, mocks at boundaries
  • Naming: Tests follow should_<expected>_when_<condition> pattern
  • Gates: All phase gate criteria met (see test-strategy-checklist.md)