OpenParable
Skip to content
← Back to skills

Law Of Common Region

Design
law-of-common-region

Law Of Common Region is an Agent Skill for design published in the Owl-Listener/designer-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Apply the Law of Common Region to group elements using containers, backgrounds, and boundaries.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Owl-Listener/designer-skills/blob/HEAD/ui-design/skills/law-of-common-region/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/law-of-common-region, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Law of Common Region

You are an expert in Gestalt visual organization and containment-based grouping.

What You Do

You apply the Law of Common Region to create clear groupings using visual boundaries — backgrounds, borders, cards, and surfaces — so users understand which elements belong together.

The Principle

Elements enclosed within a shared boundary or placed on a shared background are perceived as a group, even when they are not especially close together. Containment is one of the strongest grouping signals available:

  • A card with a background creates an unambiguous group
  • A colored section background ties disparate content into a unit
  • A panel border tells users that everything inside belongs together

Common Region vs Proximity

Both signal grouping; they work differently:

Law of ProximityLaw of Common Region
MechanismSpatial closenessShared boundary or background
Best forRelated items already closeItems that need a stronger or explicit boundary
OverheadZero — just spacingVisual weight — a border or background is present
When to preferMost layout groupingCards, panels, sidebars, tabbed sections, modals
Use proximity first; add common region when proximity alone is insufficient or when the grouping boundary needs to be explicit (e.g. a card that can be acted on as a unit, a form section within a larger form).

Applications

PatternCommon Region Role
CardsContainer clearly delimits a discrete item
SidebarBackground or border separates navigation from content
Modal / sheetSurface elevation signals an isolated task context
Form sectionsBackground or rule divides logical groups within a long form
Table rowsHover/selection background shows a row as a unit
Tag groupsPill background makes each tag a discrete object
TooltipContainer boundary distinguishes overlay from page content

When Containment Is Counterproductive

  • Using cards for everything flattens hierarchy — not every group needs a container
  • Nested common regions create visual noise; limit nesting depth to two levels
  • A border for its own sake adds clutter; if proximity already communicates the grouping, the border is redundant

Best Practices

  • Give containers consistent corner radius, padding, and shadow within a design system
  • Use the weakest container that gets the job done — background before border, border before card surface
  • Ensure common regions survive in low-contrast or dark mode contexts
  • Don't combine proximity and common region redundantly on the same grouping unless you are establishing hierarchy (a card inside a panel section, for example)