UI/UX Information Architecture and User Flows

Purpose

Make the product understandable and operable before visual styling. Model what users need to find, decide, do, recover from, and confirm.

Procedure

Read flow-review.md when navigation, recovery, responsive behavior, or state transitions are material. For a full-product screen/page inventory or a user request to identify what the project may be missing, read project-coverage-routing.md and select only relevant lenses. Read layered-escape-semantics.md only for a modal, drawer, popover, sheet, or another temporary layered surface. Use flow-decision.md as a starting format for a bounded flow decision; omit sections that do not apply.