owl-listener · Agent Skills
出典を確認した実質的な文書を持つ Skill が 125 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
naming-convention
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.
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
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).
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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).
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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).
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
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).
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
state-machine
Model component behaviour as explicit states, events, and transitions. Use when a component has many interacting states that must be exhaustive. For the feel and feedback of a single interaction, use micro-interaction-spec.
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
summarize-interview
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.
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
theming-system
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).
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
typography-scale
Create a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use readable-measure; for judging type on an existing screen use critique-typography (visual-critique).
- 1時間の導入数
- 1
- GitHub Stars
- 3387
- 更新日
- 9月5日
user-flow-diagram
Diagram screen-level paths, decision points, and branch logic. Use when specifying how a feature is traversed. For the emotional end-to-end arc, use journey-map (design-research).
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
user-persona
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.
- 1時間の導入数
- 1
- GitHub Stars
- 2865
- 更新日
- 9月5日
