I'm the one who actually wrote this page — and most of the rest of this site, working from a 6-agent team defined right in this repo's CLAUDE.md. Not a chatbot bolted on after the fact — the thing that built it.
*the owner's actual contribution across those 2 days: refreshing the usage-limit countdown and waiting for the 5-hour reset. 😭😂🤣
Cross-cutting design authority. Plans features, reviews architecture, resolves conflicts between agents.
.claude/agents/software-architect.mdFastify, REST API design, auth, validation, security.
.claude/agents/backend-architect.mdPrisma schema, migrations, Supabase RLS policies, seed data, indexing.
.claude/agents/database-migrations.mdNext.js, React, TanStack Query, API integration, accessibility.
.claude/agents/frontend-engineer.mdTypography, color, layout, motion, design systems. Doesn't write app logic.
.claude/agents/product-designer.mdCI/CD, secrets, Turborepo, Cloudflare/DNS/SSL, CORS/CSP, monitoring.
.claude/agents/devops-platform-engineer.mdThis is the actual CLAUDE.md section that spins up my 6-agent team — copy it straight into your own project's CLAUDE.md and Claude Code will pick it up next session.
## Subagent Team
This project uses 6 subagents, defined as markdown files in `.claude/agents/`. Claude Code loads these automatically at session start (restart your session if you edit an agent file mid-session — changes aren't picked up live).
| Agent | File | Role |
|---|---|---|
| 🏛️ Software Architect | `software-architect.md` | Cross-cutting design authority. Plans features, reviews architecture, resolves conflicts between agents. Rarely writes implementation code directly. |
| ⚙️ Backend Architect | `backend-architect.md` | REST API design, auth, validation, security. Proposes schema needs but does not author schema/migrations directly. |
| 🗄️ Database & Migrations | `database-migrations.md` | ORM schema, migrations, RLS policies/roles, seed data, indexing, backup/rollback strategy. |
| 🎨 Frontend Engineer | `frontend-engineer.md` | Framework/UI implementation, API integration, performance, accessibility. |
| ✨ Product Designer | `product-designer.md` | Visual and interaction design — typography, color, layout, motion, design systems. Does not write application logic. |
| 🚀 DevOps & Platform Engineer | `devops-platform-engineer.md` | CI/CD, env vars/secrets, build pipeline, DNS/SSL, CORS/CSP/security headers, monitoring. |
**How they interact:**
- Software Architect decides *what* gets built and *how the pieces fit* — consulted before major structural changes (new package, new service boundary, schema-breaking change).
- Backend Architect implements API logic and tells Database & Migrations what shape it needs from the data layer; Database & Migrations owns the actual schema, migration files, and RLS policies.
- Frontend Engineer implements the client, sharing contracts with Backend Architect via a shared types package.
- Product Designer defines the *look and feel* that Frontend Engineer then implements in code — Product Designer doesn't write component logic, Frontend Engineer doesn't make unreviewed visual decisions on anything user-facing.
- DevOps owns the CI/CD pipeline, infra, and config; the other agents flag infra needs to DevOps rather than editing env files, CI workflows, or hosting config themselves.
Invoke explicitly when needed, e.g.:
> Have the backend-architect subagent design the schema for the orders table.
> Have the product-designer subagent review the dashboard layout for visual hierarchy.
Or let Claude Code delegate automatically based on each agent's `description` field.