Skip to main content
skill CX Codex

law-of-closure — Claude Code skill: boundaries without borders

Teaches the agent to build UI on implied boundaries: drop redundant borders, draw icons from minimal cues, and let negative space carry the structure.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill law-of-closure -a claude-code
Open on GitHub

What law-of-closure does

The skill covers the Law of Closure — the eye completes an incomplete form into a whole one. The practical takeaway: you don't have to draw every edge to mark a boundary. A hint is enough, because the mind fills in the rest.

Four areas get worked through. Icons: a circle with a gap reads as a ring or a progress indicator, an open checkbox border still reads as a square. Containers: a rule above a section, corner accents, a background that fades out at the edge. Grids: consistent left alignment implies a vertical line nobody drew. Scroll: an element clipped at the screen edge signals that more content sits in that direction.

Closure only works when the shape can be isolated. In a busy layout competing partial forms get in the way, so clear the surrounding noise first. Some cases call for a real border instead: when the boundary is the primary grouping signal rather than a supporting one, or when it defines the hit area of an interactive element. In dark mode the skill advises re-checking the result, since negative-space relationships shift with the background and a shape that closes in light mode can feel open in dark.

What it helps with

  • strip borders from blocks while keeping the structure readable
  • build an icon set from minimal cues
  • mark a section boundary with one rule instead of a full outline
  • signal scrollability without an explicit indicator
  • check whether an icon still closes at 16px and 20px

Example prompts for the agent

  • Remove the borders from the product cards and keep only a rule above the section heading
  • Build a progress indicator from an arc with a missing segment
  • Check whether this icon reads at 16px and add detail if the shape doesn't close

How to install law-of-closure

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/law-of-closure/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/law-of-closure/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about law-of-closure

How do I install law-of-closure in Claude?

Run npx skills add Owl-Listener/designer-skills --skill law-of-closure -a claude-code. The skill file lands at ~/.claude/skills/law-of-closure/SKILL.md.

What does law-of-closure do?

It guides the agent toward implied boundaries in UI: removing redundant borders, designing icons from partial forms, and using alignment instead of drawn grid lines.

When should I use an explicit border instead?

When the boundary is the primary grouping signal rather than a supporting one, or when it defines the hit area of an interactive element. For explicit containers the skill points to law-of-common-region.

Source text

SKILL.md · MIT
---
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.

### 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 · Owl-Listener/designer-skills

Similar skills

Everything for Design →

From the same set109

business-design Helps a designer read a P&L, map competitors and argue decisions with metrics when a PM or CFO pushes back. CX Codex +1 1,400installs platform-conventions The skill maps what iOS and Android each mandate in their interfaces, where the two diverge, and when a single cross-platform design makes sense. CX Codex +1 1,100installs law-of-continuity A skill about the Law of Continuity: alignment, arrows and lines set the path the eye follows across an interface. Useful for forms, carousels and timelines. CX Codex +1 1,100installs conversational-ux Designs voice interfaces and chat dialogs: prompt structure and error reprompt ladders. Ideal when speech or chat replaces screens. CX Codex +1 1,100installs law-of-figure-ground A skill that sorts out which layer of an interface reads as foreground and which as background, and helps you set that relationship on purpose. CX Codex +1 1,100installs law-of-similarity Applies the Gestalt Law of Similarity to group UI elements across distance using shared color, shape, and size. Useful for unifying components without altering layout. CX Codex +1 1,100installs serial-position-effect A skill that applies the serial position effect: it tells the agent which items belong first and last, and what lands in the memory valley. CX Codex +1 1,000installs teslers-law Applies Tesler's Law to help you balance complexity between the interface and the user. Useful when designing forms, multi-step flows, and settings. CX Codex +1 1,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor