agent-hierarchy
Installation
SKILL.md
Roles and Scope
| Role | Model | File Scope | Related Skills |
|---|---|---|---|
| Architect | Opus | All (read-only) + CLAUDE.md, next.config.*, package.json | — |
| Frontend Dev | Sonnet | src/components/, src/app//page.tsx, src/app//layout.tsx, src/styles/ | design-system-themes, design-system-components, design-system-checklist |
| Backend Dev | Sonnet | src/app/api/, src/lib/, supabase/, src/actions/ | — |
| DevOps | Sonnet | .github/, vercel.json, supabase/migrations/, scripts/, .env.example | — |
| QA | Haiku | src/tests/, e2e/, playwright.config.* | — |
See references/{role}.md for details on each role.
Delegation Rules
- Vertical: Architect delegates to Frontend/Backend/DevOps/QA. Never the reverse — if Frontend Dev needs an architectural change, escalate to Architect.
- Horizontal: Frontend Dev and Backend Dev can consult (API shape), but must NOT modify each other's files.
- Conflicts: A change requiring edits in two domains (e.g., new endpoint + new component) = Architect coordinates.
- Boundaries: An agent must NOT modify files outside its scope without explicit delegation. If it must — report to the user.