distill

Simplify UI designs by removing redundant elements and clarifying hierarchy.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/jcdiv47/cool-paper --skill distill-jcdiv47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/jcdiv47/cool-paper/tree/main/.agents/skills/distill
Command: npx skills add https://github.com/jcdiv47/cool-paper --skill distill-jcdiv47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distills complex designs by removing unnecessary elements, clarifying hierarchy, and focusing the interface on a single user goal so users complete tasks faster and with less confusion.

Core Features & Use Cases

  • Complexity audit: Identify visual noise, redundant elements, and feature creep in UI components and screens.
  • Ruthless simplification plan: Define core purpose, essential elements, progressive disclosure, and consolidation opportunities.
  • Cross-cutting scope: Applies to information architecture, visual design, layout, interaction flows, content, and code simplification.
  • Use case: Simplify a cluttered settings screen by consolidating actions, hiding advanced options, and establishing one clear primary CTA.

Quick Start

Use the distill skill to simplify the specified component by removing redundant elements, consolidating related actions, and proposing a focused layout that prioritizes the primary user goal.

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 and reduce visual noise in frontend components?

To simplify a cluttered UI, you strip unnecessary complexity from frontend components to reveal essential elements, clarifying hierarchy and focusing the interface on a single primary user goal to improve task completion speed.

What is the best way to audit a UX flow for feature creep and redundant elements?

Auditing a UX flow for feature creep involves identifying visual noise and redundant elements across information architecture and interaction design, then defining a ruthless simplification plan that establishes progressive disclosure and consolidation opportunities.

How do I consolidate related actions on a complex settings screen?

Consolidating actions on a complex settings screen requires identifying redundant elements, hiding advanced options through progressive disclosure, and establishing one clear primary call-to-action to prioritize the main user goal.

Does simplifying information architecture require reference to frontend-design guidance?

Simplifying information architecture requires design context gathered via a Context Gathering Protocol and reference to frontend-design guidance to accurately identify redundant elements and ensure safe simplifications across the UI.

Can I use this approach to simplify code as well as visual design?

You can apply this simplification approach across visual design, layout, interaction flows, content, and code simplification, ensuring all cross-cutting scopes of the interface focus on essential elements without unnecessary complexity.

When should I not use ruthless simplification on a feature screen?

You should avoid ruthless simplification when a feature screen lacks sufficient design context, as removing elements without identifying safe simplifications and understanding essential user flows may degrade the overall interaction design.