onboardinglisted

# Onboarding ## Use it (2 minutes) Open the repo in Claude Code and ask normally. `CLAUDE.md` loads automatically, Claude reads the roster and delegates. To force a specific agent, name it: > Use the `database-architect` agent to review this schema. Or route by command: `/team <task>`. ## Understand it (10 minutes) | Path | What it is | Loaded | |---|---|---| | `CLAUDE.md` | The delegation rule | Always | | `.claude/rules/*.md` | Standing standards | Always | | `.claude/teams/README.md` | Full roster with `name` values | On lookup | | `.claude/agents/<name>.md` | One agent, ten sections | When delegated to | | `.claude/commands/*.md` | Slash commands | When invoked | | `.claude/skills/*/SKILL.md` | Procedures | On demand, by description match | | `scripts/agents_data.py` | **The only file you edit** | Never — it is the source | ## First tasks to try | Goal | Say | |---|---| | Find the owner | "who handles database migrations here?" | | Review a diff | `/review` | | Design something | `/design payment retry logic` | | Pre-release check | `/ship` | | Security pass | `/audit src/api` | | Cost pass | `/cost` | ## Extend it ```bash # 1. add a record to AGENTS in scripts/agents_data.py # 2. regenerate everything python3 scripts/generate.py ``` Never hand-edit `.claude/agents/*.md` — regeneration overwrites it. That is deliberate: one source of truth is what keeps 109 agents consistent. ### What separates a good agent record from a filler one The template forces ten sec