law-of-common-region

Applies the Law of Common Region to group UI elements using shared containers, backgrounds, and borders.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill law-of-common-region
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: law-of-common-region
Source: https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/law-of-common-region
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill law-of-common-region

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers often struggle to communicate which interface elements belong together, especially when spacing alone is not enough. This Skill applies the Gestalt Law of Common Region to create unambiguous visual groupings using containers, backgrounds, and borders.

Core Features & Use Cases

  • Containment-Based Grouping: Uses cards, panels, colored backgrounds, and borders to signal that enclosed elements form a unit, even when they are not close together.
  • Proximity vs Common Region Guidance: Provides a decision framework for choosing spacing-based grouping versus explicit boundaries, and when to combine them for hierarchy.
  • Pattern Library: Covers concrete applications including cards, sidebars, modals, form sections, table rows, tag groups, and tooltips.
  • Use Case: When designing a settings page with multiple form sections, use this Skill to decide which sections need a card or background boundary versus which can rely on spacing alone, avoiding visual clutter from over-containment.

Quick Start

Ask the AI to review your layout and apply the Law of Common Region to clarify which elements belong together using containers or backgrounds.

Frequently Asked Questions about law-of-common-region

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Law of Common Region in UI design?

The Law of Common Region is a Gestalt principle stating that elements enclosed within a shared boundary or background are perceived as a group. In UI design, cards, panels, and colored sections use this principle to show which elements belong together.

When should I use common region instead of proximity for grouping?

Use proximity first since it adds no visual weight. Add common region when spacing alone is insufficient, when the boundary must be explicit, or when a group acts as a unit, such as a clickable card, a modal, or a form section within a longer form.

Law of Common Region vs Law of Proximity: what is the difference?

Proximity groups elements through spatial closeness with zero visual overhead, while common region uses a shared border or background for a stronger, explicit boundary. Proximity suits most layout grouping; common region suits cards, panels, sidebars, and modals.

Can using too many cards or containers hurt a design?

Yes. Using cards for everything flattens visual hierarchy, and nested common regions create noise. Limit nesting to two levels, prefer the weakest container that works, and skip borders when proximity already communicates the grouping.

How do I keep common region groupings visible in dark mode?

Ensure containers remain distinguishable in low-contrast and dark mode contexts by testing background and border contrast. Consistent corner radius, padding, and shadow within the design system also help groupings survive theme changes.