hierarchy

Construct visual hierarchy in layouts using size, weight, color, position, and whitespace.

8|3|Updated May 3, 2026
One-click install
npx skills add https://github.com/Deibler/universal-design-principles --skill hierarchy-deibler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hierarchy
Source: https://github.com/Deibler/universal-design-principles/tree/main/plugins/perception-and-hierarchy-principles/skills/hierarchy
Command: npx skills add https://github.com/Deibler/universal-design-principles --skill hierarchy-deibler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designs with weak visual hierarchy leave users unsure where to look, making pages feel flat and forcing viewers to figure out what matters on every screen. This Skill teaches how to rank elements deliberately so the primary focal point is obvious at a glance. ## Core Features & Use Cases - Hierarchy construction guidance: Explains the eight visual dimensions (size, weight, color, tone, position, whitespace, density, motion) and how to stack them for a clear primary, secondary, and tertiary tier structure. - Worked framework-agnostic examples: Provides HTML/CSS patterns for page headers, button rows, dashboard tile grids, and forms, each showing the anti-pattern and the corrected version. - Diagnostic heuristics: Includes the squint test, eye-trace test, grayscale test, and five-tier check to validate whether hierarchy is working. - Use Case: When reviewing a dashboard where twelve KPI tiles all look identical, apply the three-tier rule to promote one primary metric to a 2x2 tile with a large value while recessing the rest. ## Quick Start Review this screen layout and rebuild its visual hierarchy so there is one clear primary element with supporting secondary and tertiary tiers.

Frequently Asked Questions about hierarchy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create visual hierarchy in a UI layout?▼

Create visual hierarchy by varying size, weight, color, tone, position, and whitespace so one element reads as primary, a few as secondary, and the rest as tertiary. Stacking multiple dimensions on the primary element makes the ranking unambiguous.

How many levels of visual hierarchy should a page have?▼

Aim for three levels: one primary focal element, several secondary supporting elements, and recessive tertiary elements like metadata and fine print. Fewer levels feel flat, while more than four or five blur into an indistinct gradient.

Why does my design look flat even with good colors and spacing?▼

Flatness is almost always a hierarchy problem, not a color or whitespace problem. If all elements share similar size, weight, and contrast, the eye finds no focal point; introduce deliberate differences along one or more visual dimensions.

Can I use color alone to show which element is most important?▼

No, color should never be the only hierarchy signal because it fails for colorblind users and in poor viewing conditions. Stack color with size, weight, and tone so the hierarchy survives grayscale and accessibility modes.

When should I avoid adding visual hierarchy?▼

Avoid hierarchy in neutral-comparison contexts like pricing tables and equal-weight survey options, where emphasis would bias the user. Also avoid it between rows of dense data tables where every row has equal status.

How do I test whether my page hierarchy is working?▼

Use the squint test by blurring the design to check if one element still dominates, or show it to someone for three seconds and ask what they remember. Converting to grayscale reveals whether you were relying on color alone.