ss-audit

# UX Audit ## Registry-first artifact boundary When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists. ## 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...