law-of-closure
Apply the Law of Closure — the eye completes implied shapes from partial forms
Install / Use
npx skills add Owl-Listener/designer-skills --skill law-of-closureInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of law-of-closure
law-of-closure scores 80/100 on our quality scale, 3641st of 4,700 Development & Engineering skills we index.
Its SKILL.md is 4.5 KB long, well organised into 11 sections and no code examples: a solid amount of guidance for an agent.
With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so law-of-closure is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
law-of-closure compared with similar skills
All 4 of these similar skills score higher than law-of-closure; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| law-of-closure (this skill)by Owl-Listener | 80 | 2.7k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install law-of-closure?
- Run
npx skills add Owl-Listener/designer-skills --skill law-of-closure. The install tabs above show the steps for each supported agent. - Which AI agents does law-of-closure work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is law-of-closure safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is law-of-closure still maintained?
- The repository was last updated about 2 months ago, so law-of-closure is actively maintained.
Skill content
View source on GitHubname: 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.
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
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
