Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification.
MANDATORY PREPARATION
Invoke /impeccable — 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 /impeccable teach first.
Assess Current State
Analyze what makes the design feel complex or cluttered:
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
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 directly to clarify what you cannot infer.
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:
- Core purpose: What's the ONE thing this should accomplish?
- Essential elements: What's truly necessary to achieve that purpose?
- Progressive disclosure: What can be hidden until needed?
- Consolidation opportunities: What can be combined or integrated?
IMPORTANT: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless.
Simplify the Design
Systematically remove complexity across these dimensions:
Information Architecture
- Reduce scope: Remove secondary actions, optional features, redundant information
- Progressive disclosure: Hide complexity behind clear entry points (accordions, modals, step-through flows)
- Combine related actions: Merge similar buttons, consolidate forms, group related content
- Clear hierarchy: ONE primary action, few secondary actions, everything else tertiary or hidden
- Remove redundancy: If it's said elsewhere, don't repeat it here
Visual Simplification
- Reduce color palette: Use 1-2 colors plus neutrals, not 5-7 colors
- Limit typography: One font family, 3-4 sizes maximum, 2-3 weights
- Remove decorations: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function
- Flatten structure: Reduce nesting, remove unnecessary containers—never nest cards inside cards
- Remove unnecessary cards: Cards aren't needed for basic layout; use spacing and alignment instead
- Consistent spacing: Use one spacing scale, remove arbitrary gaps
Layout Simplification
- Linear flow: Replace complex grids with simple vertical flow where possible
- Remove sidebars: Move secondary content inline or hide it
- Full-width: Use available space generously instead of complex multi-column layouts
- Consistent alignment: Pick left or center, stick with it
- Generous white space: Let content breathe, don't pack everything tight
Interaction Simplification
- Reduce choices: Fewer buttons, fewer options, clearer path forward (paradox of choice is real)
- Smart defaults: Make common choices automatic, only ask when necessary
- Inline actions: Replace modal flows with inline editing where possible
- Remove steps: Can signup be one step instead of three? Can checkout be simplified?
- Clear CTAs: ONE obvious next step, not five competing actions
Content Simplification
- Shorter copy: Cut every sentence in half, then do it again
- Active voice: "Save changes" not "Changes will be saved"
- Remove jargon: Plain language always wins
- Scannable structure: Short paragraphs, bullet points, clear headings
- Essential information only: Remove marketing fluff, legalese, hedging
- Remove redundant copy: No headers restating intros, no repeated explanations, say it once
Code Simplification
- Remove unused code: Dead CSS, unused components, orphaned files
- Flatten component trees: Reduce nesting depth
- Consolidate styles: Merge similar styles, use utilities consistently
- Reduce variants: Does that component need 12 variations, or can 3 cover 90% of cases?
NEVER:
- Remove necessary functionality (simplicity ≠ feature-less)
- Sacrifice accessibility for simplicity (clear labels and ARIA still required)
- Make things so simple they're unclear (mystery ≠ minimalism)
- Remove information users need to make decisions
- Eliminate hierarchy completely (some things should stand out)
- Oversimplify complex domains (match complexity to actual task complexity)
Verify Simplification
Ensure simplification improves usability:
- Faster task completion: Can users accomplish goals more quickly?
- Reduced cognitive load: Is it easier to understand what to do?
- Still complete: Are all necessary features still accessible?
- Clearer hierarchy: Is it obvious what matters most?
- Better performance: Does simpler design load faster?
Document Removed Complexity
If you removed features or options:
- Document why they were removed
- Consider if they need alternative access points
- Note any user feedback to monitor
Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away."
1---2name: ui-simplify3description: >-4 Simplifies an overloaded existing UI: removes, merges or hides tabs, toggles, panels and5 duplicate controls, cuts choices, applies progressive disclosure and describes the leaner6 layout. Use when the user says a screen is cluttered or overwhelming, has too many options, tabs7 or settings, or asks to declutter or strip it down. Not for building in a minimalist visual8 style (use minimalist-ui).9version: 2.1.110user-invocable: true11argument-hint: "[target]"12metadata:13 source: https://skillmd.com/skills/the-utopia-studio/ui-simplify14---1516Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification.1718## MANDATORY PREPARATION1920Invoke /impeccable — 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 /impeccable teach first.2122---2324## Assess Current State2526Analyze what makes the design feel complex or cluttered:27281. **Identify complexity sources**:29 - **Too many elements**: Competing buttons, redundant information, visual clutter30 - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose31 - **Information overload**: Everything visible at once, no progressive disclosure32 - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations33 - **Confusing hierarchy**: Unclear what matters most34 - **Feature creep**: Too many options, actions, or paths forward35362. **Find the essence**:37 - What's the primary user goal? (There should be ONE)38 - What's actually necessary vs nice-to-have?39 - What can be removed, hidden, or combined?40 - What's the 20% that delivers 80% of value?4142If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.4344**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence.4546## Plan Simplification4748Create a ruthless editing strategy:4950- **Core purpose**: What's the ONE thing this should accomplish?51- **Essential elements**: What's truly necessary to achieve that purpose?52- **Progressive disclosure**: What can be hidden until needed?53- **Consolidation opportunities**: What can be combined or integrated?5455**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless.5657## Simplify the Design5859Systematically remove complexity across these dimensions:6061### Information Architecture62- **Reduce scope**: Remove secondary actions, optional features, redundant information63- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows)64- **Combine related actions**: Merge similar buttons, consolidate forms, group related content65- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden66- **Remove redundancy**: If it's said elsewhere, don't repeat it here6768### Visual Simplification69- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors70- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights71- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function72- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards73- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead74- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps7576### Layout Simplification77- **Linear flow**: Replace complex grids with simple vertical flow where possible78- **Remove sidebars**: Move secondary content inline or hide it79- **Full-width**: Use available space generously instead of complex multi-column layouts80- **Consistent alignment**: Pick left or center, stick with it81- **Generous white space**: Let content breathe, don't pack everything tight8283### Interaction Simplification84- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real)85- **Smart defaults**: Make common choices automatic, only ask when necessary86- **Inline actions**: Replace modal flows with inline editing where possible87- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified?88- **Clear CTAs**: ONE obvious next step, not five competing actions8990### Content Simplification91- **Shorter copy**: Cut every sentence in half, then do it again92- **Active voice**: "Save changes" not "Changes will be saved"93- **Remove jargon**: Plain language always wins94- **Scannable structure**: Short paragraphs, bullet points, clear headings95- **Essential information only**: Remove marketing fluff, legalese, hedging96- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once9798### Code Simplification99- **Remove unused code**: Dead CSS, unused components, orphaned files100- **Flatten component trees**: Reduce nesting depth101- **Consolidate styles**: Merge similar styles, use utilities consistently102- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases?103104**NEVER**:105- Remove necessary functionality (simplicity ≠ feature-less)106- Sacrifice accessibility for simplicity (clear labels and ARIA still required)107- Make things so simple they're unclear (mystery ≠ minimalism)108- Remove information users need to make decisions109- Eliminate hierarchy completely (some things should stand out)110- Oversimplify complex domains (match complexity to actual task complexity)111112## Verify Simplification113114Ensure simplification improves usability:115116- **Faster task completion**: Can users accomplish goals more quickly?117- **Reduced cognitive load**: Is it easier to understand what to do?118- **Still complete**: Are all necessary features still accessible?119- **Clearer hierarchy**: Is it obvious what matters most?120- **Better performance**: Does simpler design load faster?121122## Document Removed Complexity123124If you removed features or options:125- Document why they were removed126- Consider if they need alternative access points127- Note any user feedback to monitor128129Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away."