본문으로 건너뛰기
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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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-skills3천2026년 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-skills3천2026년 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-skills3천2026년 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-skills3천2026년 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-skills3천2026년 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-skills3천2026년 9월 6일 업데이트

Owl-Listener의 스킬 모두 보기

이 스킬의 문제 신고