Law Of Common Region

作者 owl-listener9a6930cf84a8無授權條款2.8K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫4 週前更新

Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use `law-of-proximity`.

僅含說明Design & Creative
AI 產生的概覽

運用格式塔共同區域法則,透過共享容器、背景或邊框將介面元素分組。

功能
此技能引導代理運用格式塔共同區域法則,也就是位於同一邊界或背景內的元素會被視為同一組。它說明這項原理,以對照表格區分它與接近法則,並列出卡片、側邊欄、模態視窗、表單區段、表格列、標籤群組與工具提示等應用情境。它也說明容器何時會造成反效果,並提供最佳實務:容器樣式保持一致、採用最弱的容器手段、在低對比或深色模式下仍可辨識,以及避免重複的分組訊號。
適用情境
當緊湊版面中分組必須保持清楚,或分組邊界需要明確時使用,例如可整組操作的卡片,或較大表單中的表單區段。在決定是否加入容器、背景或邊框而非只靠間距時也適用。
執行需求
不需要任何工具、套件、執行環境、憑證或網路存取;僅為指示性內容,未附帶指令碼。

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)

來源與署名

來源:owl-listener/designer-skills位於ui-design/skills/law-of-common-region提交9a6930c

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架