ui-visual-hierarchy

Review and improve UI visual hierarchy using size, weight, color, and spacing principles.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill ui-visual-hierarchy-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-visual-hierarchy
Source: https://github.com/pnewsam/skills/tree/main/archive/ui-visual-hierarchy
Command: npx skills add https://github.com/pnewsam/skills --skill ui-visual-hierarchy-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces often fail because everything competes for attention — secondary metadata looks as heavy as primary content, multiple filled buttons fight for clicks, and users cannot tell where to look first. This Skill provides a structured decision framework for diagnosing and fixing visual hierarchy problems so the most important content is visually dominant. ## Core Features & Use Cases - Squint Test Diagnosis: Evaluate whether primary headings, CTAs, and sections stand out when details blur, and identify unintended attention-grabbers. - Four Levers of Visual Weight: Apply size, weight, color/contrast, and position/space adjustments with concrete rules (e.g., two weight steps for clear contrast, de-emphasize before amplifying). - Content Chunking & Progressive Disclosure: Group content into 3-7 item chunks with clear labels, and hide advanced settings, secondary metadata, and rare actions behind reveal triggers. - Scanning Pattern Guidance: Design for F-pattern, Z-pattern, and layer-cake scanning based on content type. - Use Case: A settings page has 8 equally weighted sections and three filled buttons per card. Use this Skill to get a structured review table recommending chunking into 3 categories and demoting secondary actions to text buttons. ## Quick Start Review this settings page for visual hierarchy problems and recommend fixes using the squint test and primary-secondary-tertiary tiers.

Frequently Asked Questions about ui-visual-hierarchy

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

FAQPage Schema
How do I fix visual hierarchy on a cluttered UI page?▼

Start with the squint test: blur the page and check what still stands out. De-emphasize secondary elements first by reducing color, contrast, and border weight, then increase size or weight of the primary element only if it still does not dominate.

What is the squint test in UI design?▼

The squint test means squinting at a page until details blur to see what still stands out, simulating a first-time visitor's eye. A page passes when the primary heading and main CTA are most prominent and no unintended element grabs attention.

How many items should a content chunk contain?▼

Aim for 3-7 items per chunk, matching working memory limits. Split chunks with 10 or more items into sub-chunks, and merge chunks with only 1-2 items into neighboring groups.

When should I use progressive disclosure in a UI?▼

Hide advanced settings, secondary metadata, detailed explanations, and rarely used actions behind reveal triggers like toggles, tooltips, or overflow menus. Always keep primary content, critical status indicators, and primary actions visible.

What is the difference between F-pattern and Z-pattern scanning?▼

F-pattern scanning applies to text-heavy pages where users read the first lines fully then scan vertically. Z-pattern applies to visual pages like landing pages, where eyes move across the top, diagonally down, then across the bottom.

Why does my UI feel like everything competes for attention?▼

This happens when features accumulate at equal visual weight, leaving nothing primary. Identify the 1-2 primary elements, demote everything else to secondary or tertiary tiers, and use muted colors for common statuses so bright colors signal only what needs attention.