agentleFS
Dragoon0xDragoon0x/taste-skills/skills/visual-language/hierarchy-principles/SKILL.md

hierarchy-principles

Skill5 starsChanged 8 months agoMITView on GitHub

Visual weight, attention order, and the decisions that guide the eye. Use when building layouts, evaluating information architecture, or diagnosing why a design feels confusing.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    MUST establish a clear primary element on every screen.

    line 17
  2. Distinctive:

    MUST create hierarchy through at least two of: scale, weight, contrast, color, space, position

    line 18
  3. Distinctive:

    MUST ensure visual weight matches content priority (the most important thing is the most prominent)

    line 19
  4. Distinctive:

    NEVER allow two elements to compete at the same hierarchy level unless intentional tension is the goal

    line 20
  5. Distinctive:

    SHOULD test by covering half the screen.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Hierarchy Principles

The single most important thing in any visual design.

How to use

  • /hierarchy-principles Apply hierarchy constraints to any design work in this conversation.

Constraints

Hierarchy Rules

  • MUST establish a clear primary element on every screen. If everything is important, nothing is.
  • MUST create hierarchy through at least two of: scale, weight, contrast, color, space, position
  • MUST ensure visual weight matches content priority (the most important thing is the most prominent)
  • NEVER allow two elements to compete at the same hierarchy level unless intentional tension is the goal
  • SHOULD test by covering half the screen. Can you still tell what's most important?

Hierarchy Tools

  • Scale: Bigger things get seen first. The ratio between largest and smallest defines your range.
  • Weight: Bolder things demand attention. Use sparingly or nothing stands out.
  • Contrast: High-contrast elements pull focus. Low-contrast recedes.
  • Color: Saturated colors advance. Desaturated retreat. One accent in a neutral system creates instant hierarchy.
  • Space: More breathing room signals more importance. Crowded elements feel like metadata.
  • Position: Top-left gets seen first (LTR). Center gets attention. Bottom-right gets ignored unless hierarchy pulls the eye there.

Anti-Patterns

  • Using size as the only hierarchy tool (creates monotonous layouts)
  • Making everything bold (negates the purpose of bold)
  • Competing calls-to-action on the same screen
  • Navigation that's visually louder than the content it serves

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.