distill

Strip UI layouts to essential content while preserving accessibility affordances.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Nweremizu/ekklesia --skill distill-nweremizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/Nweremizu/ekklesia/tree/main/.junie/skills/distill
Command: npx skills add https://github.com/Nweremizu/ekklesia --skill distill-nweremizu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you remove visual and content clutter from UI work so the page focuses on the one thing the user needs to understand or do next.

Core Features & Use Cases

  • Essence-first editing: Cuts sections, components, and copy that do not answer a user question or drive an action.
  • Interface simplification: Reduces repetitive grids, decorative noise, and oversized visual weight while keeping the design readable.
  • Use case: Take a crowded landing page or dashboard and turn it into a tighter version with fewer sections, clearer hierarchy, and only the strongest details.

Quick Start

Use the distill skill to trim this UI to its essential sections while preserving the main action and accessibility.

Frequently Asked Questions about distill

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

FAQPage Schema
How do I reduce UI clutter on a landing page without losing accessibility?

Reduce UI clutter by stripping away decorative noise and redundant sections while preserving essential accessibility affordances. This approach keeps the page readable and focused on the main action without compromising usability for assistive technologies.

What is the best way to simplify a crowded frontend dashboard?

Simplify a crowded dashboard by cutting components that do not answer a user question or drive an action. Essence-first editing removes repetitive grids and oversized visual weight, leaving only the strongest designed details and clearer hierarchy.

Can I use interface simplification to remove dead code and duplicate patterns in frontend work?

Interface simplification removes dead code and duplicate patterns during the editing process. By cutting down to essential content and structure, the frontend layout becomes tighter and more maintainable without losing its required functionality.

Does simplifying visual weight mean I have to delete all designed details?

Simplifying visual weight does not require deleting all designed details. When higher craft level is needed, the simplification process keeps the strongest designed detail intact while removing only decorative noise and unnecessary copy.

When should I not use UI simplification on marketing sections?

Avoid UI simplification on marketing sections when the copy, layout, and decorative elements are already essential to answering the user question or driving the required action. If the page lacks clutter, stripping elements further may reduce usability.