@owl-listener

test-scenario structures the anatomy of usability test scenarios with context, tasks, success criteria, and observation guides. covers two task types (exploratory and specific) but lacks procedural depth for practitioners.

design-rationale teaches how to structure and articulate reasoning behind design choices by connecting decisions to evidence, user needs, and business goals through a seven-part template.

usability-test-plan structures test design across research questions, methodology, participant screening, task scenarios, metrics, facilitation guidance, data collection, analysis, and pilot validation. covers moderated and unmoderated approaches.

component-spec guides creation of design system specifications covering anatomy, variants, states, props, accessibility, and usage patterns for both designers and developers.

jobs-to-be-done maps user motivations across functional, emotional, and social dimensions to reframe product thinking using structured job statements and persona-outcome tables.

documentation-template provides structured scaffolding for design system artifact documentation across components, patterns, and foundations, with prescribed fields and formatting conventions but minimal operational guidance.

presentation-deck provides templated structures for four common design presentation types, with a six-element universal scaffold (hook, context, journey, solution, evidence, ask) to guide narrative arc and stakeholder alignment.

accessibility-test-plan outlines a multi-layered testing strategy combining automated tools, manual checks, assistive technology validation, and user testing. coverage spans wcag principles and specific at technologies like screen readers and voice control.

affinity-diagram synthesizes qualitative research by clustering observations into themed hierarchies with insight statements. intended for ux researchers organizing interview notes, surveys, and field data into actionable design patterns.

design-sprint-plan covers the five-day google design sprint methodology with daily breakdowns from challenge definition through prototype testing, including variations for compressed and remote contexts.

empathy-map guides teams through synthesizing user research into a four-quadrant visualization (says, thinks, does, feels) with goals and pain points, outputting a collaboratively refined research artifact.

card-sort-analysis provides a framework for extracting actionable ia recommendations from card sort studies by identifying grouping patterns, flagging ambiguous items, and proposing navigation structures grounded in participant mental models.

version-control-strategy outlines naming conventions and semantic versioning patterns for design files, component libraries, and assets, but lacks actionable procedures and failure-mode coverage.

design-brief provides a template structure for creating project briefs with problem statements, audience definition, success criteria, and scope constraints, but lacks actionable procedural guidance for execution.

user-persona guides synthesis of research data into archetypical user personas with behavioral patterns, goals, and frustrations for product and ux design teams.

theming-system outlines a three-layer token architecture (global, semantic, component) for multi-brand and multi-mode design systems. covers color modes, brand variants, and density options with dark mode guidance but lacks actionable implementation steps.

typography-scale defines a modular type system with predefined size, weight, and line-height values. lacks procedural guidance on ratio selection, implementation, or adaptation across contexts.

design-qa-checklist provides categorical checklists for verifying visual accuracy, layout, and interaction states, but lacks procedural clarity on execution, triggering conditions, and failure recovery.

pattern-library documents reusable design patterns through problem statements, solution anatomy, variants, behaviors, examples, and accessibility guidance. emphasizes problem-first thinking and anti-pattern callouts to build connected pattern graphs.

handoff-spec catalogs categories of design specification elements (visual, interaction, content) for developer handoff documents. lacks procedural steps, decision logic, and failure modes.

opportunity-framework structures prioritization using multiple evaluation models (impact-effort matrix, rice scoring, kano model). produces ranked opportunity lists with rationale and dependencies, but lacks concrete procedural steps.

design-principles helps teams articulate actionable, memorable principles that resolve trade-offs and guide decisions. covers principle qualities, structure template, and a six-step workshop process.

design-critique outlines a feedback framework and conversation structure for facilitating design reviews, but lacks procedural specificity and actionable decision-making guidance.

stakeholder-alignment guides teams in building shared understanding through structured artifacts like raci matrices, decision frameworks, and communication plans. covers role definition and conflict navigation but lacks procedural depth.

design-token-audit catalogs visual token adoption and inconsistencies across products, identifying gaps between actual usage and design system coverage, but lacks executable procedure and concrete decision criteria.

visual-hierarchy documents the core mechanics of establishing visual hierarchy through size, weight, color, spacing, and positioning, but lacks actionable procedure and failure handling.

state-machine codifies finite state machine patterns for predictable ui behavior by constraining transitions between explicit states and events, reducing impossible states through declarative guards and actions.

design-token describes naming patterns and token hierarchies for design systems, but lacks procedural steps for implementation, edge case handling, or concrete trigger scenarios.

color-system provides a descriptive framework for organizing palettes and accessibility rules, but lacks actionable procedures, specific trigger scenarios, and failure recovery guidance needed to execute systematically.

design-review-process outlines three review gates with domain-specific criteria for concept, design, and pre-handoff stages, but lacks procedural depth, trigger specificity, and failure recovery mechanics.

data-visualization covers chart selection across common use cases (comparison, trend, distribution, relationship) and articulates basic design principles like data-ink ratio and axis labeling, but lacks procedural depth and concrete implementation guidance.

accessibility-audit outlines wcag 2.2 principles and severity ratings for identifying barriers, but lacks concrete procedural steps, specific trigger phrases, and actionable remediation workflows.

responsive-design covers layout adaptation principles and pattern names without providing actionable step sequences, decision criteria, or failure recovery paths. references breakpoints and techniques but lacks implementation procedure.

diary-study-plan provides a minimal template for designing longitudinal diary studies, but lacks actionable procedure depth, specific research workflows, and recovery guidance.

Create a consistent spacing system based on a base unit with contextual application rules.

Summarize a user interview transcript into structured insights with key themes, quotes, and action items. Use after conducting user interviews to extract and…

Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure…

Craft portfolio-ready case studies that tell the story of a design project.

Define UX metrics and KPIs that connect design decisions to measurable business and user outcomes.

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

team-workflow — an installable skill for AI agents, published by owl-listener/designer-skills.

Create a holistic experience map showing the full ecosystem of user touchpoints, channels, and relationships.

Create an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a…

Create adoption strategies and materials to drive design system usage across teams.

gesture-patterns — an installable skill for AI agents, published by owl-listener/designer-skills.

Conduct a structured competitive analysis comparing UX patterns, features, strengths, and gaps across rival products.

feedback-patterns — an installable skill for AI agents, published by owl-listener/designer-skills.

Establish a naming convention system for design elements, components, and tokens with clear rules and examples.

Design click/first-click tests to evaluate navigation and information findability.

Articulate a compelling north-star product vision that aligns teams and inspires strategic design decisions.

Design error prevention, detection, and recovery experiences.

Conduct expert heuristic evaluations using Nielsen's heuristics and domain-specific criteria.

Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.

Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.

Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.

Design loading, skeleton, and progressive content reveal patterns.

Specify wireframe layouts with content priority, component placement, and annotation.

Choose the right prototyping fidelity and method for the design question.

Apply animation principles to UI motion for purposeful, polished interactions.

Write effective UI copy including microcopy, error messages, empty states, and CTAs.

Design effective dark mode interfaces with proper color adaptation, contrast, and elevation.

Create user flow diagrams showing paths, decisions, and branch logic.

Define an illustration style guide with visual language, color usage, and application rules.