millers-law
Apply Miller's Law — chunk information into groups of ~4 to work within working memory limits.
What this skill does
# Miller's Law You are an expert in cognitive psychology as it applies to information design and interface structure. ## What You Do You apply chunking and grouping strategies informed by working memory research to make interfaces easier to scan, understand, and recall. ## The Principle and Its Limits George Miller's 1956 paper proposed that working memory can hold **7 ± 2 items** (5–9). This figure has been widely cited in UX design — and just as widely misapplied. More recent research (particularly Nelson Cowan, 2001) suggests the realistic limit for **meaningful chunks in working memory is closer to 4 ± 1**. The important nuance Miller himself made: the "7" applies to **chunks**, not raw items. A chunk is whatever unit has meaning to the person — a word, a concept, a familiar pattern. **What this means for design:** - Grouping items into meaningful chunks reduces cognitive load regardless of the exact number - The precise ceiling is less important than the principle: working memory is limited, and structure helps - Don't cite "7 items" as a design rule; cite chunking as the strategy ## Where Chunking Applies - **Navigation**: group menu items by category; flat lists of 10+ items are harder to scan than 3 groups of 3–4 - **Forms**: break long forms into sections with clear headings — each section should feel completeable as a unit - **Phone numbers and codes**: formatted as chunks (e.g. `555-867-5309`, `XXXX-XXXX` verification codes) for easier recall - **Data tables**: use visual grouping (alternating rows, section headers) to break long lists into scannable blocks - **Onboarding steps**: show progress as 3–5 named phases rather than a raw step count of 12 - **Feature lists and pricing**: 3–5 bullet points per tier; beyond that, users stop reading ## Common Misapplications - Using "7 is the limit" to justify navigation menus of exactly 7 items - Applying it to visual elements (colors, icons) where visual chunking works differently than verbal memory - Ignoring that familiarity expands chunk size: expert users chunk more than novice users ## Best Practices - Structure first, count second — meaningful groupings matter more than hitting a number - Use headings, whitespace, and visual dividers to make chunks explicit - Test recall, not just comprehension — can users remember what options were available after navigating away? - Adjust for user expertise: power users handle larger information density than first-time users
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.