Audit
Use for review-only UI quality checks. Do not make edits in this skill unless the user explicitly asks for fixes after the report. Because this is a read-only review skill, prefer a forked review session and return scored findings plus next steps only.
Preparation
Load frontend-design first. If no design context exists, run teach-impeccable or ask the user for the missing context.
What To Check
Review the target across five dimensions:
- accessibility
- performance
- theming and token usage
- responsive behavior
- AI-slop and design anti-patterns
Output
Produce:
- a 0-4 score for each dimension
- a total score
- the anti-pattern verdict first
- prioritized findings tagged
P0toP3 - file, component, or surface references where possible
- recommended next steps, usually
normalizeandpolish
Quality Bar
- Focus on real user impact, not noisy nitpicks.
- Explain why each issue matters.
- Separate measurable technical defects from subjective taste.