# CLAUDE.md ## Direction Before designing or restructuring agent code, read `docs/adr/`. ADR-0002 is the anchor: behaviour lives in Agent Skills (agentskills.io format) loaded by the framework's own skill runtime, and this repo builds the tooling around them. Google Cloud is the first Cloud provider, not the only one, so cloud-specific knowledge belongs in Skills and tooling, never in the agent's core. Reach cloud environments and cloud documentation through the provider's hosted remote MCP servers, not hand-written API clients. Plans and history live in `.agents/plans/`, one directory per iteration. Before changing anything under `app/`, `agents/`, `skills/` or `eval/`, read `.agents/plans/README.md`: it lists each iteration's status and maps the module paths that specs and ADRs written before the KAB layout move still use. When you finish a step, record it there as that README describes. The design spec for iteration 2 is `.scratch/solution-architect-agent/spec.md`. ## Agent skills ### Issue tracker Issues and specs live as local markdown files under `.scratch//`. See `docs/agents/issue-tracker.md`. ### Triage labels Default five-role vocabulary (`needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`), recorded as a `Status:` line in each issue file. See `docs/agents/triage-labels.md`. ### Domain docs Single-context: one `CONTEXT.md` and `docs/adr/` at the repo root. See `docs/agents/domain.md`.