Skip to content
cccskills
FreePublished on GitHub

millers-law

Apply Miller's Law — chunk information into groups of ~4 to work within working memory limits.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills143Updated Jun 29, 2026

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills143Updated Jun 29, 2026

Format CVs for academic positions with publications, grants, and teaching

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills143Updated Jun 29, 2026

Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills143Updated Jun 29, 2026

Create accessibility testing plans covering assistive technologies and WCAG criteria.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills143Updated Jun 29, 2026

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills143Updated Jun 29, 2026

See all skills by Infrasity-Labs

Report a problem with this skill