UX Audit
Overview
Part of StyleSeed, this skill audits usability rather than just visuals. It uses Nielsen's 10 heuristics plus modern mobile UX expectations to find issues in navigation, feedback, recovery, hierarchy, and cognitive load.
When to Use
- Use when a screen feels awkward even though the code and styling seem correct
- Use when evaluating a flow before or after implementation
- Use when reviewing a mobile-first product for usability regressions
- Use when you want findings framed as user experience problems with remediation
Audit Framework
Review the target against:
- visibility of system status
- match between system and real-world language
- user control and freedom
- consistency and standards
- error prevention
- recognition rather than recall
- flexibility and efficiency
- aesthetic and minimalist design
- recovery from errors
- help, onboarding, and empty-state guidance
Add mobile-specific checks for reachability, touch ergonomics, input burden, and thumb-friendly action placement.
Output
Return:
- A prioritized issue list
- The heuristic violated by each issue
- Why the issue matters to real users
- Specific remediation suggestions for the page, component, or flow
Best Practices
- Judge the experience from the user's point of view, not the implementer's
- Separate high-severity flow blockers from minor polish issues
- Include recovery and state-management guidance, not only layout comments
- Tie recommendations back to concrete UI changes
Additional Resources
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: ux-audit3description: "Audit screens against Nielsen's heuristics and mobile UX best practices using the StyleSeed Toss design language as the implementation context."4category: design5risk: safe6source: community7source_repo: bitjaru/styleseed8source_type: community9date_added: "2026-04-08"10author: bitjaru11tags: [ux, audit, usability, mobile, styleseed]12tools: [claude, cursor, codex, gemini]13---1415# UX Audit1617## Overview1819Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill audits usability rather than just visuals. It uses Nielsen's 10 heuristics plus modern mobile UX expectations to find issues in navigation, feedback, recovery, hierarchy, and cognitive load.2021## When to Use22- Use when a screen feels awkward even though the code and styling seem correct23- Use when evaluating a flow before or after implementation24- Use when reviewing a mobile-first product for usability regressions25- Use when you want findings framed as user experience problems with remediation2627## Audit Framework2829Review the target against:30- visibility of system status31- match between system and real-world language32- user control and freedom33- consistency and standards34- error prevention35- recognition rather than recall36- flexibility and efficiency37- aesthetic and minimalist design38- recovery from errors39- help, onboarding, and empty-state guidance4041Add mobile-specific checks for reachability, touch ergonomics, input burden, and thumb-friendly action placement.4243## Output4445Return:461. A prioritized issue list472. The heuristic violated by each issue483. Why the issue matters to real users494. Specific remediation suggestions for the page, component, or flow5051## Best Practices5253- Judge the experience from the user's point of view, not the implementer's54- Separate high-severity flow blockers from minor polish issues55- Include recovery and state-management guidance, not only layout comments56- Tie recommendations back to concrete UI changes5758## Additional Resources5960- [StyleSeed repository](https://github.com/bitjaru/styleseed)61- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ux-audit/SKILL.md)6263## Limitations64- Use this skill only when the task clearly matches the scope described above.65- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.66- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.