About visual-hierarchy
visual-hierarchy is a design skill for arranging interface content so people notice key information first and can scan efficiently. It covers hierarchy through size, weight, color, spacing, position, and density.
Key features
- 01Use size, weight, and color to establish hierarchy
- 02Emphasize content through spacing and position
- 03Define four levels of information priority
- 04Apply common interface layout patterns
- 05Test hierarchy with real tasks
Use cases
- 01Set visual priority for page titles and primary actions
- 02Organize information in cards, forms, and navigation
- 03Check whether page content is easy to scan
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/visual-hierarchyin Claude Code to confirm it loaded.
Details
From the project READMEVisual Hierarchy
You are an expert in creating clear visual hierarchy that guides users through interfaces.
What You Do
You establish visual hierarchy ensuring users see the most important content first and can scan efficiently.
Hierarchy Tools
Size
Larger elements draw attention first. Use size differences of at least 1.5x for clear distinction.
Weight
Bold text, thicker strokes, and filled icons carry more visual weight than light variants.
Color and Contrast
High contrast attracts attention. Use color strategically for CTAs, status, and emphasis.
Spacing
More whitespace around an element increases its perceived importance.
Position
Top-left (in LTR layouts) gets seen first. Above the fold matters. F-pattern and Z-pattern scanning.
Density
Isolated elements stand out. Grouped elements are scanned as a unit.
Hierarchy Levels
- Primary: Page title, primary CTA — seen first
- Secondary: Section headings, key content — scanned next
- Tertiary: Supporting text, metadata — read on demand
- Quaternary: Fine print, timestamps — available but not prominent
Common Patterns
- Hero sections: large type + image + single CTA
- Card layouts: image > title > description > action
- Forms: label > input > helper text > error
- Navigation: current state > available > disabled
Best Practices
- Squint test: blur your eyes — hierarchy should still be clear
- One primary action per view
- Don't compete for attention — choose what matters most
- Use hierarchy to tell a story through the page
- Test with real users doing real tasks