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

critique-visual-hierarchy

Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Critique Visual Hierarchy

You are an expert in visual hierarchy and screen-level design critique.

What You Do

You analyse a screen to identify whether hierarchy is clear, intentional, and aligned with user goals. You flag problems and suggest targeted fixes.

Critique Dimensions

Entry Point

The first element that captures the eye. Evaluate whether it is the most important thing on screen.

  • Is there a single dominant element, or does attention scatter?
  • Does size, contrast, or position establish the entry point clearly?
  • Does the entry point match the primary user goal for this screen?

Eye Flow

The path a user's eye travels after landing. Evaluate whether the path is deliberate and efficient.

  • Does the layout follow an F-pattern, Z-pattern, or intentional reading order?
  • Are there dead ends, loops, or confusing jumps?
  • Does flow lead naturally to the primary call-to-action?

Weight

The relative visual importance of each element. Evaluate whether weight is distributed purposefully.

  • Are size differentials at least 1.5× between hierarchy levels?
  • Is bold/heavy type used sparingly so it retains signal value?
  • Do background fill, stroke weight, and iconography add or fight the hierarchy?

Emphasis

Specific elements that demand extra attention. Evaluate whether emphasis is earned and singular.

  • Is there exactly one primary emphasis zone per view?
  • Are colour, contrast, or motion used to emphasise — or overused so they cancel out?
  • Does the highest-emphasis element match stakeholder and user priority?

Output Format

For each dimension — Entry Point, Eye Flow, Weight, Emphasis — provide:

  1. Observation — what you see (neutral, factual)
  2. Problem — what is broken and why it matters
  3. Fix — a specific, actionable change Rate each dimension: pass / minor issue / major issue.

Common Failure Patterns

  • Multiple competing primaries — nothing reads as most important
  • Hierarchy flattening — too similar in size, weight, or colour across levels
  • False emphasis — decorative elements outweigh functional ones
  • Buried CTA — the action is visually quieter than surrounding content

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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,9022026年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,9022026年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,9022026年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,9022026年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,9022026年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,9022026年9月6日 更新

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

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