critique

Invoke the critique skill and optionally specify the feature or area to evaluate. It assesses the interface across ten dimensions including visual hierarchy, information architecture, and emotional resonance, then returns a structured report with prioritized issues and fixes.

The critique skill includes a dedicated AI slop detection check that reviews the design against known anti-patterns like gradient text, glassmorphism, dark mode with glowing accents, and identical card grids. It gives a pass/fail verdict on whether the interface looks AI-generated.

The report contains an anti-patterns verdict, an overall impression, what is working, three to five priority issues each with a concrete fix and recommended command, minor observations, and provocative questions to unlock 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 yet, you must run teach-impeccable first before conducting the critique.

Avoid it when the interface has no design context established yet, since the protocol requires running teach-impeccable first. It is also not suited for purely functional bug testing, as it evaluates design quality rather than technical correctness.