AGENT SKILLS · ミッション装備
実際に使われている Agent Skills
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 23,248
- リポジトリ
- 3589
- 最終同期
- 2026/11/04
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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerdesign-review-process
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use design-critique.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerdesign-system-adoption
Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use design-system-governance (design-systems).
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerdesign-token
Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules. Use when establishing the token layer. For auditing existing usage use design-token-audit (designer-toolkit); for multi-brand mapping use theming-system.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerdiary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use usability-test-plan.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerempathy-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.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerheuristic-evaluation
Run an expert review against Nielsen's heuristics and domain criteria, with severity ratings. Use when you need findings without recruiting participants. For a facilitated team feedback session, use design-critique (design-ops).
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerjakobs-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).
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerlaw-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.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerlaw-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.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerlaw-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.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenermicro-interaction-spec
Specify one micro-interaction completely — trigger, rules, feedback, loops, and modes. Use when handing a single interaction to engineering. For motion craft alone use animation-principles; for multi-state components use state-machine.
- 1時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenernaming-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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenernavigation-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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerparallel-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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerpresentation-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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日
owl-listenerprototype-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時間の導入数
- 3
- GitHub Stars
- 3209
- 更新日
- 9月5日