Tool-specific rules in this file are a bootstrap only.

Authoritative instructions live in scoped `AGENTS.md` files.

Always read in this order:
1. Root `AGENTS.md`
2. The nearest scoped `AGENTS.md` for the files you read or change

Start with:
- [AGENTS.md](AGENTS.md)
- [internal/storage/AGENTS.md](internal/storage/AGENTS.md)
- [apps/cli-journey-e2e/AGENTS.md](apps/cli-journey-e2e/AGENTS.md)

Minting a resource ID? Never write custom ULID/UUID helpers — the canonical
minting contract lives in
[internal/storage/AGENTS.md](internal/storage/AGENTS.md) (context:
[ADR 047](docs/adrs/047-dialect-id-generation.md)).

Building console or design-system UI (from Figma or otherwise)? Before you
edit `apps/console/**` or `packages/{components,ui-react,shared-component-styles,design-tokens}/**`,
read these first and classify the component before building — do not
reverse-engineer a flattened app mock:
- [apps/console/docs/styling.md](apps/console/docs/styling.md) — where a
  component lives decides how it's styled (console-local utilities vs a
  Lit+React pair); the 3-way decision and token authority.
- [apps/storybook/AGENTS.md](apps/storybook/AGENTS.md) — the Figma→pair recipe
  and the parity gate (only when it's a shared primitive the login surface needs).