/stark-audit

description: Audit existing UI/UX code, flows, or screenshots against UX heuristics plus the matching platform's anti-slop ban list and idiomatic checklist. Reports specific violations with line numbers and proposed fixes.
argument-hint: "[file or screenshot path]"

/stark-audit

Legacy Claude Code command. In Codex, ask:

> Audit this file with stark for UX problems and AI design slop.

Audit the file or screenshot at `$1` against the appropriate platform's standards from this plugin.

Steps:

1. **Detect platform** from file extension or screenshot context:

• `.tsx`/`.jsx`/`.html`/`.svelte`/`.vue`/`.astro` → web
• `.xaml`/`.cs` (with WinUI/WPF context) → windows
• `.swift` → apple
• `.kt`/`.kts` → android
• Screenshot → infer from chrome (title bar style, icons, materials)

2. **Load UX checks first when the artifact includes a workflow, form, dashboard, onboarding, checkout, settings, or multi-step task**:

• UX -> `skills/ux-design/SKILL.md` audit checklist
• UI -> `references/ui-patterns/ui-audit-rubric.md`
• Assets -> `references/ui-patterns/asset-selection.md` when the artifact uses images, screenshots, icons, generated visuals, external references, or brand assets
• References -> `references/ui-patterns/reference-analysis.md` when the artifact claims to use a real product, Mobbin, Figma, or screenshot reference

3. **Load the matching ban list**:

• web → `references/web-bans.md`
• windows → `skills/windows-design/SKILL.md` step 6
• apple → `skills/apple-design/SKILL.md` step 6
• android → `skills/android-design/SKILL.md` step 6

4. **Walk the file** and report violations as a table:

| Line | Violation | Severity | Fix | |---|---|---|---| | 42 | `bg-gradient-to-r from-purple-500 to-pink-500` (banned web slop) | high | Pick a real direction; see web-fonts.md | | 88 | `font-family: 'Inter'` (banned default) | high | Replace with a curated pair from `assets/font-pairs.md` |

5. **Categorize** violations:

• **High** — blocked primary job, missing recovery path, unsafe/destructive action, broken platform idiom, or definitive AI slop tell
• **Medium** — missing state, weak action hierarchy, generic pattern that hurts distinctiveness, decorative assets that do not support the job, or repeated-use friction
• **Low** — unclear copy, mild scan-speed issue, or currency issue (using older patterns when newer ones exist)

6. **Recommend a fix path**: one paragraph, concrete steps, no hedging.

Do not just list violations. Always include the fix. If the entire approach needs rework, say so plainly. Prioritize broken flow, missing states, unclear next actions, and accessibility before visual distinctiveness.