# 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 `agent-ux` in `.claude/worktrees/agent-ux`. If that worktree still exists (U1 not landed), continue there and `git rebase main`; otherwise, from the main checkout, `git worktree add .claude/worktrees/agent-ux -b agent-ux main`, then `git reset --hard main` inside it.
- 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 every §13.3 state or "not applicable"), `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 all states of §13.3.
- Stop and ask before installing any tool. Commit on `agent-ux`, `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, fonts and licences, open questions and spec gaps with section numbers, and the owner's next step ("Approve the design spec").