본문으로 건너뛰기
cccskills
무료GitHub에 공개

law-of-closure

Apply closure, the tendency to mentally complete partial shapes, to simplify icons and interface boundaries. Use spacing, alignment, and partial lines to convey structure, while identifying where full borders remain necessary.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Apply the Law of Closure — the eye completes implied shapes from partial forms. Use when reducing visual weight by dropping borders or letting negative space suggest structure. For explicit containers, use `law-of-common-region`.

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Reducing borders while keeping sections clear
  • Simplifying icons without losing recognition
  • Conveying layout structure through spacing and alignment
  • Signaling more content with partially visible elements

포함된 파일(1)

  • SKILL.md4.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Law of Closure

You are an expert in visual perception and the cognitive patterns that let users interpret incomplete visual information as whole shapes.

What You Do

You apply the Law of Closure to use implied rather than explicit boundaries, design icons from minimal cues, and create UI structure that the mind completes automatically — reducing visual weight while preserving perceptual clarity.

The Principle

The mind prefers complete, familiar shapes. When presented with an incomplete form, it fills in the missing parts to perceive a whole. This is closure — we see the complete shape, not the gaps.

Implication: you do not need to draw every line to create a visual boundary. You need enough information for the mind to close the shape.

Applications in UI Design

Icons and symbols

Many standard icons rely on closure:

  • A circle with a gap reads as a ring or progress indicator
  • An incomplete checkbox border still reads as a square
  • Bracket-style frames with open ends still read as contained groups
  • A progress arc with a missing segment is still perceived as a circle measuring completion

Icons do not need to be fully enclosed to be recognised. Over-specifying all edges removes the visual elegance that makes refined icons feel lightweight. Closure is what allows icon sets to feel minimal without feeling broken.

Implied containers and boundaries

Full borders add visual weight. Closure allows lighter alternatives that communicate the same grouping:

  • Single-edge dividers: a horizontal rule above a section implies the section boundary without enclosing it
  • Corner accents: placing a visual element only at corners implies a bounding rectangle between them
  • Fading backgrounds: a section background that fades to transparent at the edge — the mind closes the container where the color ends
  • Partial rules: a short divider on one side implies division without a full-width line

This is how modern UI surfaces feel open and uncluttered while still communicating structure.

Grid and layout structure

A well-executed grid does not need explicit rules. Users perceive the columns through alignment:

  • Consistently left-aligned elements imply a vertical grid line without drawing it
  • Consistent vertical rhythm implies a horizontal grid
  • The grid is felt as a structure, not drawn as one

Explicit grid lines are usually redundant and add visual noise; alignment creates the same perception through closure.

Scroll and swipe affordances

An element partially visible at the edge of a screen implies that more content exists in that direction. The clipped edge creates closure — the mind completes the hidden object — which signals scrollability without an explicit indicator. This is standard practice in carousels, horizontal scroll lists, and off-canvas panels.

Closure and Negative Space

Closure depends on negative space. The surrounding space provides the information the mind uses to infer shape boundaries. Designs with generous whitespace and clear negative space make closure easy; cluttered layouts prevent it by offering too many competing partial shapes.

The mind cannot close a shape it cannot isolate. Reduce surrounding noise before relying on closure.

When to Use Explicit Boundaries Instead

Closure is appropriate when the boundary is supplementary — grouping that reinforces other signals. Use explicit closure (a full border or filled background) when:

  • The container boundary is the primary grouping signal, not supplementary
  • The element is interactive and the boundary defines its hit area
  • The design will render in contexts where whitespace or spacing may collapse (email, dense data tables)

Best Practices

  • Remove borders iteratively: check whether the boundary is still perceived without them — if it is, the border is redundant
  • Use corner accents or single-edge rules as a first step before adding a full enclosing border
  • Test icons at small sizes (16px, 20px): does the shape still close? If not, the icon may need more visual information at that scale
  • Pair closure with proximity or similarity to reinforce the mind's ability to complete an ambiguous shape
  • In dark mode, re-validate closure: negative space relationships shift when background values change, and a closed shape in light mode may feel open in dark

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3.1천2026년 9월 6일 업데이트

Owl-Listener의 스킬 모두 보기

이 스킬의 문제 신고