distill

Start by identifying complexity sources such as too many elements, excessive color variation, and unclear hierarchy. Then reduce scope, apply progressive disclosure, consolidate actions, limit the palette to 1-2 colors plus neutrals, and cut copy aggressively while keeping one clear primary action.

Remove decorative borders, shadows, and backgrounds that do not serve hierarchy or function. Limit typography to one font family with 3-4 sizes, use a single consistent spacing scale, and replace nested cards with spacing and alignment for structure.

No. Simplification removes obstacles between users and their goals, not necessary functionality. Features can be hidden behind progressive disclosure patterns like accordions or step-through flows, but everything users need to make decisions must remain accessible.

Avoid oversimplifying when the domain is genuinely complex, when it would sacrifice accessibility such as clear labels and ARIA attributes, or when it removes information users need for decisions. Minimalism should never create mystery about what to do next.

It requires an existing design context established through the frontend-design skill and its Context Gathering Protocol. If no design context exists, you must run the teach-impeccable skill first before simplification can proceed.