owl-listener · Agent Skills
125 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.
accessibility-audit
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use accessibility-test-plan (prototyping-testing).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
concept-selection
Choose between competing concepts against criteria fixed in advance, and record what each rejected concept was testing. Use when several directions are alive and one has to win. For picking which problem to work on, use opportunity-framework (ux-strategy); for deciding by production traffic, use a-b-test-design.
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
critique-color
Critique a rendered screen's colour — contrast ratios, palette coherence, and semantic meaning. Use when reviewing one screen. For a product-wide WCAG audit use accessibility-audit (design-systems); for building the palette use color-system (ui-design).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
critique-information-density
Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use hicks-law (interaction-design).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
critique-visual-hierarchy
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
dark-mode-design
Adapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use color-system.
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
experience-map
Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use journey-map (design-research); for backstage operations use service-blueprint.
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
loading-states
Design waiting experiences — spinners, skeletons, optimistic updates, and progressive reveal. Use when content takes time to arrive. For the latency budget itself use doherty-threshold; for success confirmation use feedback-patterns.
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
localization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
service-blueprint
Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use experience-map.
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
accessibility-test-plan
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use accessibility-audit (design-systems).
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
color-system
Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use dark-mode-design; for chart palettes use data-visualization; for multi-brand token architecture use theming-system (design-systems).
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
critique-brand-consistency
Critique a rendered screen against mood.md, voice.md, and tokens.md. Use when those brand files exist and you are checking compliance. For defining the visual language itself, use illustration-style (ui-design).
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
critique-composition
Critique a rendered screen's composition — balance, whitespace, rhythm, and gestalt grouping. Use when a layout feels off but hierarchy is fine. For emphasis and eye flow specifically, use critique-visual-hierarchy.
- 1h installs
- 3
- GitHub stars
- 3K
- Updated
- Sep 5
design-brief
Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use north-star-vision; for reusable decision rules use design-principles.
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
design-principles
Define actionable principles that resolve trade-offs when the team disagrees. Use when the same decisions keep getting relitigated. For a single project's framing, use design-brief.
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
design-review-process
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use design-critique.
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
design-system-adoption
Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use design-system-governance (design-systems).
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
design-token
Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules. Use when establishing the token layer. For auditing existing usage use design-token-audit (designer-toolkit); for multi-brand mapping use theming-system.
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
diary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use usability-test-plan.
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
heuristic-evaluation
Run an expert review against Nielsen's heuristics and domain criteria, with severity ratings. Use when you need findings without recruiting participants. For a facilitated team feedback session, use design-critique (design-ops).
- 1h installs
- 3
- GitHub stars
- 3.4K
- Updated
- Sep 5
hicks-law
Apply Hick's Law — decision time grows with the number of simultaneous choices. Use when a screen offers too many options at once. For how many items survive in memory afterwards, use millers-law.
- 1h installs
- 3
- GitHub stars
- 3.2K
- Updated
- Sep 5
