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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontddExecute the skills CLI command in your project's root directory to begin installation:
Fetches tdd from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tdd. Access via /tdd in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
95
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
95
stars
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
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
pproenca/dot-skills
pproenca/dot-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
We added tdd from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
tdd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
tdd is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
tdd reduced setup friction for our internal harness; good balance of opinion and flexibility.
tdd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added tdd from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend tdd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for tdd matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: tdd is focused, and the summary matches what you get after install.
We added tdd from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 32