AGENT SKILLS · ÉQUIPEMENT DE MISSION / owl-listener

owl-listener · Agent Skills

125 Skills avec une documentation substantielle et des sources vérifiées. Ouvrez une fiche pour lire les instructions originales et vérifier le paquet et son installation.

owl-listener
Communauté

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

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

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

Installations / 1h
1
GitHub Stars
3,4 k
Mis à jour
5 sept.
owl-listener
Communauté

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

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

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

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

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

Installations / 1h
1
GitHub Stars
3,4 k
Mis à jour
5 sept.
owl-listener
Communauté

design-qa-checklist

Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use handoff-spec.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

design-rationale

Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use design-negotiation.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

design-sprint-plan

Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use team-workflow.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

design-system-governance

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

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

design-token-audit

Audit token usage across a product for coverage, drift, and hard-coded values. Use when tokens exist and you suspect they are being bypassed. For defining tokens in the first place, use design-token (design-systems).

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

empathy-map

Build a Says, Thinks, Does, Feels map for one user or segment. Use when sharing user understanding quickly. For a composite archetype with goals and behaviours use user-persona; for cross-session themes use affinity-diagram.

Installations / 1h
1
GitHub Stars
3,4 k
Mis à jour
5 sept.
owl-listener
Communauté

error-handling-ux

Design error prevention, detection, and recovery across a product — message content, placement, and escape routes. Use when errors span multiple flows. For validation inside a single form, use form-design.

Installations / 1h
1
GitHub Stars
3,4 k
Mis à jour
5 sept.
owl-listener
Communauté

fitts-law

Apply Fitts's Law — target acquisition time depends on size and distance. Use when sizing and positioning controls, especially for touch. For how many controls to show at once, use hicks-law.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

form-design

Design a form end to end — field order, grouping, validation, and completion. Use when the artifact is a form. For product-wide error strategy use error-handling-ux; for first-run signup use onboarding-design.

Installations / 1h
1
GitHub Stars
3,4 k
Mis à jour
5 sept.
owl-listener
Communauté

gesture-patterns

Design gesture interactions for touch and pointer — swipe, drag, long-press, and their discoverability. Use when input is gestural. For OS-standard gestures on iOS and Android, use platform-conventions (ui-design).

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

handoff-spec

Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

icon-system

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

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

interview-script

Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use summarize-interview.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

jakobs-law

Apply Jakob's Law — users expect your product to work like the others they already use. Use when deciding whether to innovate on a familiar pattern. For OS-mandated conventions specifically, use platform-conventions (ui-design).

Installations / 1h
1
GitHub Stars
3,4 k
Mis à jour
5 sept.
owl-listener
Communauté

journey-map

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

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

law-of-closure

Apply the Law of Closure — the eye completes implied shapes from partial forms. Use when reducing visual weight by dropping borders or letting negative space suggest structure. For explicit containers, use law-of-common-region.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

law-of-common-region

Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

law-of-continuity

Apply the Law of Continuity — the eye follows alignment and unbroken paths. Use when sequencing steps, aligning content, or designing carousels and timelines. For grouping rather than sequencing, use law-of-proximity.

Installations / 1h
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

law-of-figure-ground

Apply the Law of Figure-Ground — establish which layer is foreground and actionable versus background. Use when designing modals, overlays, and depth. For emphasising one element among peers, use von-restorff-effect.

Installations / 1h
1
GitHub Stars
3,4 k
Mis à jour
5 sept.