distill

Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. ## 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. --- ## Assess Current State Analyze what makes the design feel complex or cluttered: 1. **Identify complexity sources**: - **Too many elements**: Competing buttons, redundant information, visual clutter - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose - **Information overload**: Everything visible at once, no progressive disclosure - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations - **Confusing hierarchy**: Unclear what matters most - **Feature creep**: Too many options, actions, or paths forward 2. **Find the essence**: - What's the primary user goal? (There should be ONE) - What's actually necessary vs nice-to-have? - What can be removed, hidden, or combined? - What's the 20% that delivers 80% of value? If any of these are unclear from the codebase, Ask the user using AskUserQuestion. **CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. ## Plan Simplification Create a ruthless editing strategy: - ...