UX Flows

Design every screen by walking the user's journey, not by listing widgets.

The lens

Before building, answer for each state of the flow:

1. What did the user just do? The screen must acknowledge it instantly.
2. What do they want to know right now? Show exactly that — nothing else.
3. What will they most likely do next? Make that the one obvious CTA and lead them into it.
4. Where are they looking / where is their thumb? Feedback appears where they look; primary actions sit in the bottom bar or a bottom sheet (thumb zone). Never bury the next step at the top.

If a component's purpose is an action, the CTA must be unmissable. If its purpose is information, remove every label the content already implies (no "Truck" eyebrow above a plate number).

Questions 1–3 close the Gulf of Execution ("how do I do this?"); question 4 closes the Gulf of Evaluation ("what just happened?"). Mirror the user's mental model from {agentRoot}/USER-BRIEF.md (/understand-the-user) — the flow should match how they think the task works, not your schema. To make any single screen read clearly at a glance, run /make-it-obvious.

Feedback at its locality