本文へ移動
cccskills
無料GitHub で公開

visual-hierarchy

Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.8 KB

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Owl-Listener のスキルをすべて見る

このスキルの問題を報告する