# Start prompt: U1 UX directions

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-U1.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.

Setup and limits:
- Work on branch `UX-sprint` in the worktree `~/orca/workspaces/kvitt/UX-sprint` (the owner's separate session); `git rebase main` before reporting. Do not use any other branch or worktree.
- Commit only files under `docs/ux/`. Edit nothing else, SPEC.md and CLAUDE.md included.
- Deliver 2 or 3 directions per SPEC §13.4 phase 1: HTML in a 411 dp phone frame, the six screens S-4, S-7, S-5, S-9, S-11, S-8 in light and dark, Swedish copy, realistic data for Jacob and Anna, PNG exports, and `docs/ux/directions/README.md` with the comparison and your recommendation.
- No external requests except Google Fonts. The app bundles no font and uses the Material 3 default typeface (D-020). No placeholder text.
- Stop and ask before installing any tool (for example a headless browser for PNG export).
- Commit on `UX-sprint`, `git rebase main`. Never merge, push or remove the worktree.

Report: end with the report described in PLAN-U1.md §10: branch, head commit hash, files produced with PNG counts, typography, your recommendation in one line, open questions and spec gaps with section numbers, and the owner's next step ("Review 2-3 directions, pick one, give comments") with the PNG paths.