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
- thewyattbrocato/design-and-copy-skillstheir own version, first seen Oct 17, 2026
- pengGgxp/skillstheir own version, first seen Oct 11, 2026
- SkillMedev/brand-visual-identitytheir own version, first seen Oct 5, 2026
- miovrag/claude-skillstheir own version, first seen Jun 12, 2026
- launchapp-dev/animus-clitheir own version, first seen Mar 15, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- launchapp-dev/animus-cli★ 39same name
- thewyattbrocato/design-and-copy-skills★ 2same name
- miovrag/claude-skills★ 1same name
- pengGgxp/skills★ 1same name
- SkillMedev/brand-visual-identity★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessible-interfaceSkill
- color-and-contrastSkill
- design-contextSkill
- design-system-auditSkill
- forms-and-validationSkill
- interaction-and-motionSkill
- interface-critiqueSkill
- layout-and-spacingSkill
- loading-empty-error-statesSkill
- responsive-designSkill
- typographySkill
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
- Distinctive: line 11
Do not use decoration to compensate for weak content order.
- Distinctive: line 18
Read the interface at a glance, then in detail.
- Distinctive: line 27
Check long content, missing data, localization, narrow screens, zoom, and focus states so the hierarchy survives realistic conditions.
- Distinctive: line 29
Verify that headings outline the page, primary and secondary actions remain distinguishable, and color is not the only priority signal.
“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.
Files
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
- Identify the primary user goal, the essential supporting information, and the action or decision the surface should make easiest.
- Read the interface at a glance, then in detail. Note the actual first three attention targets and compare them with the intended order.
- Diagnose competition across size, weight, contrast, position, whitespace, grouping, repetition, and motion.
- Establish one dominant focal point per meaningful region. Reduce competing emphasis before adding more.
- Group related items through proximity and alignment. Separate changes in meaning with spacing, boundaries, or section rhythm rather than arbitrary decoration.
- Check long content, missing data, localization, narrow screens, zoom, and focus states so the hierarchy survives realistic conditions.
- 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.
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
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.

