approval-gate
ワークフローの重要なフェーズ移行前にユーザーの明示的な承認を必要とする承認ゲートの共通フォーマットとパターンを定義
frontend-design
UI/UX design principles and patterns for building intuitive, accessible, and beautiful web interfaces
functional-design
プロダクト要求定義書（docs/product-requirements.md）から機能設計書（docs/functional-design.md）を作成する。 「機能設計して」「設計書を作って」「PRDを設計に落として」「コンポーネント設計」「データモデル設計」 「シーケンス図を書いて」「ER図を作って」などの依頼時に発火。 システム構成図・データモデル・コンポーネント責務・ユースケースフロー・エラー設計を出力。
concept-modeler
从模糊的用户需求中提取领域概念——实体、流程和"暗物质"（用户没说的）。基于 DDD（领域驱动设计）方法论。
accessibility-review
Audit for WCAG 2.1 AA compliance including keyboard navigation, ARIA usage, color contrast, and screen reader support. Use when building UI components, reviewing forms, or checking accessibility of new features.
senior-ui-designer
Expert UI/UX design guidance for professional SaaS interfaces. Covers interaction design, visual hierarchy, accessibility (WCAG 2.2 AA), color theory with OKLCH, micro-interactions, and design system coherence. Use when designing components, improving UX, or refining visual polish.
ui-design-system
UI design patterns, component design, interaction design, visual design system. Use when designing user interfaces, color systems, layout patterns, interaction behaviors, or translating features into visual components.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
product-manager
Expert Product Manager specializing in B2B SaaS platforms, multi-tenant systems, and subscription-based business models. Activated for product strategy, feature prioritization, requirements gathering, and stakeholder management.
feature-spec-writing
Creates focused feature specifications with user stories, acceptance criteria, and edge cases. Lighter than PRD, focuses on single feature implementation. Use when specifying individual features after PRD approval or for standalone feature work.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
plan-validation
Interactive plan validation loop for /resolve. Displays plan, offers modification/regeneration options, handles validation states.
spec-observation
仕様誤解を早期発見する観測。仕様の曖昧さ、仮定の明文化、受入条件のテスト化を行う。Use when: 新機能設計前、要件レビュー、仕様が曖昧、何を作るべきか不明、受入条件を決めたい、PRで仕様との乖離をチェックしたい時、生成コードの受入判断時。
analizador-traccion
Analiza métricas post-lanzamiento para determinar si un producto tiene tracción real o si debes pivotar. Interpreta señales de usuarios, retención, engagement y monetización. Úsalo después de lanzar para tomar decisiones basadas en datos sobre continuar, pivotar o cerrar.
product-strategy
Write product strategy documents for Viya TMS product teams. Uses Playing to Win framework, cascading from company strategy to team-level strategic choices.
requirements-analysis
Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.
brainstorming
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
user-stories
Break PRDs into user stories with acceptance criteria. Use when preparing work for development.
