critique

## MANDATORY PREPARATION Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: what the interface is trying to accomplish. --- Conduct a holistic design critique, evaluating whether the interface actually works — not just technically, but as a designed experience. Think like a design director giving feedback. ## Phase 1: Design Critique Evaluate the interface across these dimensions: ### 1. AI Slop Detection (CRITICAL) **This is the most important check.** Does this look like every other AI-generated interface from 2024-2025? Review the design against ALL the **DON'T** guidelines in the frontend-design skill — they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If you showed this to someone and said "AI made this," would they believe you immediately? If yes, that's the problem. ### 2. Visual Hierarchy - Does the eye flow to the most important element first? - Is there a clear primary action? Can you spot it in 2 seconds? - Do size, color, and position communicate importance correctly? - Is there visual competition between elements that should have different weights? ### 3. Information Architecture ...