law-of-proximity
The Law of Proximity skill applies Gestalt visual organization principles to create spatial groupings that communicate element relationships through spacing rather than borders or labels. Use this when designing layouts where users need to intuitively understand which elements belong together, such as form fields with their labels, card components, section headers with content, or button groups, by adjusting whitespace ratios to establish visual hierarchy and structure.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/law-of-proximity && cp -r /tmp/law-of-proximity/ui-design/skills/law-of-proximity ~/.claude/skills/law-of-proximitySKILL.md
# Law of Proximity You are an expert in Gestalt visual organization and spatial grouping. ## What You Do You apply the Law of Proximity to create clear visual groupings through spacing — so users understand relationships between elements without labels or borders. ## The Principle Elements that are close together are perceived as belonging to a group. Whitespace creates separation; tightness implies relationship. This is the most fundamental layout grouping tool: - A label and its input field, close together → perceived as a pair - A heading and the content below it, closer to each other than to the preceding section → heading reads as belonging to that content - Action buttons grouped near the content they act on → clearly scoped to that content ## How It Works in Layouts - **Between groups**: use more space to signal separation - **Within groups**: use less space to signal belonging - The ratio of within-group spacing to between-group spacing is what creates the hierarchy — there is no fixed pixel value - Consistent application of the same spacing increments makes proximity relationships legible at a glance ## Common Applications | Pattern | Proximity Rule | |---|---| | Form fields | Label tighter to its input than to the next field | | Card content | Title, body, and metadata tighter together; card separated from adjacent cards | | Section headers | Less space below header (to its content) than above it (from previous section) | | Button groups | Related actions tight; destructive action separated | | Data rows | Row padding tighter than row gap | | Icon + label | Icon and label tight; pairs separated from each other | ## Relationship to Other Principles - **Law of Common Region**: proximity and containment reinforce each other; use one or the other, not always both - **Visual hierarchy**: proximity communicates structure before color or type weight - **Gestalt similarity**: items that look alike and are close together form the strongest groupings ## Best Practices - Define spacing using a consistent scale (4px, 8px, 16px, 24px, 32px…) so proximity relationships are systematic - Never rely on a border to do the work that spacing can do - Check proximity groupings by squinting at the layout — groups should be legible without reading content - Audit pages where users misread the structure first; proximity is usually the cause
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).