skillZs
LIVE SKILL TAGS
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
REAL INSTALL DATA
← back to all skills
owl-listener/designer-skills983 installs

millers-law

Apply Miller's Law — chunk information into groups of about four to fit working memory. Use when grouping fields, menu items, or steps. For reducing the number of choices offered, use `hicks-law`.

How do I install this agent skill?

npx skills add https://github.com/owl-listener/designer-skills --skill millers-law
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a purely educational resource providing guidance on cognitive psychology principles for design. It contains no code, network requests, or sensitive data access.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/owl-listener/designer-skills/millers-law">View millers-law on skillZs</a>