# Working on Fractal

Fractal owns canonical design policy, tokens, and approved icon source. Start agent design context at SKILL.md; the harness resolves scoped evidence through manifest.json.

For design work, start with [SKILL.md](SKILL.md) and load only the selected domain’s guidance. Read `integration/pi.md` when changing the loading contract. Repository maintenance instructions here are not part of the consumer's design prompt.

- Keep policy in shared references and task decisions in `domains/*/skills/*/SKILL.md`; do not duplicate whole policies across skills.
- Preserve `fractal-ui` and `fractal-icons` as separate packages. Do not add React runtime components here.
- Canonical tokens live in resources/tokens/. Approved icon source remains in design/icons/ for package sync; shared/icons/catalogue.json links to that single catalogue.
- Do not edit icon SVGs or the generated catalogue by hand. Approved artwork still goes through `fractal-testing`, Fractal, and the `fractal-icons` sync/release workflow.
- Keep datasets, model runs, scores, and generated review artifacts in `fractal-testing`.
- Update manifest references and migration provenance when moving documents. Preserve asset licenses and source provenance.
- Ask the user when a source conflict or missing design policy prevents a faithful rewrite. Do not silently invent a new domain or default.
- Package releases remain separate work: inspect the owning package's workflow, build and validate, then use GitHub Actions OIDC. Never request npm tokens or publish locally.
