UI Design Critique

Produce a rigorous, prioritized design critique of a user interface. Output a single report that lists every issue ranked by impact, classifies each finding, and calls out what already works. Be strict. The goal is a report a designer can act on top-to-bottom, not vague praise.

This skill evaluates and reports. It does not implement fixes. For building or polishing UI, use design-engineering. For self-evidence/affordance depth, cross-reference ux-interface-design.

Non-Negotiables

1. Breakage is computed, not judged. Run the deterministic broken-UI smoke test (references/broken-ui-detectors.md) before any judgment-based review. Vision review reliably misses overflow, overlap, clipping, and misalignment — never rely on "looking at" a screenshot to find them. A page that fails the smoke test is broken regardless of its aesthetics.
2. AI Slop Detection is the most important judgment check. Run it immediately after the smoke test. See references/ai-slop-detection.md.
3. Critique against intent, not personal taste. When a DESIGN.md spec exists, it is the source of truth. Distinguish a violation of intent (a real finding) from a stylistic preference (a suggestion, clearly labeled).
4. Every finding needs evidence. Point to the specific element, region, or token. No pattern-only claims like "typography feels off" without naming the element and the reason.
5. Every finding needs a priority and a classification. No unranked, unclassified findings.
6. Report strengths too. A critique that only lists problems is incomplete and untrustworthy.

Inputs

Accept any of these; ask only if none are available: