product-uxlisted

# Product UX ## Purpose And Boundary Translate confirmed journey and stories into page skeletons (WHERE content lives) and interaction rules (IX, HOW users interact) — at a level business can review and function-description can use without re-interpreting. This Skill owns the **UX layer** only: page skeletons (§页面设计, produced by `page-design`) and interaction rules (§交互规则, produced by `interaction-rules`). **Do not do 功能清单 (feature lists) or 功能流程 (functional flows)** — those belong to `function-description`. Business rules (BR), validations (VL), and acceptance criteria (AC) also belong to function-description — **do not leak them here**. **Do not**: design visual UI (colors/fonts), write business rules, define acceptance criteria, produce feature lists or functional flows, invent pages not traced to confirmed stories, or use prototype as substitute for written rules. ## UX Layer Model ``` 页面设计 (§页面设计) → Page skeletons: WHERE content lives, entry→content→actions→next-state 交互规则 (§交互规则) → IX-XXX: HOW users interact, trigger → system response (normal/error/empty/loading/edge) ``` This mirrors how senior PMs sequence UX definition: pages first (structure/layout of content), then the interaction rules that govern each page. ## PM-Specific Deliverables - **Page skeletons**: entry trigger + preconditions + content areas + available actions + next-state — not visual design - **IX rules**: trigger → system response, covering normal + error + empty + loading + edge states -