npx skills add https://github.com/owl-listener/designer-skills
infrasity-labs/dev-gtm-claude-skills
law-of-common-region
Apply the Law of Common Region to group elements using containers, backgrounds, and boundaries.
Installation
npx skills add infrasity-labs/dev-gtm-claude-skills --skill law-of-common-region
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Apply the Law of Common Region — a shared container, background, or border groups elements rega…
1.1K installscuOpt REST server — what it does and how requests flow. Domain concepts; no deploy or client co…
1.3K installsUnauthorized access playbook for common exposed services. Use when Redis, Rsync, PHP-FPM, AJP/G…
2.8K installsQuery and download public cancer imaging data from NCI Imaging Data Commons.
1.3K installsOmniStudio OmniScript creation and validation with 120-point scoring. Use when building guided …
988 installsCross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and …
984 installsAlso in this package
Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.
npx skills add infrasity-labs/dev-gtm-claude-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,865 B -
docs
SUMMARY.md123 B
History
- First seen on skills.sh
- First recorded snapshot · 54 installs
SKILL.md
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)