distilllisted

Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. ## MANDATORY PREPARATION ### Context Gathering (Do This First) You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), and understanding what's truly essential vs nice-to-have for this product. Attempt to gather these from the current thread or codebase. 1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right. 2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context. Do NOT proceed until you have answers. Simplifying the wrong things destroys usability. ### Use frontend-design skill Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts. --- ## 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 -