ss-audit
Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices
Profile →npx skills add bitjaru/styleseed --skill ss-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# UX Audit ## 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
- When NOT to use
- Audit Framework
- Nielsen's 10 Usability Heuristics
- Mobile-Specific UX Checks
- Dark Pattern Prevention
- Output Format
What does the ss-audit skill do?
Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices
How do I install it?
Run `npx skills add bitjaru/styleseed --skill ss-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From bitjaru/styleseed, a repository with 867 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.