Skip to content
Skillpedia
Interfaces (UI/UX)48k · #4471

ux-audit

Helps your agent find usability problems on screens. It checks if the design follows known rules for good user experience, especially for mobile.

What it does

This tool analyzes app or website screens to find usability problems. It checks if the design is easy to use, intuitive, and follows modern best practices, using rules known as 'Nielsen's heuristics'.

When to use it

  • ✓When you want to improve the user experience of an app or website.
  • ✓Before launching a new feature to ensure it's user-friendly.
  • ✓To identify points of frustration users might be facing.

Example of what to ask your AI

“Analyze this login screen and tell me if it's easy to use and what can be improved.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/ux-audit/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/ux-audit/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The AI compares the screen you show it against a list of golden rules for interface design. It checks if buttons are clear, navigation makes sense, and if there are confusing elements, generating a report with the issues found.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill ux-audit

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/ux-audit/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

UX Audit

When to Use

Use this skill when you need audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices.

When NOT to use

  • For accessibility-only issues → use /ss-a11y
  • For design system token/golden-rule compliance → use /ss-review
  • For copy/microcopy quality → use /ss-copy
  • For brand new screens that don't exist yet — design first with /ss-page or /ss-flow

Target: $ARGUMENTS

Audit Framework

Nielsen's 10 Usability Heuristics

1. Visibility of System Status

  • Loading states present (skeleton screens, not spinners)
  • Success/error feedback after actions (toast notifications)
  • Progress indicators for multi-step flows
  • Active state clearly shown on navigation items
  • Real-time data has timestamp showing freshness

2. Match Between System and Real World

  • Labels use user's language, not technical jargon
  • Icons are universally recognizable (Lucide standard set)
  • Number formats match user expectations (comma separators, currency symbols)
  • Date formats are locale-appropriate

3. User Control and Freedom

  • Back navigation available on all non-root screens
  • Destructive actions have confirmation dialogs
  • Undo available for reversible actions (toast with undo)
  • Bottom sheet/modal can be dismissed (backdrop tap, swipe down, X button)
  • No dark patterns (no forced actions, always a way to dismiss)

4. Consistency and Standards

  • Same action = same appearance everywhere
  • Color meanings are consistent (green=success, red=error, brand=active)
  • Text hierarchy follows the 5-level grayscale system
  • All cards use the same shadow, radius, padding
  • Spacing follows the 6px grid system

5. Error Prevention

  • Destructive buttons are visually distinct (destructive variant)
  • Form validation happens on blur (not while typing)
  • Dangerous actions require explicit confirmation
  • Input constraints are visible before errors occur (character limits, format hints)

6. Recognition Rather Than Recall

  • Labels on all icons (especially BottomNav)
  • Current state visible without memorization (active tab highlighted)
  • Recent/frequent items shown for quick access
  • Placeholder text shows expected format

7. Flexibility and Efficiency

  • Key actions reachable within 3 taps from home
  • Pull-to-refresh on data screens
  • Touch targets >= 44x44px (no tiny tap areas)
  • Frequently used actions in easy-to-reach zones (bottom of screen)

8. Aesthetic and Minimalist Design

  • Each screen focuses on ONE primary task
  • No decorative elements that don't serve a purpose
  • Information pyramid respected (most important = biggest)
  • Card density follows the max-4-items rule
  • No competing visual elements (one hero metric per page)

9. Help Users Recover from Errors

  • Error messages explain what went wrong in plain language
  • Error messages suggest how to fix the problem
  • Partial failures don't break the whole page (one card fails, others load)
  • Network errors show retry button
  • Form errors highlight the specific field

10. Help and Documentation

  • Empty states guide users to take action
  • Onboarding for first-time features (if applicable)
  • Tooltips for complex metrics (if applicable)

Mobile-Specific UX Checks

Touch & Gesture

  • Touch targets minimum 44x44px
  • Minimum 8px between adjacent touch targets
  • No hover-dependent interactions (mobile has no hover)
  • Swipe gestures have visible affordances (carousel indicators)

Performance Perception

  • Skeleton screens appear within 300ms
  • Optimistic updates for user actions
  • Above-the-fold content loads first
  • No layout shift after content loads

Safe Areas

  • Content not hidden behind notch/Dynamic Island
  • Bottom content not behind home indicator
  • BottomNav has pb-safe padding

Dark Pattern Prevention

  • No forced bottom sheets on entry
  • No exit-prevention dialogs
  • Every screen has a way to go back/dismiss
  • CTA labels clearly describe the action
  • No manipulative graphics (begging, urgency)

Output Format

  1. Score: A+ to F rating with breakdown
  2. Critical Issues: Must fix (blocks usability)
  3. Major Issues: Should fix (degrades experience)
  4. Minor Issues: Nice to fix (polish)

…

FAQ

What are 'Nielsen's heuristics'?

These are 10 principles created by Jakob Nielsen to guide interface design, focusing on making systems easy to use and understand.

Does this tool check for accessibility issues?

No, it focuses on general usability. For specific accessibility, you should use a different tool.

Can I use it for screens that don't exist yet?

No, the tool analyzes existing screens. For new screens, you should design them first.

Details

Original description by the author

Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#4471
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills