
Law Of Common Region
- 626 installs
- 2k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
law-of-common-region is a Claude Code design skill that applies Gestalt containment grouping with borders, backgrounds, and cards for developers who need clearer UI component relationships.
About
law-of-common-region is a designer-skills agent skill from owl-listener/designer-skills focused on Gestalt visual organization through shared boundaries. The skill teaches that elements inside a common container or background are perceived as one group even when spacing is loose, making containment one of the strongest grouping signals in interfaces. Developers invoke law-of-common-region when forms, dashboards, or settings panels feel visually flat and users cannot tell which labels, inputs, and actions belong together. The skill guides card surfaces, bordered sections, shared backgrounds, and boundary treatments in React, CSS, or design handoffs. Outputs are concrete grouping recommendations tied to real UI regions rather than abstract design theory alone.
- law-of-common-region
Law Of Common Region by the numbers
- 626 all-time installs (skills.sh)
- +64 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #607 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill law-of-common-regionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 626 |
|---|---|
| repo stars | ★ 2k |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you group UI elements with containers and borders?
Use law-of-common-region for development tasks
Who is it for?
Frontend developers and designers refining component layouts where related controls need stronger visual grouping without adding more labels.
Skip if: Interfaces where spatial proximity alone already communicates grouping and added containers would add visual noise.
When should I use this skill?
A developer asks how to group related UI elements with cards, borders, backgrounds, or shared containers in a layout.
What you get
Grouped UI regions using cards, borders, and shared backgrounds that clarify element relationships.
Files
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 Proximity | Law of Common Region | |
|---|---|---|
| Mechanism | Spatial closeness | Shared boundary or background |
| Best for | Related items already close | Items that need a stronger or explicit boundary |
| Overhead | Zero — just spacing | Visual weight — a border or background is present |
| When to prefer | Most layout grouping | Cards, 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
| Pattern | Common Region Role |
|---|---|
| Cards | Container clearly delimits a discrete item |
| Sidebar | Background or border separates navigation from content |
| Modal / sheet | Surface elevation signals an isolated task context |
| Form sections | Background or rule divides logical groups within a long form |
| Table rows | Hover/selection background shows a row as a unit |
| Tag groups | Pill background makes each tag a discrete object |
| Tooltip | Container 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)
Related skills
FAQ
What is the Law of Common Region in UI design?
law-of-common-region applies the Gestalt principle that elements inside a shared boundary or background are perceived as a group. The skill recommends cards, borders, and surface backgrounds so users understand which labels, inputs, and actions belong together.
When should developers use law-of-common-region?
law-of-common-region fits when related controls are not close enough for proximity alone or when a screen needs explicit sections. Developers use it for forms, settings panels, and dashboards where containment clarifies grouped UI regions.