This skill should be used when the user asks to "generate build prompts", "create implementation prompts", "break down the UX spec", "prepare prompts for v0/Bolt/Claude", "sequence the build tasks", or needs to transform UX specifications into sequential, self-contained prompts for UI generation tools.
Generate detailed feature specifications based on the project's feature spec template, using the prototype GDD and roadmap for context. Use this when the user wants to create a feature spec, document a new feature idea, or plan implementation for a game feature.
Orchestrator skill for creating and maintaining the System Context (SSOT). Sequentially executes Observe, Orient, Decide, and Act phases. Representative use cases include (1) Defining initial system boundaries and domain models for a new project, (2) Realigning documentation with codebase reality to correct drift, and (3) Establishing a grounded SSOT foundation before initiating Architectural Decision Records (ADR).
Design and implement UI/UX changes using existing components and Tailwind tokens; ensure accessibility. EXCLUSIVE to ui-ux-designer agent.
Skill for creating C4 System Context Diagrams using Mermaid. Visualizes the system's boundaries, external actors (Users, External Systems), and high-level relationships.
Comprehensive draft story review with parallel specialist sub-agents. Spawns PM, UX, and SM agents to review stories from product, design, and implementation readiness perspectives before development begins.
Expert in making multi-agent systems resilient. Specializes in detecting loops, hallucinations, and failures, and implementing self-healing workflows. Use when designing error handling for agent systems, implementing retry strategies, or building resilient AI workflows.
Algorithmic decision tree for when to follow plan exactly vs when to report STOPPED - prevents scope creep and unauthorized deviations
Refine concept designs using six transformational moves. This skill should be used when improving existing concepts, addressing design trade-offs, or deciding between split/merge, unify/specialise, tighten/loosen approaches. Handles queries like "should I split this concept", "how to make concepts more flexible", "improve this concept design", "add more automation to concepts", "make concepts more general".
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, Bun, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.
Apply Elon Musk-inspired system design thinking for research, engineering, and business workflows: rigorously challenge requirements, delete steps, simplify/optimize what remains, accelerate iteration, then automate. Use when designing or revising systems, processes, or products that need lean, high-velocity execution.
Marp を使用してプレゼンテーション用スライドの Markdown ファイルを作成するスキル。ユーザーの要望に基づいて、Marp の機能（ディレクティブ、画像構文、フラグメントリスト、テーマ設定等）をフル活用した高品質なスライドを生成します。「スライドを作成して」「プレゼン資料を作って」「Marp でスライドを書いて」「発表資料を Markdown で作成して」等のリクエストで使用してください。
Professional design methodology for building modern, premium interfaces with client branding. Use for ALL client work and non-AICA projects. Applies glassforium logic, cinematic polish, and intentional design principles while adapting to client colors and brand identity. For Kelvin's personal AICA brand (black glass + gold), use the 'aica' skill instead.
Professional PlantUML theme collection with 5 curated color schemes optimized for software requirement analysis and enterprise architecture diagrams. Each theme provides comprehensive styling with colors, fonts, and visual identity suitable for different business contexts.
Create distinctive, production-grade frontend interfaces with high design quality AND comprehensive mobile responsiveness. Combines aesthetic guidelines with mobile-first patterns, form consistency, and color contrast rules. Use this as your single frontend design skill.
Atomic Design methodology for building component hierarchies in React. Trigger: When creating UI components, organizing component libraries, or structuring presentation layer.
Guides the planning of a microservices architecture. Use this skill when asked to design, plan, or architect a system using microservices. This skill helps with service boundary identification, communication pattern selection, data management, and defining service contracts.
Transform PRD or story into complete page/component designs with ASCII layouts, component specs, interaction flows, and frontend implementation prompts. Use this skill when: - User asks to "design the page", "design component", "create page design" - User mentions "page design", "component design", "UI design", "layout design" - Running /frontend.design command - PRD or story is ready and need visual/interaction design before implementation - Need to create design spec that frontend developer can implement from Prerequisites: Design system must exist at docs/reference/frontend/design-system.md Output: ALWAYS write design files to docs/reference/frontend/designs/{name}.md
Transform vague requirements into detailed specifications for HTML + Tailwind + vanilla JS web apps. Use when customers describe features vaguely, need project documentation, or want technical specifications without backend.
Question template for Insight stories ('I discovered X while doing Y'). Arc: Routine → Disruption → Recognition → Understanding → Application. Use with question-design skill.
Shared standards for decision checkpoints, manifest shape, revisioning, reproducibility, and privacy across the process mining skill suite.
