
Millers Law
- 620 installs
- 2k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
millers-law is a Claude Code skill that applies cognitive chunking principles to interface design so developers can group information into roughly four-item clusters that respect working memory limits and improve scanabi
About
millers-law is an agent skill from owl-listener/designer-skills grounded in cognitive psychology for information design. George Miller's 1956 research proposed working memory holds 7 ± 2 items, though Nelson Cowan's 2001 work suggests a tighter meaningful chunk limit near four items for interface design. The skill guides developers to chunk navigation menus, form fields, dashboard metrics, and content blocks into scannable groups rather than misapplying the classic seven-item rule. Frontend engineers and designers reach for millers-law when menus feel overwhelming, settings pages sprawl, or users struggle to recall options on mobile screens. The skill outputs concrete grouping recommendations aligned to working-memory research for clearer hierarchy and faster comprehension.
- millers-law
Millers Law by the numbers
- 620 all-time installs (skills.sh)
- +61 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #625 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill millers-lawAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 620 |
|---|---|
| repo stars | ★ 2k |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you chunk UI information for working memory?
Use millers-law for development tasks
Who is it for?
Frontend developers or designers restructuring crowded menus, settings screens, or data-dense dashboards for better scanability.
Skip if: Backend API design or database schema normalization where working-memory chunking does not apply.
When should I use this skill?
The user asks to simplify navigation, reduce cognitive load, apply Miller's Law, or group interface elements for better readability.
What you get
Chunked navigation groupings, reorganized form field sections, and interface hierarchy recommendations with grouped labels.
- Chunked navigation structure
- Regrouped form or dashboard layout recommendations
By the numbers
- References Miller's 1956 working-memory limit of 7 ± 2 items
- Cites Nelson Cowan's 2001 research favoring ~4 meaningful chunks for UI design
Files
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-XXXXverification 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 skills
FAQ
How many items should a UI chunk contain per millers-law?
The millers-law skill recommends grouping interface elements into roughly four meaningful chunks, reflecting Nelson Cowan's tighter working-memory research rather than blindly applying Miller's classic 7 ± 2 figure to every menu or form.
What interfaces benefit most from the millers-law skill?
millers-law fits navigation menus, multi-section forms, settings pages, and data dashboards where users must scan and recall options quickly. The skill produces regrouped hierarchies that reduce cognitive load on mobile and desktop layouts.