UI/UX、ロゴ、スライド、画像生成（7,385 件）
Implementing CSS/JS animations for hover effects, loading states, modal transitions, and gesture interactions. Use for meaningful motion, interaction feedback, or performance-safe animation.
日本語の概要は準備中です。原文の説明を表示しています。
Building rapid prototypes for frontend (UI components/pages) and backend (API mocks, simple servers). Use to validate new features or turn ideas into working demos. Working software over perfection.
日本語の概要は準備中です。原文の説明を表示しています。
Enumerating failure modes via pre-mortem analysis. Systematically identifies failure scenarios for plans, designs, and features, scoring them with RPN/AP. Does not write code.
日本語の概要は準備中です。原文の説明を表示しています。
Designing and reviewing APIs: OpenAPI spec generation, versioning strategy, breaking change detection, REST/GraphQL best practices. Use for API design or OpenAPI specs.
日本語の概要は準備中です。原文の説明を表示しています。
Navigating the skill ecosystem and guiding onboarding. Lists agents, recommends best fit for tasks. Don't use for task execution (Nexus), agent design (Architect).
日本語の概要は準備中です。原文の説明を表示しています。
Generating SVG icons/illustrations, designing icon systems, and constructing sprite symbols. Use when vector assets are needed.
日本語の概要は準備中です。原文の説明を表示しています。
Defining and managing design tokens, applying token systems to existing codebases, building design system foundations. Use for spacing, color, typography, dark mode, cross-platform output.
日本語の概要は準備中です。原文の説明を表示しています。
Implementing production iOS/Android/macOS native features (SwiftUI, Compose) and iterating a screen against a reference design. Not for cross-platform RN/Flutter (Forge prototypes only; production is out of scope) or web (Artisan).
日本語の概要は準備中です。原文の説明を表示しています。
Extracting and structuring design context from Figma via MCP Server for downstream implementation agents. Use for Figma-to-code bridging or Code Connect management.
日本語の概要は準備中です。原文の説明を表示しています。
System-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries", or before an ADR. Hands off to /ship:write-docs to record the decision. Not implementation planning (/ship:design — that turns a decided design into stories).
日本語の概要は準備中です。原文の説明を表示しています。
Plan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design approach", "scope", or any coding task needing a plan. Not system-design thinking (/ship:arch-design) or full /ship:auto.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself (architecture, trade-offs, failure modes) use /ship:arch-design first — it hands back here to record the decision.
日本語の概要は準備中です。原文の説明を表示しています。
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Design a worked example fading sequence from fully worked examples through to independent practice. Use when teaching procedures, algorithms, or multi-step processes to novice learners.
日本語の概要は準備中です。原文の説明を表示しています。
Design a variation theory task using contrast, separation, and fusion to teach critical features of a concept. Use when students confuse similar concepts or fail to discern key distinctions.
日本語の概要は準備中です。原文の説明を表示しています。
Design finalization: generates production-quality Pretext-native HTML/CSS. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Design a practitioner inquiry cycle from research question through data collection to evidence-informed action. Use when starting action research, teacher-led investigation, or professional inquiry.
日本語の概要は準備中です。原文の説明を表示しています。
Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Design the transition from worked examples to independent problem-solving using expertise-reversal principles. Use when students follow examples but cannot solve problems alone.
日本語の概要は準備中です。原文の説明を表示しています。
Generates multiple means of engagement, representation, and action/expression for a given learning goal. Produces specific, practical alternatives — not generic options — and recommends the highest-impact single change.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview... (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Design an uninterrupted work cycle with choice-based activities structured within a realistic time block. Use when planning Montessori-style independent work periods or extended choice time.
日本語の概要は準備中です。原文の説明を表示しています。
Design trauma-informed classroom practices that prioritise safety, predictability, connection, and regulation. Use when student behaviour may be trauma-related or the class needs a sensitive approach.
日本語の概要は準備中です。原文の説明を表示しています。