critique

Run a design critique that evaluates the interface across ten dimensions including visual hierarchy, information architecture, typography, and color. The output is a prioritized report listing the top issues, why each matters, and concrete fixes.

Check for common AI tells such as gradient text, glassmorphism, dark mode with glowing accents, hero metric layouts, identical card grids, and generic fonts. If someone would immediately believe AI made the interface, it fails the test.

The report contains an anti-patterns verdict, an overall impression, two to three things working well, three to five prioritized issues with fixes and suggested commands, minor observations, and open questions to provoke better solutions.

Yes, it depends on the frontend-design skill for design principles, anti-patterns, and the Context Gathering Protocol. If no design context exists, the teach-impeccable skill must run first before the critique proceeds.

Avoid it for purely technical reviews like performance, accessibility compliance audits, or code correctness, since the critique focuses on experiential design quality. Use dedicated audit or hardening commands for those concerns.