Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Owl-Listener/designer-skills --skill millers-lawgit clone --depth 1 https://github.com/Owl-Listener/designer-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/owl-listener/designer-skills/millers-law)<a href="https://agentmods.dev/skills/owl-listener/designer-skills/millers-law"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/millers-law/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/millers-law"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/millers-law.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.00599 |
| Opus 5 | $0.00023 | $0.00300 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
millers-law scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 32 lines · 46 tokens per session scan A 4245b9110c04
millers-law is a skill published in the GitHub repository Owl-Listener/designer-skills (2,619 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 599 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
ui-review
Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.
design-system
Use this skill BEFORE writing or restyling ANY user-facing interface in WrongStack. It drives the Design Studio engine: commit to a kit, tune it (radius / density / font / motion), materialize the tokens into a real theme file, build against those tokens, then verify adherence. Trigger it whenever the user asks to…
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.
anti-slop-frontend
A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…
frontend-mockup-loop-dashboard
Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…