← ClaudeAtlas

aie-web-uxlisted

Review a website or web app for usability and user-experience problems that hurt real visitors — confusing navigation, weak visual hierarchy, buttons that don't look clickable, forms with poor feedback, cluttered layouts, mobile/touch issues, low readability, and missing error handling. Evaluates against Nielsen's usability heuristics and WCAG-informed readability, then scores each area and lists prioritized, actionable fixes. Trigger on "review the UX," "UX review," "usability review," "is my site easy to use," "hard to navigate," "confusing layout," "improve the flow," "design review," "mobile experience," "users can't find," or "information architecture."
mrhinkle/aienterprise-skills · ★ 2 · Web & Frontend · score 68
Install: claude install-skill mrhinkle/aienterprise-skills
# Web UX Review Evaluates whether a site works well *for humans*, not just whether it technically works. Catches the friction that automated tools miss: confusing navigation, buried content, unclear CTAs, and mobile pain. Produces a scored review with prioritized fixes. ## Workflow 1. **Confirm the target and audience** — the URL or pages to review, who the primary visitor is, and what they're trying to accomplish. UX is judged against a goal. 2. **Walk the key journeys** — at minimum: homepage first impression, the primary conversion path (contact/signup/purchase), and mobile. See `reference/journeys.md` for what to ask on each page type. 3. **Evaluate against the heuristics and checklists** — apply Nielsen's 10 usability heuristics plus the navigation, visual-hierarchy, mobile, and readability checklists in `reference/checklists.md`. 4. **Flag anti-patterns** — scan for the common UX traps in `reference/checklists.md` (mystery-meat navigation, walls of text, auto-playing media, hidden contact info, hover-only interactions, etc.). 5. **Score and prioritize** — fill the scorecard below, then rank fixes by impact. Navigation and mobile issues usually outrank cosmetic ones. ## Nielsen's 10 usability heuristics (what to check) 1. **Visibility of system status** — loading/feedback states, active-page highlighting, visible success/error messages. 2. **Match with the real world** — plain-language labels and CTAs, intuitive icons, no unexplained jargon. 3. **User control and fr