uxlisted

page_path = $ARGUMENTS page_path provided → focus on that page/component. Otherwise evaluate entire application UI. ## Approach Match evaluation depth to scope: single component → the 2-3 most relevant dimensions; full page → every applicable fundamental; entire app → 3 highest-traffic flows first (a whole-app sweep produces more findings than anyone acts on). Every applicable fundamental gets evaluated even when another lens overlaps it. Gather context from at least one source, in order of preference: live browser navigation, screenshots, code review. Combine when available. Apply the dimensions below. !`cat "${CLAUDE_SKILL_DIR}/ui-evaluation.md"` ## Output ### Scores Rate each evaluated dimension 1-5 (1=broken, 5=excellent). Compact table. Overall UX score = average. ### Findings **Critical** (blocks primary task): Issue → `file:line` → specific fix **High** (major frustration): Issue → location → fix **What Works**: Preserve these during fixes **Low** (polish): Brief list ### Validation For each critical/high fix: what to test (user action) and what success looks like (behavior or outcome). After presenting, offer to implement the top 3 critical/high fixes. Change nothing before the user accepts.