Writes a Kyora BRD (Business Requirements Document) from stakeholder requirements, optimized for Kyora’s mobile-first, Arabic/RTL-first DM-commerce customers. Use when you want a ready-to-build spec stored under /brds with a clear status workflow.
Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
WCAG 2.1 AA accessibility audit. Use to ensure the application is accessible to all users.
Эксперт по B2B SaaS маркетингу. Используй для стратегий генерации спроса, growth-маркетинга, PLG, расчёта CAC/LTV, оптимизации воронки и маркетинговых операций.
Provides REQ-* key pattern definitions, validation rules, and traceability operations. Use for understanding requirement key formats, validating keys, or tracing requirements through the SDLC lifecycle.
Design System & UI Kit Development with Figma 2025, Design Tokens, and Component Documentation
Write high-quality technical specifications that enable clear communication, reduce ambiguity, and drive successful implementation. Use when planning new features, designing APIs, documenting system architecture decisions, creating technical requirements, writing acceptance criteria, preparing RFCs, defining data models, or specifying integration requirements. Triggers include "write spec", "technical specification", "feature spec", "API spec", "requirements document", "RFC", or when creating documentation that defines what to build.
Use when creating, editing, or reviewing skills. Covers discovery optimization, structure patterns, testing approaches, and format decisions.
Cognitive psychology principles for UX design decisions. Use when planning features, structuring interfaces, reducing complexity, or optimizing user journeys. Covers choice architecture, cognitive load, attention, and experience design. (project)
画面遷移図(画面フロー図 / Screen flow / UI flow / Wireflow)を、要件・ユーザーストーリー・既存ルート・Figma構成・文章仕様から再現可能に作成/更新する。出力はMermaidのflowchartを基本とし、画面カタログ(画面ID/名称/状態/権限)と遷移カタログ(トリガー/条件/結果/例外)も併記する。例外系(失敗・戻り・未ログイン・権限不足・空状態)を必ず含め、スパゲッティ化する場合はユースケース単位で図を分割(L0/L1/L2)する。トリガー語: 画面遷移図, 画面フロー, UIフロー, screen flow, wireflow, 遷移図, フロー図, 画面一覧, 画面設計, 導線
Guidelines for maintaining visual consistency with The Economist's design language
CRO Specialist Agent. 전환율 최적화, A/B 테스트, 랜딩 최적화를 담당합니다.
**REQUIREMENTS ANALYZER** - '이런 거 만들고 싶어', '기능 정리', '뭐부터 만들어야', 'MVP 정의', '요구사항 분석', '기획서 분석' 요청 시 자동 발동. 자연어 아이디어를 기술 명세로 변환. MVP 분리, 우선순위 매트릭스, 의존성 그래프 제공.
Web/モバイルアプリのアイデアを共創型インタビューで具体化し、開発用ドキュメント一式を生成するスキル。「アプリのアイデアがある」「新しいサービスを考えたい」「仕様を固めたい」「アプリ開発の相談」と言った時に使用する。アイデア段階から開発着手可能なドキュメントまで一貫してサポート。
Complete Brand World Design methodology for developing comprehensive brand strategy. Use when users need brand positioning, purpose discovery, audience definition, creative strategy, or want to create a Brand World Document. Includes FOR/ONLY/BECAUSE framework, PITS (Problem-Insight-Truth-Solution), and Seven Chambers journey structure.
Design System & UI Kit Development with Figma 2025, Design Tokens, and Component Documentation
Guide for spec-based agent-driven development using structured requirements (EARS notation), technical design documentation, and implementation planning. Use when users want to build features using a specification-first approach, need to document requirements formally, want to generate implementation plans from specs, or when working on projects that benefit from clear requirement-to-code traceability.
產品經理/產品規劃工作流與產出模板（PRD）。用於把一句話需求或商業問題，系統化收斂成：問題定義、目標與指標、使用者與情境、範圍（in/out）、解法方案比較、MVP/迭代拆解、需求明細與驗收標準、埋點/實驗設計、上線/回滾計畫、風險與依賴。適用於 0→1 新功能規劃、成長/轉換漏斗優化、需求評審與對齊、跨團隊交付前的 PRD 寫作與補完。
太陽スタイル完全準拠のブレット（箇条書き）・ベネフィットリスト生成。特徴→ベネフィット変換で購買意欲を最大化。
