agentleFS
elie222elie222/rakazo/.agents/skills/ux-declutter/SKILL.md

ux-declutter

Skill8.6k starsChanged 2 days agoApache-2.0View on GitHub

Review a screen for visual noise and redesign it to be calm — fewer elements, one accent, progressive disclosure, the main action first. Use whenever you build or change UI on web, desktop or mobile, before calling it done, and whenever you look at a screenshot of your own UI.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about elie222/rakazo

The biggest 5 of 86 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 86

Talked about on GitHub, YouTube, the web and Bluesky (86 times).

On GitHub · 50

45 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 6

1 more on Bluesky

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read first, edit second. Open a record as a calm summary.

    line 30
  2. Distinctive:

    Every field on a view screen is editable.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Declutter a screen

A screen that works can still be poor. The usual failure is noise: every capability visible at once, the same fact said twice, several colors fighting for attention, and edit controls where someone only wanted to read. Do this pass on every UI change, from a real screenshot, not from the code.

1. Look at it

Capture the screen in its common state (web E2E screenshot, simulator, emulator). Code review does not show noise; a screenshot does. Look at it as someone who opened it to do one thing.

2. Inventory every element

List every visible word, control, color and container, top to bottom. For each ask, in this order:

  1. Remove? Does it earn its place on this screen, for most visits? Explainer copy that restates a label, a heading that repeats the values under it, a field that repeats the title, a status that is obvious — delete.
  2. Merge? Is the same fact shown twice (title and a name field, a group label and its rows, a summary and the controls that set it)? Keep one.
  3. Disclose later? Is it needed only sometimes? Move it behind a tap:
    • Read first, edit second. Open a record as a calm summary; put the form behind Edit. Inputs everywhere tell people they must fill something in.
    • A long list (history, runs, logs) becomes one row with a chevron to its own screen.
    • Rare or destructive actions (delete, export, test, remove one item) go in a menu, the edit screen, a swipe, or the bottom of the edit form — not repeated per item.
  4. Shrink? Could an icon replace a word (add, share, play, more) where the meaning is universal? Give it an accessible label. Could a value sit at the end of its row instead of taking its own row?

3. Order by use

The control people touch most goes first (an on/off switch, the main content). Then the content they came to read. Then secondary facts (schedule, next run). Navigation rows (history, settings) and the way into editing go last.

4. Color

One accent at a time. Text is ink and secondary gray. Use the accent for the single primary action or link. Destructive red appears once, where deleting happens, not on every row. A switch's own color is enough; do not add colored buttons around it. Count the distinct colors in the screenshot: more than ink, gray, one accent and (rarely) one red is noise.

5. Consistency of controls

One kind of button per job. Do not mix floating pills, full-width filled buttons, tinted text rows and header buttons on one screen. On mobile, prefer the platform's places: header buttons for Save/Cancel/Edit and icons, list rows for navigation, native menus for choices, swipe or a menu for per-item actions.

6. Redo the screenshot and compare

Capture again and put old and new side by side. Count elements and colors before and after. If a reference design or a sibling screen exists, match its density and structure. Keep going until nothing more can be removed without losing what the screen is for.

Signs you are not done

  • Every field on a view screen is editable.
  • The header title also appears in the body.
  • A group label says what its rows already say.
  • Each item in a list carries its own Remove/Delete text button.
  • More than one filled or colored button is visible.
  • A history or log list is expanded inline on a detail screen.
  • Copy explains what a control does when its label already says it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.