owl-listener
112 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
owl-listeneraffinity-diagram
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use summarize-interview; for one segment's inner state use empathy-map.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerbehavioural-analytics
Read funnels, retention curves, and event data as a designer — separating a design problem from a tracking artefact. Use when handed product data you did not design and asked why people drop off. For choosing what to measure, use metrics-definition (ux-strategy); for running a controlled test, use a-b-test-design (prototyping-testing).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerbusiness-design
Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use design-negotiation (designer-toolkit).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercard-sort-analysis
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use information-architecture (ux-strategy).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercase-study
Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use presentation-deck.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerclick-test-plan
Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use test-scenario.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercolor-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).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercompetitive-analysis
Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use jakobs-law (interaction-design).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercomponent-spec
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.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerconcept-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.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercontent-strategy
Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use ux-writing (designer-toolkit); for structural hierarchy use information-architecture.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerconversational-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.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercritique-affordance
Critique a rendered screen's affordances — what looks clickable, state visibility, CTA clarity, and action discoverability. Use when reviewing an existing screen. For sizing and positioning targets in new work, use fitts-law (interaction-design).
- 導入数
- 1
- GitHub Stars
- 2934
- 更新日
- 9月5日
owl-listenercritique-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).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercritique-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).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercritique-typography
Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use typography-scale (ui-design).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenercritique-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).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerdark-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.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerdesign-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.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerdesign-critique
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use heuristic-evaluation (prototyping-testing).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerdesign-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerdesign-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
- 導入数
- 1
- GitHub Stars
- 2926
- 更新日
- 9月5日
owl-listenerdesign-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).
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
owl-listenerdesign-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.
- 導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日