Guides test-driven development with red-green-refactor workflow, test design principles, isolation, and data management. Includes 42 prioritized rules for writing tests first.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pproenca-dot-skills-1:tddThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive guide to Test-Driven Development practices, designed for AI agents and LLMs. Contains 42 rules across 8 categories, prioritized by impact to guide test writing, refactoring, and code generation.
Comprehensive guide to Test-Driven Development practices, designed for AI agents and LLMs. Contains 42 rules across 8 categories, prioritized by impact to guide test writing, refactoring, and code generation.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Red-Green-Refactor Cycle | CRITICAL | cycle- |
| 2 | Test Design Principles | CRITICAL | design- |
| 3 | Test Isolation & Dependencies | HIGH | isolate- |
| 4 | Test Data Management | HIGH | data- |
| 5 | Assertions & Verification | MEDIUM | assert- |
| 6 | Test Organization & Structure | MEDIUM | org- |
| 7 | Test Performance & Reliability | MEDIUM | perf- |
| 8 | Test Pyramid & Strategy | LOW | strat- |
cycle-write-test-first - Write the Test Before the Implementationcycle-minimal-code-to-pass - Write Only Enough Code to Pass the Testcycle-refactor-after-green - Refactor Immediately After Greencycle-verify-test-fails-first - Verify the Test Fails Before Writing Codecycle-small-increments - Take Small Incremental Stepscycle-maintain-test-list - Maintain a Test Listdesign-test-behavior-not-implementation - Test Behavior Not Implementationdesign-one-assertion-per-test - One Logical Assertion Per Testdesign-descriptive-test-names - Use Descriptive Test Namesdesign-aaa-pattern - Follow the Arrange-Act-Assert Patterndesign-test-edge-cases - Test Edge Cases and Boundariesdesign-avoid-logic-in-tests - Avoid Logic in Testsisolate-mock-external-dependencies - Mock External Dependenciesisolate-no-shared-state - Avoid Shared Mutable State Between Testsisolate-deterministic-tests - Write Deterministic Testsisolate-prefer-stubs-over-mocks - Prefer Stubs Over Mocks for Queriesisolate-use-dependency-injection - Use Dependency Injection for Testabilitydata-use-factories - Use Factories for Test Data Creationdata-minimal-setup - Keep Test Setup Minimaldata-avoid-mystery-guests - Avoid Mystery Guestsdata-unique-identifiers - Use Unique Identifiers Per Testdata-builder-pattern - Use Builder Pattern for Complex Objectsassert-specific-assertions - Use Specific Assertionsassert-error-messages - Assert on Error Messages and Typesassert-no-assertions-antipattern - Every Test Must Have Assertionsassert-custom-matchers - Create Custom Matchers for Domain Assertionsassert-snapshot-testing - Use Snapshot Testing Judiciouslyorg-group-by-behavior - Group Tests by Behavior Not Methodorg-file-structure - Follow Consistent Test File Structureorg-setup-teardown - Use Setup and Teardown Hooks Appropriatelyorg-test-utilities - Extract Reusable Test Utilitiesorg-parameterized-tests - Use Parameterized Tests for Variationsperf-fast-unit-tests - Keep Unit Tests Under 100msperf-avoid-network-calls - Eliminate Network Calls in Unit Testsperf-fix-flaky-tests - Fix Flaky Tests Immediatelyperf-parallelize-tests - Parallelize Independent Testsperf-avoid-sleep - Avoid Arbitrary Sleep Callsstrat-test-pyramid - Follow the Test Pyramidstrat-mutation-testing - Use Mutation Testing to Validate Test Qualitystrat-coverage-targets - Set Meaningful Coverage Targetsstrat-integration-boundaries - Test Integration at Service Boundariesstrat-e2e-critical-paths - Limit E2E Tests to Critical User PathsRead individual reference files for detailed explanations and code examples:
vitest skillmsw skillFor the complete guide with all rules expanded: AGENTS.md
npx claudepluginhub joshuarweaver/cascade-code-general-misc-1 --plugin pproenca-dot-skills-1Guides the RED-GREEN-REFACTOR TDD cycle with principles, AAA pattern, test prioritization, and anti-patterns. Useful when writing tests before code.
Guides TDD cycles (red-green-refactor), outside-in double-loop architecture, test isolation, and naming. Useful when writing test plans or reviewing test quality.
Enforces strict red-green-refactor TDD cycle with automated test specification, failure verification, coverage thresholds, and refactoring triggers for developers practicing test-driven development.