Agent skill

Law Of Closure

by Owl-Listener in Owl-Listener/designer-skills

Apply the Law of Closure — the eye completes implied shapes from partial forms.

MITAuto-check passedFrontend & Design

Install Law Of Closure

skills CLI
$ npx skills add Owl-Listener/designer-skills --skill law-of-closure -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Owl-Listener/designer-skills law-of-closure --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ui-design/skills/law-of-closure .claude/skills/law-of-closure && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
law-of-closure
GitHub stars
2.9k
Token cost
~1.2k tokens
SKILL.md length
657 words
Files
1
Skills in repo
107
Repo updated
First seen
Licence
MIT

At a glance

Apply the Law of Closure — the eye completes implied shapes from partial forms.

  • Reducing visual weight by dropping borders
  • SKILL.md covers What You Do, The Principle, Applications in UI Design and Closure and Negative Space, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Letting negative space suggest structure

What it does

Law Of Closure is an agent skill from Owl-Listener/designer-skills. 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.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.

When your agent uses it

  • Reducing visual weight by dropping borders
  • Letting negative space suggest structure

Example prompts

  • “/law-of-closure”

What it can do on your machine

Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Law Of Closure loads about 1.2k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 657 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 657 words, ~1,156 tokens.

Download SKILL.mdSave it as .claude/skills/law-of-closure/SKILL.md (or your agent's skills folder).
name
law-of-closure
description
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`.

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.

Show full SKILL.md (280 more words)Show less
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

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ui-design/skills/law-of-closure of Owl-Listener/designer-skills.

Open the folder on GitHubat commit 9a6930c

Compare with similar skills

Law Of Closure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Law Of Closure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Law Of Closure this skillOwl-Listener/designer-skills2.9k—~1.2kAutomated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k40 repos~769Automated safety check: PassApache-2.0
React Doctormakeplane/plane61k12 repos~657Automated safety check: PassAGPL-3.0
Impeccablebestofjs/bestofjs3.1k26 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone

Similar skills

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 40 repos~769 tokens
    Frontend & DesignAuto-check passed
  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    61k GitHub starsUsed in 12 repos~657 tokens
    Frontend & DesignAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed

More from Owl-Listener/designer-skills

All 107 skills in this repo
  • A B Test Design

    Owl-Listener/designer-skills

    Design an A/B experiment — hypothesis, variants, primary metric, and sample size.

    2.9k GitHub starsUsed in 1 repo~472 tokens
    Auto-check passed
  • Accessibility Test Plan

    Owl-Listener/designer-skills

    Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.

    2.9k GitHub starsUsed in 1 repo~478 tokens
    Auto-check passed
  • Aesthetic Usability

    Owl-Listener/designer-skills

    Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.

    2.9k GitHub starsUsed in 1 repo~678 tokens
    Auto-check passed
  • Affinity Diagram

    Owl-Listener/designer-skills

    Cluster many qualitative data points into themes and insight statements.

    2.9k GitHub starsUsed in 1 repo~520 tokens
    Auto-check passed
  • Animation Principles

    Owl-Listener/designer-skills

    Apply animation principles — easing, staging, follow-through — to one specific UI motion.

    2.9k GitHub starsUsed in 1 repo~492 tokens
    Auto-check passed
  • Business Design

    Owl-Listener/designer-skills

    Read financials, map competitive landscapes, and argue design decisions in the language of value.

    2.9k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

Questions about Law Of Closure

What does Law Of Closure do?

Apply the Law of Closure — the eye completes implied shapes from partial forms. Law Of Closure is an agent skill from Owl-Listener/designer-skills. Apply the Law of Closure — the eye completes implied shapes from partial forms.

When should I use Law Of Closure?

Law Of Closure fits situations like: reducing visual weight by dropping borders; letting negative space suggest structure.

How do I install Law Of Closure in Claude Code?

Run `npx skills add Owl-Listener/designer-skills --skill law-of-closure -a claude-code`. Or copy the skill folder (ui-design/skills/law-of-closure in Owl-Listener/designer-skills) into .claude/skills/law-of-closure in your project. Claude Code loads it when a task matches its description.

How do I install Law Of Closure in Codex?

Run `npx skills add Owl-Listener/designer-skills --skill law-of-closure -a codex`. Or copy the skill folder (ui-design/skills/law-of-closure in Owl-Listener/designer-skills) into .agents/skills/law-of-closure in your project. Codex loads it when a task matches its description.

Can I use Law Of Closure in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill law-of-closure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/law-of-closure, .gemini/skills/law-of-closure, .github/skills/law-of-closure and .opencode/skills/law-of-closure in your project.

What does Law Of Closure need to run?

SKILL.md names no scripts, command-line tools or credentials: Law Of Closure is instructions for the agent only.

Does Law Of Closure access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Law Of Closure safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Law Of Closure use?

Law Of Closure is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Law Of Closure use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Law Of Closure?

Skills that share tags, products or a category with Law Of Closure: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Law Of Closure?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.

Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.