distill

Simplify UI designs by removing unnecessary elements, visual noise, and redundant content.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill distill-shyamravidath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/ShyamRavidath/oscc-detection-v2/tree/main/.agents/skills/distill
Command: npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill distill-shyamravidath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces accumulate clutter over time: competing buttons, excessive colors, redundant copy, and nested containers that bury the primary user goal. This Skill systematically strips a design down to its essential elements so users can complete their core task faster with less cognitive load. ## Core Features & Use Cases - Complexity Assessment: Identifies sources of clutter such as too many elements, excessive visual variation, information overload, and confusing hierarchy before making changes. - Multi-Dimension Simplification: Applies structured reduction across information architecture, visual styling, layout, interaction flows, copy, and code, including progressive disclosure and consolidation of redundant actions. - Verification and Documentation: Confirms simplification improves task completion and hierarchy clarity, and documents any removed features with rationale. - Use Case: A settings page has grown to five competing CTAs, seven colors, and cards nested inside cards. Use this Skill to reduce it to one primary action, a two-color palette, and a flat linear layout while preserving all necessary functionality. ## Quick Start Simplify the dashboard page by removing redundant elements and clarifying the primary user action.

Frequently Asked Questions about distill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I simplify a cluttered UI design?

Start by identifying complexity sources such as too many elements, excessive color variation, and unclear hierarchy. Then reduce scope to one primary action, apply progressive disclosure for secondary content, and cut the palette to one or two colors plus neutrals.

How to reduce visual clutter without removing features?

Use progressive disclosure to hide secondary options behind accordions, modals, or step-through flows rather than deleting them. Consolidate similar actions, flatten nested containers, and rely on spacing and alignment instead of decorative cards and borders.

Does simplifying a design mean removing functionality?

No. Simplification removes obstacles between users and their goals, not necessary features. Every element must justify its existence, but accessibility labels, decision-critical information, and required functionality must be preserved.

When should I not simplify a user interface?

Avoid oversimplifying genuinely complex domains where the task itself requires density, such as data-heavy professional tools. Also avoid reducing hierarchy so far that nothing stands out, or cutting information users need to make decisions.

Why does my simplified design feel unclear or confusing?

Over-reduction creates mystery rather than minimalism. Check that one obvious next step remains, labels stay explicit, and hierarchy still distinguishes primary from secondary content. Clarity takes priority over removing more elements.