Owl-Listener

Owl-Listener/designer-skills

Skill Claude CodeCodex

Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use user-persona.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use experience-map (ux-strategy); for screen-level paths use user-flow-diagram (prototyping-testing).

Owl-Listener/designer-skills

Skill Claude CodeCodex

Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use affinity-diagram.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).

Owl-Listener/designer-skills

Skill Claude CodeCodex

Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use test-scenario (prototyping-testing).

Owl-Listener/designer-skills

Skill Claude CodeCodex

Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use empathy-map; for motivation framing use jobs-to-be-done.

Owl-Listener/designer-skills

Plugin Claude Code

Build, document, and maintain scalable design systems — from tokens and components to accessibility and theming.

Owl-Listener/designer-skills

Command

Run a comprehensive audit of an existing design system for consistency, completeness, and accessibility.

Owl-Listener/designer-skills

Command

Scaffold a full component specification end to end — props, states, variants, accessibility, and documentation.

Owl-Listener/designer-skills

Command

Extract tokens from an existing design or stylesheet and organise them — naming, structure, and theme mapping.

Owl-Listener/designer-skills

Skill Claude CodeCodex

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).

Owl-Listener/designer-skills

Skill Claude CodeCodex

Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use documentation-template; for a problem-solution pattern use pattern-library.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use design-system-adoption (designer-toolkit); for design file history use version-control-strategy (design-ops).

Owl-Listener/designer-skills

Skill Claude CodeCodex

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.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Generate a reusable documentation scaffold for components, patterns, or guidelines. Use when standardising how the system is documented. For the content of one component's spec, use component-spec.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Specify an icon system — grid, sizing, stroke weight, naming, categories, and implementation. Use when standardising iconography. For broader illustration, use illustration-style (ui-design).

Owl-Listener/designer-skills

Skill Claude CodeCodex

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).

Owl-Listener/designer-skills

Skill Claude CodeCodex

Define motion tokens — durations, easing vocabulary, and reduced-motion handling — for consistency product-wide. Use when standardising motion across a system. For crafting one specific animation, use animation-principles (interaction-design).

Owl-Listener/designer-skills

Skill Claude CodeCodex

Establish naming rules for components, tokens, and layers with patterns and worked examples. Use when names are inconsistent or being set. For what the tokens actually contain, use design-token.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Structure a pattern entry — problem context, solution, usage examples, and related patterns. Use when documenting a recurring solution rather than a component. For a single component's API, use component-spec.

Owl-Listener/designer-skills

Skill Claude CodeCodex

Design theming architecture — brand variants, dark mode, and high-contrast — mapped through token layers. Use when one system must serve multiple themes. For a single palette use color-system (ui-design); for dark mode craft use dark-mode-design (ui-design).

Owl-Listener/designer-skills

Plugin Claude Code

Essential designer utilities for writing rationale, building presentations, crafting case studies, UX writing, and driving adoption.

Owl-Listener/designer-skills

Command

Build a design presentation end to end — audience framing, narrative structure, and supporting rationale.