AGENT SKILLS · ÉQUIPEMENT DE MISSION / owl-listener

owl-listener · Agent Skills

112 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

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
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
1
GitHub Stars
2,9 k
Mis à jour
5 sept.
owl-listener
Communauté

law-of-proximity

Apply the Law of Proximity — spatial closeness groups elements more strongly than any other cue. Use when spacing alone must carry grouping. For grouping via containers use law-of-common-region; via shared appearance use law-of-similarity.

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

law-of-similarity

Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.

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

layout-grid

Define a responsive grid — columns, gutters, margins, and breakpoint behaviour. Use when establishing page structure. For the spacing scale inside components use spacing-system; for cross-device behaviour use responsive-design.

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

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.

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

millers-law

Apply Miller's Law — chunk information into groups of about four to fit working memory. Use when grouping fields, menu items, or steps. For reducing the number of choices offered, use hicks-law.

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

navigation-patterns

Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks. Use when choosing how users move between sections. For the underlying content structure, use information-architecture (ux-strategy).

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

north-star-vision

Articulate a long-horizon product vision that aligns teams and anchors strategy. Use when direction is contested or absent. For near-term project scope, use design-brief.

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

onboarding-design

Design the first-run experience — activation path, progressive disclosure, and time to first value. Use for a user's very first session. For the mechanics of the signup form itself, use form-design.

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

opportunity-framework

Identify, score, and prioritise design opportunities against impact and effort. Use when there are more ideas than capacity. For framing the one you choose, use design-brief.

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

parallel-concepts

Build several genuinely different solutions to the same problem at once, spread across what the user does rather than how it looks. Use when one direction is on the table and the team is about to refine it by default. For choosing between the concepts afterwards, use concept-selection.

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

pattern-library

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.

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

peak-end-rule

Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use zeigarnik-effect.

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

platform-conventions

Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).

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

presentation-deck

Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.

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

prototype-strategy

Choose prototype fidelity and method to match the design question and the decision at stake. Use before building a prototype. For what to test once it exists, use test-scenario.

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

qual-quant-triangulation

Reconcile what the numbers say with what users say, and design the study that settles it rather than restates it. Use when behavioural data and research findings point different ways. For reading the data on its own, use behavioural-analytics; for synthesising interviews on their own, use affinity-diagram.

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

readable-measure

Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.

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

research-repository

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.

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

responsive-design

Design layouts and interactions that adapt across screen sizes and input methods. Use when one design must serve many viewports. For the underlying column grid use layout-grid; for OS-specific patterns use platform-conventions.

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

serial-position-effect

Apply the Serial Position Effect — first and last items in a sequence are recalled best. Use when ordering menus, lists, and steps. For emphasising one item regardless of its position, use von-restorff-effect (ui-design).

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

spacing-system

Create a spacing scale from a base unit with rules for when each step applies. Use when standardising padding and margins. For page-level columns and gutters, use layout-grid.

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

stakeholder-alignment

Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).

installations
1
GitHub Stars
2,9 k
Mis à jour
5 sept.