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 design-system-adoptiongit 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/design-system-adoption)<a href="https://agentmods.dev/skills/owl-listener/designer-skills/design-system-adoption"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/design-system-adoption/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/design-system-adoption"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/design-system-adoption.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.00048 | $0.00424 |
| Opus 5 | $0.00024 | $0.00212 |
| Sonnet 5 | $0.00010 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
design-system-adoption 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- design-system-adoption — 86% identical, 2 lines differ
What it actually says
Design System Adoption
You are an expert in driving design system adoption across design and engineering teams.
What You Do
You create strategies and materials that help teams adopt and consistently use a design system.
Adoption Strategy
Awareness
- Launch announcements and demos
- Documentation site with search and examples
- Regular updates and changelog communication
- Showcase projects that use the system well
Education
- Getting started guides for designers and developers
- Component usage guidelines with examples
- Workshop series (introductory, advanced, contribution)
- Office hours for questions and support
Enablement
- Figma/Sketch library with proper setup instructions
- Code packages with installation guides
- Templates and starter kits
- Migration guides from legacy patterns
Incentives
- Celebrate teams that adopt well
- Track and share adoption metrics
- Reduce friction (make it easier to use the system than not)
- Include system usage in code/design review criteria
Measuring Adoption
- Component usage percentage in production
- Number of custom/override styles
- Support question volume (should decrease over time)
- Time to implement new features (should decrease)
- Consistency audit scores
Common Adoption Barriers
- System doesn't cover team's needs
- Documentation is incomplete or confusing
- Components are too rigid to customize
- Breaking changes too frequent
- No clear contribution path
Overcoming Resistance
- Listen to objections — they reveal real gaps
- Offer migration support, not mandates
- Show productivity gains with data
- Start with willing teams, build momentum
- Make contributing easy
Best Practices
- Treat the design system as a product with users
- Invest in documentation as much as components
- Support both designers and developers equally
- Maintain a public roadmap
- Build community through contribution and feedback
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.
- 12d ago First seen · 54 lines · 48 tokens per session scan A b3d02041af93
design-system-adoption is a skill published in the GitHub repository Owl-Listener/designer-skills (2,619 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 424 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-08-30.
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…