infrasity-labs/dev-gtm-claude-skills

visual-hierarchy

Establish clear visual hierarchy through size, weight, color, spacing, and positioning.

First seen Jun 30, 2026

Installation

$ npx skills add infrasity-labs/dev-gtm-claude-skills --skill visual-hierarchy

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.

npx skills add infrasity-labs/dev-gtm-claude-skills

Browse all from infrasity-labs/dev-gtm-claude-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 123
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,740 B
  • docs SUMMARY.md 111 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 56 installs

SKILL.md

Visual 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

  1. Primary: Page title, primary CTA — seen first
  2. Secondary: Section headings, key content — scanned next
  3. Tertiary: Supporting text, metadata — read on demand
  4. 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