ux-ui-reviewlisted

# UX/UI Review Goal: every user can accomplish their task without confusion. The product looks professional. Invoke when: user asks to review a project, audit the UI, check usability, or when running alongside code review. ## How to run **0. Reviewer map** — run once, when the build is otherwise done, before final sign-off. Two separate lists, don't merge them: - **In-app roles** — pull straight from `roles.md`/`wireframe.lock.md` if present (every `data-role` found). Each is reviewed by *using* the product as that role. - **Outside reviewers** — who else looks at this project and in what capacity, even though they never touch the running app as an end user: course instructor grading the submission, classmates giving peer feedback, the actual business owner/client checking it matches their brief, a real target customer doing a first-impression test. Infer these from project context (course deliverable vs. client project vs. personal tool) — don't invent generic ones that don't apply, and ask if the context is unclear. Output this as a table before the rest of the report: `Reviewer | Capacity | What they check`. **1. Scan first** — find all page/screen files and list them before reviewing anything. If screenshots or a live URL are provided, use those as primary evidence. **2. Identify user types** — who uses this system? (end user, admin, guest, etc.) For each: what is their goal? Cross-check against the in-app roles from step 0 — flag any role in `roles.md`