UX Structure & Interaction Design

There is a prompt instruction at https://www.zangwei.dev/prompts/product-execution/ux-structure-interaction-design-prompt . Extract and follow the prompt to create file /docs/handbook/product/{version|feature}/ux.md

You are a senior UX Designer / Product Designer. Given that the PRD is frozen and the product shape + primary user journey are clear, design the **UX Structure & Interaction Design** for the current version.

## Positioning
- This document focuses on *structure and interaction*, not visual styling
- The goal is to ensure users can complete the core task with minimal cognitive load
- UX design must strictly serve the PRD requirements and acceptance criteria
- This is the direct prerequisite input for UI design and engineering implementation

## Preconditions
- PRD defines scope, interaction logic, and acceptance criteria
- MVP scope and product boundaries are frozen
- This UX design covers only the current version

## General requirements
- Center on the primary user journey
- Prioritize clarity first, then efficiency
- Reduce decision points; avoid unnecessary choices
- If the UX cannot support PRD acceptance, call it out explicitly

---

## UX output structure

1) Information architecture
- Core information hierarchy and grouping
- Level-1 / level-2 pages or views
- What information is required for the primary journey vs auxiliary
- What should not appear in the primary journey

2) Page / view responsibilities
- What problem does each page/view solve?
- What does the user expect upon entering?
- What defines success for the page?
- Navigation relationships between pages

3) Core user flow
- Full primary journey (step-by-step)
- What decisions does the user make at each step?
- What feedback must the system provide at each step?
- What steps can be merged vs must not be removed?

4) States & feedback
- Key states:
  - initial
  - loading
  - success
  - failure
  - empty
- What should the user be told on transitions?
- Which states must be explicit vs can be subtle?

5) Exceptions & fault tolerance
- How to guide users when they make mistakes
- Fallback UX when the system fails
- Which errors can be auto-repaired vs require user action

6) Cognitive load & complexity control
- Core concepts users must understand on the primary journey
- Any info overload or too many steps?
- Which complexity is necessary vs removable?

7) Alignment with PRD & success criteria
- Does the UX directly support PRD acceptance criteria?
- Any interactions drifting from core goals?
- Could UX affect key metrics (conversion, retention, completion rate)?

---

## Output requirements
- No colors/fonts/visual style
- You may use flow descriptions, structured lists, or wireframe-level notes
- Every design decision must be traceable to the PRD
- If the UX structure is unclear, call out the risk

End with 3–5 bullet points:
"Will this UX design enable target users to complete the core task smoothly?"