An elite collection of specialized AI sub-agents that transform Claude Code into a powerhouse development environment. These agents work individually or collaboratively to handle everything from code review to design system extraction.
- Overview
- Installation
- Available Agents
- Usage Guide
- Agent Collaboration
- Best Practices
- Examples
- Contributing
This repository contains a carefully crafted collection of Claude Code sub-agents and powerful slash commands, each specialized in specific development tasks.
- π Auto-activate based on context
- π€ Collaborate on complex tasks
- π Improve code quality dramatically
- β‘ Accelerate development speed
- π¨ Extract design systems from screenshots
- π Quality sprints - Comprehensive code improvement
- π¨ Design-to-code - Transform mockups to components
- π Full-stack features - Complete feature implementation
- π Debug workflows - Systematic error resolution
- π API-first development - Design-driven API creation
- Clone this repository:
git clone https://github.com/yourusername/awesome-claude-code-agents.git
cd awesome-claude-code-agents-
The agents are already in the correct location (
.claude/agents/). They're ready to use immediately! -
Verify installation:
ls .claude/agents/*.mdPowerful commands that orchestrate multiple agents for complete workflows:
Comprehensive code quality improvement using multiple agents in sequence.
quality-sprint @src/ # Analyze and improve entire directoryTransform mockups into production components with extracted design systems.
design-to-code @mockup.png --framework reactImplement complete features with backend, frontend, tests, and docs.
full-stack-feature "user authentication"Systematic debugging with root cause analysis and prevention.
debug-and-fix "TypeError: Cannot read property"Design-first API development with OpenAPI spec and full implementation.
api-first "user management API" --restExpert code review specialist that proactively reviews code for quality, security, and maintainability.
- Auto-triggers: After file saves, before commits, during refactoring
- Specialties: Security vulnerabilities, performance issues, code smells, SOLID principles
- Example:
"Review my recent changes"or auto-activates on git diff
Elite debugging specialist for errors, test failures, and unexpected behavior.
- Auto-triggers: On errors, test failures, exceptions
- Specialties: Root cause analysis, stack trace interpretation, systematic problem-solving
- Example:
"Debug this error: TypeError: Cannot read property..."
Comprehensive test creation specialist generating unit, integration, and E2E tests.
- Auto-triggers: After new functions/classes, low test coverage
- Specialties: Edge cases, mocking strategies, test patterns, high coverage
- Example:
"Generate tests for the UserService class"
Professional documentation specialist for READMEs, APIs, and code comments.
- Auto-triggers: After code changes, missing documentation
- Specialties: API docs, architecture diagrams, user guides, JSDoc/docstrings
- Example:
"Document the payment processing module"
Code improvement specialist mastering clean code principles and design patterns.
- Auto-triggers: Code smells detected, before major features
- Specialties: SOLID principles, performance optimization, technical debt reduction
- Example:
"Refactor this function to be more maintainable"
Elite Python specialist mastering advanced features and Pythonic patterns.
- Specialties: Decorators, generators, async/await, type hints, context managers
- Frameworks: FastAPI, Django, Flask, asyncio
- Example:
"Implement an async rate limiter in Python"
TypeScript master pushing the type system to its limits.
- Specialties: Advanced types, generics, decorators, type-level programming
- Frameworks: React, Node.js, Angular, Vue
- Example:
"Create type-safe API client with full inference"
Extracts comprehensive design systems from screenshots.
- Auto-triggers: When implementing UI from designs
- Specialties: Color extraction, typography analysis, spacing systems, component patterns
- Output: Design tokens, Tailwind config, React components
- Example:
"Extract design system from @screenshot.png"
Agents automatically activate based on context:
# Writing a new function triggers documentation-writer
def process_payment(amount, card):
# Agent will suggest comprehensive documentation
pass
# Making changes triggers code-reviewer
# The agent will automatically review for quality and security
# Encountering an error triggers debugger
# Agent will analyze and provide solutionMention the agent by name:
"Use the code-reviewer to check my PaymentService class"
"Have the test-generator create integration tests for the API"
"Get the python-expert to optimize this data processing pipeline"
"Review and refactor this module"
# Activates: code-reviewer β refactoring-expert
"Debug and fix with tests"
# Activates: debugger β test-generator
"Document and review the architecture"
# Activates: documentation-writer β code-reviewer
graph LR
A[code-reviewer] --> B[refactoring-expert]
B --> C[test-generator]
C --> D[documentation-writer]
Example: "Improve code quality"
- code-reviewer identifies issues
- refactoring-expert implements improvements
- test-generator ensures coverage
- documentation-writer updates docs
Multiple agents can work simultaneously:
- Performance optimization: python-expert + refactoring-expert
- Full feature: typescript-expert + test-generator + documentation-writer
graph LR
A[Developer] --> B[Implementation]
B --> C[code-reviewer]
C --> D{Issues Found?}
D -->|Yes| E[refactoring-expert]
E --> C
D -->|No| F[Complete]
- Trust the automatic triggers
- Agents know when they're needed
- Reduces cognitive load
β "Fix this"
β
"Debug the authentication error in login.js line 45"
β "Make it better"
β
"Refactor for better error handling and add logging"
- Use language experts for language-specific features
- Use code-reviewer before commits
- Use test-generator for critical paths
- Review β Refactor β Test β Document
- Debug β Fix β Test β Review
- Include error messages
- Mention frameworks/libraries
- Specify requirements
User: "Implement user authentication with JWT"
Agents activated:
1. typescript-expert - Creates type-safe auth service
2. test-generator - Generates comprehensive test suite
3. documentation-writer - Documents API endpoints
4. code-reviewer - Ensures security best practices
User: "Getting 'undefined is not a function' in checkout process"
Agents activated:
1. debugger - Identifies root cause
2. typescript-expert - Implements type-safe fix
3. test-generator - Creates regression test
4. code-reviewer - Validates the fix
User: "Implement this design @dashboard-mockup.png"
Agents activated:
1. visual-design-extractor - Extracts design system
2. typescript-expert - Creates React components
3. documentation-writer - Documents component API
User: "The data processing is too slow"
Agents activated:
1. python-expert - Analyzes bottlenecks
2. refactoring-expert - Implements optimizations
3. test-generator - Ensures functionality preserved
4. documentation-writer - Documents performance improvements
Create your own agent combinations:
# Quality sprint
"Run a comprehensive quality improvement on the codebase"
# Activates all quality-focused agents in sequence
# Security audit
"Perform security review with fixes"
# code-reviewer (security focus) β refactoring-expert β test-generator
# Documentation sprint
"Generate complete documentation for the API"
# documentation-writer β code-reviewer β visual diagramsSome agents excel in specific scenarios:
| Scenario | Best Agent(s) |
|---|---|
| Memory leaks | debugger + python-expert |
| Type errors | typescript-expert |
| API design | documentation-writer + code-reviewer |
| UI from mockup | visual-design-extractor |
| Test coverage | test-generator |
| Code smells | refactoring-expert |
- Check if the agent file exists in
.claude/agents/ - Be more specific in your request
- Manually invoke with "Use [agent-name] to..."
- Provide more context
- Explicitly mention the desired agent
- Use specific keywords related to the agent's expertise
- Normal! Different specialists may have different approaches
- Ask for clarification: "Reconcile the suggestions from code-reviewer and refactoring-expert"
Coming soon:
- go-expert - Go language specialist
- react-expert - React framework specialist
- security-auditor - Security vulnerability specialist
- performance-optimizer - Performance bottleneck eliminator
- ai-engineer - LLM integration specialist
Want to add your own agents? Follow these guidelines:
- Create agent file:
.claude/agents/your-agent.md - Use the required format:
---
name: agent-name
description: Clear description of when to use this agent
tools: Read, Write, Edit, etc.
---
Agent system prompt...- Make agents:
- Focused on one expertise area
- Proactive with clear triggers
- Provide actionable output
- Include examples
MIT License - see LICENSE file