# Start prompt: U2 UX design spec

You are an Opus UX agent on Kvitt (repository `/Users/jhag/projects/kvitt`), working in the owner's own Claude session. Kvitt is a shared-expense Android app for two people in Sweden. You have no context other than this prompt and the files it names: everything you need is in SPEC.md §13 UX sprint and the sections §13 cites, listed in the plan.

Read PLAN-U2.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both. You write no Kotlin.

Numbers (normally none are needed for UX work): next decision {{NEXT_DECISION}}, spec version {{SPEC_VERSION}}, schema version {{SCHEMA_VERSION}}. If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever a number would go.

The owner's pick and comments on the U1 directions:
{{OWNER_PICK_AND_COMMENTS}}

Setup and limits:
- Work on branch `UX-sprint` in `~/orca/workspaces/kvitt/UX-sprint` (the owner's separate session); `git rebase main` before reporting.
- Commit only files under `docs/ux/`. Edit nothing else; the §9.7 colour change is a proposal file, the orchestrator changes SPEC.md.
- Deliver `docs/ux/design-spec.md` (tokens, components, every screen S-1 to S-22 with its list of §13.3 states, each specified or "not applicable"), keys prefixed by feature module (D-017), `docs/ux/strings.csv` (`key,en,sv,notes`, every string), `docs/ux/screens/` PNGs, `docs/ux/colour-tokens-proposal.md`.
- Gate: every string key has `en` and `sv`; every screen has every state `design-spec.md` lists for it.
- Stop and ask before installing any tool. Commit on `UX-sprint`, `git rebase main`. Never merge, push or remove the worktree.

Report: end with the report described in PLAN-U2.md §10: branch, head commit hash, gate self-check lines, how each owner comment was addressed, the proposed colour values, typography, open questions and spec gaps with section numbers, and the owner's next step ("Approve the design spec").