agentleFS
Above-the-Fold-StudioAbove-the-Fold-Studio/designmd-skills/skills/visual-hierarchy/SKILL.md

visual-hierarchy

Skill0 starsChanged 3 months agoMITView on GitHub

Strengthen interface hierarchy so attention, reading order, and primary actions are immediately clear.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Do not use decoration to compensate for weak content order.

    line 11
  2. Distinctive:

    Read the interface at a glance, then in detail.

    line 18
  3. Distinctive:

    Check long content, missing data, localization, narrow screens, zoom, and focus states so the hierarchy survives realistic conditions.

    line 27
  4. Distinctive:

    Verify that headings outline the page, primary and secondary actions remain distinguishable, and color is not the only priority signal.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Visual Hierarchy

Make importance visible. Use this when an interface feels flat, noisy, mis-prioritized, difficult to scan, or unclear about what happens next.

Do not use decoration to compensate for weak content order. Do not make every element louder, and do not change product priority without evidence.

Workflow

  1. Identify the primary user goal, the essential supporting information, and the action or decision the surface should make easiest.
  2. Read the interface at a glance, then in detail. Note the actual first three attention targets and compare them with the intended order.
  3. Diagnose competition across size, weight, contrast, position, whitespace, grouping, repetition, and motion.
  4. Establish one dominant focal point per meaningful region. Reduce competing emphasis before adding more.
  5. Group related items through proximity and alignment. Separate changes in meaning with spacing, boundaries, or section rhythm rather than arbitrary decoration.
  6. Check long content, missing data, localization, narrow screens, zoom, and focus states so the hierarchy survives realistic conditions.
  7. Verify that headings outline the page, primary and secondary actions remain distinguishable, and color is not the only priority signal.

Output

Return the intended reading order, the strongest hierarchy problems, concrete changes in priority order, and the conditions used to verify them.

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.