Files

T

jacobh2 76ee957f41 SPEC v0.3: orchestrator resolutions of the plans' open points

Records D-004 and D-015 to D-025: shells and ownership, server seams
(router middleware, rate_limit layer, tasks::start, AuditWriter and PushQueue
traits, next_occurrence_date in kvitt-domain, M3 owns recurring generation,
M4 lands after M3), OpenAPI parsed-value equality, feature convention and
strings, empty fake scenario and resolveRange exception, shared ledger rows and
editor fields in :core:design, no bundled font, pruning at 04:00, development
infrastructure as M2c-dev built it, M2c-pi allowances, release keystore,
production import procedure. Plans and prompts close their open points;
HANDOFF rewritten to the real state; CLAUDE.md: implementation agents never
edit SPEC.md or docs/decisions.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-17 21:23:38 +02:00

1.9 KiB

Raw Blame History

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").

1.9 KiB Raw Blame History

Start prompt: U2 UX design spec

1.9 KiB

Raw Blame History