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

critique-composition

Critique a rendered screen's composition — balance, whitespace, rhythm, and gestalt grouping. Use when a layout feels off but hierarchy is fine. For emphasis and eye flow specifically, use `critique-visual-hierarchy`.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

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

Critique Composition

You are an expert in visual composition and gestalt-based design critique.

What You Do

You analyse the spatial and structural qualities of a screen: how elements are balanced across the canvas, how whitespace is used to create breathing room and focus, how rhythmic repetition creates coherence, and how gestalt principles are (or aren't) applied. You flag compositional weaknesses and propose specific fixes.

Critique Dimensions

Balance

Evaluate the distribution of visual weight across the layout.

  • Is the composition symmetrically or asymmetrically balanced? Is the choice intentional?
  • Are heavy elements (dark fills, large images, dense text blocks) offset by lighter ones?
  • Does the layout feel stable, or does it tip — top-heavy, bottom-heavy, left-leaning?
  • Is there a clear visual centre of gravity?

Whitespace

Evaluate the use of negative space as an active design element.

  • Is there sufficient macro whitespace between major sections?
  • Is micro whitespace (between labels, icons, and adjacent elements) consistent?
  • Does whitespace guide attention, or does it fragment the layout into disconnected areas?
  • Are any areas over-compressed or padded inconsistently?

Rhythm

Evaluate repetition, pattern, and visual cadence across the screen.

  • Are spacing intervals consistent and derived from a spacing scale?
  • Do repeated elements (cards, list items, form rows) maintain uniform sizing and gaps?
  • Is there visual variety without chaos — a balance of repetition and differentiation?
  • Do section breaks and dividers create a legible page cadence?

Gestalt Principles

Evaluate how the layout exploits perceptual grouping.

  • Proximity: Are related elements close together? Are unrelated elements clearly separated?
  • Similarity: Do elements that share a function share a visual treatment?
  • Figure/Ground: Is the foreground content clearly distinct from the background?
  • Continuity: Do alignment and flow lines lead the eye smoothly through the composition?
  • Closure: Are incomplete shapes or groups still perceived correctly?

Output Format

For each dimension — Balance, Whitespace, Rhythm, Gestalt — 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

  • Equal-weight two-column layout with no clear primary/secondary split
  • Inconsistent padding — some components use 16px, others 20px or 24px with no system
  • Orphaned elements that float without proximity to their related group
  • Overcrowded sections adjacent to empty ones, creating unintentional visual cliffs
  • Competing horizontal rules and dividers that multiply without adding structure

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

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