AGENT SKILL

law-of-common-region

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`.

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

name
law-of-common-region
description
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`.
disable-model-invocation
true

02 资源文件 3

03 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)

04 同仓库更多 Skills

jorgesolerrr
jorgesolerrr/skills

explainroo

Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.

★ 0
jorgesolerrr
jorgesolerrr/skills

unslop

Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".

★ 0
jorgesolerrr
jorgesolerrr/skills

technical-writing

Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.

★ 0
jorgesolerrr
jorgesolerrr/skills

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

★ 0