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.
Core Process
- Define the core tasks and user goals for the flow being audited.
- Step through the flow evaluating against Nielsen's heuristics.
- Test edge cases, error states, and empty states specifically.
- Document actionable findings and prioritize remediation.
Common Rationalizations
| Rationalization |
Reality |
| The screen looks modern, so the UX must be good. |
Aesthetics do not equal usability; heuristic evaluation is required. |
| I'll only audit the happy path. |
Most UX failures occur in error states, edge cases, and empty states. |
| Users will figure out this complex navigation. |
If navigation requires effort to 'figure out', the UX has failed. |
Red Flags
- Missing feedback for user actions (system status visibility).
- Lack of clear undo/cancel options for critical actions.
- Inconsistent terminology used across different screens.
Verification
1---2name: ux-audit3description: Use when auditing screens against Nielsen's heuristics and mobile UX best practices within the StyleSeed Toss design language context.4---56# UX Audit78## Overview910Part 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.1112## When to Use13- Use when a screen feels awkward even though the code and styling seem correct14- Use when evaluating a flow before or after implementation15- Use when reviewing a mobile-first product for usability regressions16- Use when you want findings framed as user experience problems with remediation1718## Audit Framework1920Review the target against:21- visibility of system status22- match between system and real-world language23- user control and freedom24- consistency and standards25- error prevention26- recognition rather than recall27- flexibility and efficiency28- aesthetic and minimalist design29- recovery from errors30- help, onboarding, and empty-state guidance3132Add mobile-specific checks for reachability, touch ergonomics, input burden, and thumb-friendly action placement.3334## Output3536Return:371. A prioritized issue list382. The heuristic violated by each issue393. Why the issue matters to real users404. Specific remediation suggestions for the page, component, or flow4142## Best Practices4344- Judge the experience from the user's point of view, not the implementer's45- Separate high-severity flow blockers from minor polish issues46- Include recovery and state-management guidance, not only layout comments47- Tie recommendations back to concrete UI changes4849## Additional Resources5051- [StyleSeed repository](https://github.com/bitjaru/styleseed)52- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ux-audit/SKILL.md)5354## Limitations55- Use this skill only when the task clearly matches the scope described above.56- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.57- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.585960## Core Process611. Define the core tasks and user goals for the flow being audited.622. Step through the flow evaluating against Nielsen's heuristics.633. Test edge cases, error states, and empty states specifically.644. Document actionable findings and prioritize remediation.6566## Common Rationalizations67| Rationalization | Reality |68|---|---|69| The screen looks modern, so the UX must be good. | Aesthetics do not equal usability; heuristic evaluation is required. |70| I'll only audit the happy path. | Most UX failures occur in error states, edge cases, and empty states. |71| Users will figure out this complex navigation. | If navigation requires effort to 'figure out', the UX has failed. |7273## Red Flags74- Missing feedback for user actions (system status visibility).75- Lack of clear undo/cancel options for critical actions.76- Inconsistent terminology used across different screens.7778## Verification79- [ ] Audit covers all relevant Nielsen's heuristics.80- [ ] Error states and edge cases are explicitly tested.81- [ ] A concrete list of actionable UX improvements is generated.
hybridlabor-api