product-design-reviewlisted

# Product Design Review Judge whether a real user can understand, trust, and complete the surface's primary job, then improve only what the requested scope authorizes. ## Design Posture - Identify the audience, context, and single job of the surface before discussing aesthetics. - The brief and established product identity win. In Fmind work, use [fmind-visuals](../fmind-visuals/SKILL.md) for brand truth; do not replace Tokyo Night or existing tokens by habit. - Classify the task as **preserve**, **refine**, or **redesign**. A critique does not authorize code edits, factual copy changes, or a new visual identity. - Prefer one justified signature over decorative variety. Remove elements that do not encode meaning or help the task. - Review real content, states, and runtime behavior. A static happy-path screenshot is insufficient. - Bound iteration: one batched desktop/mobile review, one coherent fix pass when authorized, and one confirmation pass. ## Workflow 1. **Recover product truth:** Read the brief, existing product or design artifacts, tokens, components, user research, and representative content. Name any missing evidence. 1. **Map the journey:** Identify entry points, primary action, decisions, exits, failure recovery, and time to first value. 1. **Inspect the live surface:** Use [quality-assurance](../quality-assurance/SKILL.md) to capture desktop and mobile states, DOM semantics, console/network errors, keyboard behavior, focus, reduced motion, and screenshots w