npx claudepluginhub hculap/better-codeTransform Claude Code into a strict TDD practitioner that enforces Red→Green→Refactor cycles
Parallel performance analysis tool that identifies N+1 queries, inefficient APIs, and suboptimal code patterns across your entire application stack
Generate and audit perfect READMEs using the PRD-README v1 standard
Comprehensive documentation toolkit with specialized agents for bulletproof software documentation across backend, frontend, API, database, architecture, tests, user guides, compliance, and mobile domains.
Enforce practical code quality standards with concrete rules of thumb for file sizes, function lengths, complexity, and best practices
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
Curated collection of 129 specialized Claude Code subagents organized into 10 focused categories
No description available.
Claude Code plugins that enforce code quality practices: TDD workflows, performance analysis, and documentation standards.
Status: Active | Documentation | Issues | Changelog
| Plugin | Version | Purpose |
|---|---|---|
| tdd-dev | 0.2.1 | Enforce Red→Green→Refactor TDD cycles |
| n1-optimizer | 0.1.3 | Detect N+1 queries and performance issues |
| readme-writer | 0.1.0 | Generate/audit READMEs with PRD-README v1 |
| doc-master | 0.2.1 | 9 specialized documentation agents |
Prerequisites: Claude Code CLI installed
Step 1: Add the marketplace
/plugin marketplace add hculap/better-code
Output:
Successfully added marketplace: better-code
Step 2: Install a plugin
/plugin install tdd-dev
Output:
Installed plugin: tdd-dev
Step 3: Use the plugin
/tdd-dev:start
Output:
TDD Dev Mode: ACTIVE
Configuration:
Strictness: strict
Test Command: npm test
That's it! You're now coding with TDD enforcement.
Enforces writing tests before implementation code.
/tdd-dev:start # Enable TDD mode
/tdd-dev:feature "add auth" # Implement feature with TDD
/tdd-dev:bug "fix #123" # Fix bug with regression test first
/tdd-dev:refactor # Safe refactoring verified by tests
/tdd-dev:stop # Disable TDD mode
Strictness levels: strict (tests required), standard (tests encouraged), relaxed (minimal enforcement)
Runs 4 parallel agents to analyze your codebase for performance issues.
/n1-optimizer:analyze
Output:
Analysis Complete
Database Layer: 3 issues found
HIGH: N+1 query in UserService.getOrders() - src/services/user.ts:45
Backend Layer: 1 issue found
MEDIUM: Sequential awaits could be parallelized - src/api/reports.ts:23
Frontend Layer: 2 issues found
HIGH: Missing React.memo on ExpensiveList - src/components/List.tsx:12
API Layer: 1 issue found
MEDIUM: Missing pagination on /api/products - src/routes/products.ts:8
| Agent | Detects |
|---|---|
| Database | N+1 queries, missing indexes, unbatched writes |
| Backend | O(n²) algorithms, blocking I/O, memory issues |
| Frontend | Re-render loops, large bundles, missing memoization |
| API | Over-fetching, missing pagination, chatty endpoints |
Generate or audit READMEs following the PRD-README v1 standard.
/readme-writer:generate # Generate README from codebase analysis
/readme-writer:audit # Score existing README (0-10)
Audit output:
README Audit Score: 7/10
✓ Test 1: What is it? - PASS
✓ Test 2: Is it maintained? - PASS
✗ Test 3: Quickstart works - FAIL (missing expected output)
...
9 specialized agents for comprehensive documentation.
/doc-master:setup # Choose framework (Diátaxis/Traditional/Custom)
/doc-master:generate "API" # Generate API documentation
/doc-master:audit # Audit existing docs
/doc-master:plan # Create documentation plan
| Agent | Focus |
|---|---|
| api-docs | REST/GraphQL endpoints, schemas |
| backend-docs | Services, data flows, deployment |
| frontend-docs | Components, state management |
| database-docs | Schema, migrations, ER diagrams |
| architecture-docs | System design, ADRs |
| test-docs | Test strategy, coverage |
| user-guide-docs | Tutorials, help articles |
| compliance-docs | Security, audit, regulatory |
| mobile-docs | iOS/Android, app stores |
Full documentation available in docs/:
Contributions welcome! Please open an issue first to discuss proposed changes.
Quick steps:
See individual plugin READMEs for plugin-specific guidance.