architecture-design
PRD・機能設計からアーキテクチャ設計書(docs/architecture.md)を作成する。「アーキテクチャ設計して」「技術選定して」「インフラ設計」「システム構成を決めて」「技術スタックを決めて」「非機能要件の設計」などの依頼時に使用。技術選定(理由付き)・レイヤー設計・データ戦略・セキュリティ・スケーラビリティを出力。
PRD・機能設計からアーキテクチャ設計書(docs/architecture.md)を作成する。「アーキテクチャ設計して」「技術選定して」「インフラ設計」「システム構成を決めて」「技術スタックを決めて」「非機能要件の設計」などの依頼時に使用。技術選定(理由付き)・レイヤー設計・データ戦略・セキュリティ・スケーラビリティを出力。
Frameworks and techniques for conducting effective interviews and transforming conversations into content. Use when interviewing for insights or converting interview material into articles/posts.
Linear、Notion、Stripe風の精密なデザインシステムを適用する。ダッシュボード、管理画面、SaaSインターフェースなどJony Ive級の精密さが必要なUI向け。「ダッシュボードを作って」「管理画面のUI」「UIデザイン原則を適用」「精密なデザイン」などの依頼時に使用。
Deeply interviews the user about a feature idea before implementation. Use this when the user says "interview me about [feature]", "I want to create a new feature", "let's create a new feature", "new feature", "plan a feature", or describes a feature they want to build. Asks probing, non-obvious questions about technical implementation, UI/UX decisions, edge cases, concerns, tradeoffs, and constraints. Continues interviewing until the feature is fully understood, then writes a detailed implementation plan.
データ分析とビジネスメトリクスの設計を支援します。KPI定義、データ収集戦略、ダッシュボード設計を提供します。分析基盤の設計、ビジネスメトリクスの測定体系構築が必要な場合に使用してください。
A rigorous Technical Architect and Systems Analyst responsible for producing implementation-ready specifications AND an execution-safe implementation plan. This skill defines immutable technical contracts (APIs, data models, states, migrations, constraints) and a structured step-by-step implementation roadmap while explicitly minimizing AI drift through locked requirements, guardrails, and verification checkpoints.
UX decision-making guidelines to avoid poor UI choices that don't match application aesthetics
Validation design rationale. Use when asking why validation works this way, understanding the layered validation strategy, or making architectural decisions about validation.
This skill should be used when the user asks about "festival operations", "event management", "vendor management", "lost and found procedures", "security protocols", "customer service at events", "handling difficult customers", "festival emergencies", "marketing communications", or discusses managing festivals, winter events, or public gatherings.
ウェブサイトのアナリティクス、トラフィックデータ、検索パフォーマンス、ユーザー行動について質問されたときに使用。仮説を立てて質問を行い、段階的にユーザーのニーズを明確化する。
Créer des interfaces frontend distinctives et production-grade avec une esthétique forte et non générique. Utiliser quand l'utilisateur demande de concevoir ou refondre une interface (composants web, pages, applications) avec un parti pris visuel marqué. Mettre l'accent sur un point de vue esthétique clair, des détails visuels soignés et un code prêt pour la production.
Guidelines for integrating additional RFP data sources beyond RFPMart
Analyzes business requirements and translates them into technical specifications
Help leaders prepare effective 1:1 meetings with their direct reports. Use this skill when asked to: prepare a 1:1 agenda, generate discussion topics, create talking points for a specific person or situation, follow up on previous 1:1s, prepare for difficult 1:1 conversations, or structure career development discussions. The skill provides templates, question banks, and frameworks for different 1:1 types (regular check-ins, career conversations, performance concerns, etc.).
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.
Comprehensive standards for creating and maintaining requirements and specification documents with SMART principles, proper structure, integrity, and traceability
Create production-grade frontend interfaces with systematic UI/UX design. Use when building web components, pages, or applications. Covers design systems, component states, accessibility (WCAG 2.2), responsive design, and industry conventions. Evaluates existing UI against best practices. Forces design thinking before implementation. Generates distinctive code avoiding generic AI aesthetics while following UX principles.
Creates contextual design briefs before any visual work begins. Establishes product purpose, user specificity, design principles, and anti-goals. Prevents generic "template" design by requiring specific context.
非エンジニアから要件をヒアリングするスキル。 「アプリを作りたい」「ツールが欲しい」などの発言時に使用。 What(何を作るか)とWhy(なぜ作るか)を明確にすることに集中する。
Validation loop for speccing. Clarifies requirements through structured questioning before document creation.
Selecciona una faceta de trabajo segun la peticion y registra la decision con fuentes.