law-of-proximity
Apply the Law of Proximity to group related elements through spatial relationships.
What this skill does
# 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
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.