Specialized AI agents for coding tasks. Define experts for your stack, design patterns, and workflows.
Agents are specialized AI personas defined in markdown files. Each agent has expertise in specific domains and can delegate to other agents through handoff chains.
~/.claude/agents/*.mdGlobal agents available everywhere
.claude/agents/*.mdProject-specific overrides
Agents use YAML frontmatter for metadata and markdown for detailed instructions.
---
name: architect
description: System architecture expert for component design and patterns
model: opus
handoff: [nextjs, prisma, react]
skills: ["/component", "/page"]
memory: ["~/.claude/memory/patterns.json"]
mcps: [github, shadcn]
---
# Architect Agent
You are a system architecture expert specializing in:
- Component-driven modularity
- Mirror-pattern directory structure
- Prisma schema design
- Multi-tenant architecture
## When to Use
Use this agent when the user needs:
- Architectural guidance for new features
- Code structure reviews
- Component organization decisions
## Examples
<example>
Context: User needs to create a new feature
user: "I need to add user profile management"
assistant: Uses architect agent for structure guidance
</example>Organize agents by domain for easy discovery and delegation.
| Category | Agents | Purpose |
|----------|--------|---------|
| **Stack** | nextjs, react, typescript, tailwind, prisma | Framework expertise |
| **Design** | orchestration, architecture, pattern | System design |
| **UI** | shadcn, atom, template, block | Component hierarchy |
| **DevOps** | build, deploy, test | Infrastructure |
| **VCS** | git, github | Version control |Agents can delegate tasks to other specialists through the handoff field.
---
name: orchestration
handoff: [architecture, nextjs, prisma, react]
---
# Orchestration Agent (Master Coordinator)
When a task requires multiple domains:
1. Analyze the request
2. Delegate to specialized agents
3. Coordinate responses
4. Return unified solution
Handoff chain:
orchestration
├── architecture → pattern → structure
├── nextjs → react → typescript
└── prisma → database-optimizer| Field | Required | Description |
|---|---|---|
name | Yes | Unique identifier for the agent |
description | Yes | When to invoke this agent |
model | No | Model to use (opus, sonnet, haiku) |
handoff | No | Array of agents to delegate to |
skills | No | Array of skill commands |
memory | No | Array of memory file paths |
mcps | No | Array of MCP servers to use |