ux-audit
Audit screens against Nielsen's heuristics and mobile UX best practices using the StyleSeed Toss design language as the implementation context.
Best use case
ux-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audit screens against Nielsen's heuristics and mobile UX best practices using the StyleSeed Toss design language as the implementation context.
Teams using ux-audit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ux-audit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ux-audit Compares
| Feature / Agent | ux-audit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audit screens against Nielsen's heuristics and mobile UX best practices using the StyleSeed Toss design language as the implementation context.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 Skills
hypeauditor-automation
Automate Hypeauditor tasks via Rube MCP (Composio). Always search tools first for current schemas.
claude-settings-audit
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.
audit-skills
Expert security auditor for AI Skills and Bundles. Performs non-intrusive static analysis to identify malicious patterns, data leaks, system stability risks, and obfuscated payloads across Windows, macOS, Linux/Unix, and Mobile (Android/iOS).
project-skill-audit
Audit a project and recommend the highest-value skills to add or update.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
wcag-audit-patterns
Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.
vibe-code-auditor
Audit rapidly generated or AI-produced code for structural flaws, fragility, and production risks.
swiftui-performance-audit
Audit SwiftUI performance issues from code review and profiling evidence.
supply-chain-risk-auditor
Identifies dependencies at heightened risk of exploitation or takeover. Use when assessing supply chain attack surface, evaluating dependency health, or scoping security engagements.
seo-content-auditor
Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines.
seo-audit
Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.
seo-aeo-content-quality-auditor
Audits content for SEO and AEO performance with scored reports, severity-ranked fix lists, and projected scores after fixes. Activate when the user wants to audit, review, or score content for SEO or AEO compliance.