ux-audit
Audit screens against Nielsen's heuristics and mobile UX best practices using the StyleSeed Toss design language as the implementation context.
What this skill does
# UX Audit ## Overview Part 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. ## 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: 1. A prioritized issue list 2. The heuristic violated by each issue 3. Why the issue matters to real users 4. 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 - [StyleSeed repository](https://github.com/bitjaru/styleseed) - [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ux-audit/SKILL.md) ## 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.
Related in design
ios-hig-design-guide
IncludedBuild, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data. Use when a task asks for iOS UI/UX rules, Apple design standards, component behavior, accessibility constraints, interaction patterns, or feature-level design-spec writing grounded in official HIG pages.
macos-design
IncludedDesign and build native-feeling macOS application UIs. Use this skill whenever the user asks to create a desktop app, macOS app, Mac-style interface, Apple-style UI, system utility, or anything that should look and feel like a native Mac application. Also trigger when users mention "native feel", "desktop app design", "Apple design patterns", "sidebar layout", "traffic lights", or want to build tools/utilities that feel like they belong on macOS. This skill covers layout, composition, interaction patterns, animations, light/dark mode, and all the subtle details that make an app feel like Apple built it.
ui-design-patterns
IncludedCommon interface patterns, navigation patterns, form patterns, data display patterns, feedback patterns, and accessibility considerations
figma-design
IncludedFigma workflows, components, auto layout, constraints, prototyping, design systems, and plugin development based on Figma Plugin API documentation
ux-principles
IncludedUser research, usability heuristics, user psychology, accessibility, inclusive design, user testing, and UX metrics
wireframing
IncludedLow/high fidelity wireframes, user flows, information architecture, prototyping techniques, and design iteration processes