| name | design-audit |
| description | Design quality auditor. Detects 24 anti-patterns in UI code (impeccable patterns), critiques visual hierarchy and UX, polishes components to shipping quality. Provides /critique, /audit, /polish, and /bolder commands. |
| automation | manual |
| intents | design, review |
Design Audit Skill
The quality gate of the design stack. Runs after ui-component-builder ships a component
and before it goes to production. Identifies technical flaws, UX problems, and aesthetic
anti-patterns without touching functionality.
Read DESIGN.md before auditing. Audit against the project's design system, not generic best practices.
Slash Commands
/audit [area]
Technical quality check — no edits, only findings.
Reports issues across: accessibility, performance, responsive layout, token compliance, animation correctness.
Output format:
AUDIT FINDINGS — [component name]
🔴 Critical (must fix before ship)
- [issue] at [file:line]
🟡 Warning (should fix)
- [issue] at [file:line]
🟢 Passed
- [checks that passed]
Score: X/10
/critique [area]
UX + visual design review — no edits, only observations.
Evaluates: visual hierarchy, content clarity, emotional resonance, information density, consistency with DESIGN.md.
/polish [area]
Final pass before shipping. Makes targeted improvements to: