tdd-guide

325 stars 73 forks
0
D

Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation

CommandsAgents
#Driven Development#claude-skills-creator#ai-agents#claude-code#Test Driven#TDD workflow#claude-ai#claude-skills
Also in: data analysis

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install alirezarezvani/claude-code-skill-factory/tdd-guide
skilz install alirezarezvani/claude-code-skill-factory/tdd-guide --agent opencode
skilz install alirezarezvani/claude-code-skill-factory/tdd-guide --agent codex
skilz install alirezarezvani/claude-code-skill-factory/tdd-guide --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/alirezarezvani/claude-code-skill-factory
2. Copy the agent skill directory:
cp -r claude-code-skill-factory/generated-skills/tdd-guide ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Stars
325
Forks
73
Type
Technical
Meta-Domain
development
Primary Domain
testing
Market Score
0

Agent Skill Grade

D
Score: 67/100 Click to see breakdown

Score Breakdown

Spec Compliance
11/15
PDA Architecture
15/30
Ease of Use
18/25
Writing Style
4/10
Utility
15/20
Modifiers: +4

Areas to Improve

  • Description needs trigger phrases
  • No References Directory (PDA Violation)
  • Missing TOC for 288-Line File

Recommendations

  • Focus on improving Pda (currently 15/30)
  • Focus on improving Writing Style (currently 4/10)
  • Address 3 high-severity issues first

Graded: 2026-01-24

Developer Feedback

I've been digging through skill implementations and noticed your TDD guide takes a pretty opinionated stance on test structure—curious what made you prioritize that particular organization over the more common pyramid approach?

Links:

The TL;DR

You're at 67/100, solidly in D territory. This is based on Anthropic's Progressive Disclosure Architecture standards and the 5-pillar rubric used across skill evaluation. Your Utility section is strong (15/20)—the actual problem-solving power is there. But Writing Style (4/10) and PDA structure (15/30) are dragging you down hard. Fix those two pillars and you're looking at a solid B.

What's Working Well

  • Real utility: You're addressing actual TDD gaps (coverage analysis, test generation, multi-framework support). This isn't theoretical stuff.
  • Good trigger terms: @tdd-guide, "run tdd guide" are clear discovery hooks.
  • Framework flexibility: Supporting Jest, Pytest, JUnit, Vitest shows you understand developers work in different ecosystems.
  • Structured sections: Your Best Practices section with numbered steps shows you understand workflow clarity.

The Big One: 288 Lines in a Single File (No References Directory)

This is your biggest blocker. Right now everything lives in one SKILL.md file—no layered structure, no references directory. This violates PDA (Progressive Disclosure Architecture) and kills your token efficiency score.

Why it matters: Skills over ~100 lines need to split content into separate files. Scripts, examples, detailed framework configs, and workflows should live in references/ subdirectory. This lets users pull in only what they need instead of parsing the whole thing.

The fix: Creat...

AI-Detected Topics

Extracted using NLP analysis

Driven Development claude-skills-creator ai-agents claude-code Test Driven TDD workflow claude-ai claude-skills ai-tools coverage

Report Security Issue

Found a security vulnerability in this agent skill?