presentation-creator
Marpを使用した提案資料・比較検討資料の作成スキル。課題提示、複数案の比較検討、メリット・デメリット整理を含む資料を作成する。使用場面:(1) 技術選定や方式比較の検討資料、(2) 提案書・企画書、(3) 問題解決策の提示、(4) 意思決定を支援するドキュメント。作成完了後は必ずサブエージェントでレビューを実施する。
Marpを使用した提案資料・比較検討資料の作成スキル。課題提示、複数案の比較検討、メリット・デメリット整理を含む資料を作成する。使用場面:(1) 技術選定や方式比較の検討資料、(2) 提案書・企画書、(3) 問題解決策の提示、(4) 意思決定を支援するドキュメント。作成完了後は必ずサブエージェントでレビューを実施する。
Use when designing animations for travel booking, hospitality apps, tourism platforms, or vacation planning experiences
Use when receiving feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
新しい要件に対して最適なアーキテクチャを提案するスキル。 既存構成を解析し、課題・選択肢比較・残課題を含む意思決定ドキュメントを生成。 新機能追加、パフォーマンス改善、セキュリティ強化時に使用。
Skill/MCPの使い分けと組み合わせ設計を支援するガイド。外部ツール接続はMCP、手順・品質基準はSkillという分離原則、衝突回避、実例(財務バリュエーション/ミーティング準備)を参照し、どちらを使うか判断・設計したいときに使う。
Review Phase 1 ASCII UI designs from a product owner perspective. Analyze user journeys, identify potential issues, ask clarifying questions about requirements and user flows, create Mermaid diagrams (flowcharts, sequence diagrams, state charts), provide detailed system behavior documentation, and document error handling strategies. Use when reviewing ASCII mockups to validate design against actual user needs, understand system workflows, and ensure completeness before moving to implementation.
Use when composing scenes, designing layouts, directing user attention, or ensuring a single clear idea is communicated at any given moment.
ユーザーが「記憶して」「思い出して」などのメモリ操作を指示した時に使用。重要な調査結果、アーキテクチャの決定、問題の解決策を発見した時にも積極的に保存を提案する。
Plan and execute Substack growth strategy for subscriber acquisition and retention. Use when developing Notes strategy, setting up recommendations, planning cross-platform promotion, optimizing for discovery, converting free to paid, reducing churn, or building long-term newsletter growth. Includes the 20-minute daily routine, leaderboard optimization, and the recommendation network strategy.
User-centered documentation quality framework. Eight quality dimensions, document type requirements, and review checklist. Documentation exists to serve readers, not demonstrate knowledge.
Designs engagement strategies to increase learner motivation, interaction, and persistence.
Clarify requirements before implementing changes or plans when a request is underspecified. Use when objectives, scope, constraints, acceptance criteria, or environment details are unclear and you need the minimum set of questions before proceeding.
Enhances the visual design and animations (UI/UX Persona).
Systematic design optimization for young-personal-site following established design principles. Ensures consistent color palette, responsive layout, and professional appearance.
Comprehensive guide to designing and writing effective user onboarding experiences that drive activation and retention
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
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 guide to enterprise vendor onboarding processes, timelines, requirements, and strategies for accelerating customer acquisition
Orchestrates EUFM monetization: pricing strategy, funnel optimization, revenue projections, and marketing execution. Targets €50K bootstrap in 30 days and €4.5M-12M ARR within 12 months by testing pricing models, tracking customer acquisition metrics, and aligning constitutional guardrails with data-driven growth tactics.
Formulates a comprehensive strategy for creating specifications. Analyzes requirements (ADR/Issue), defines shared definitions, drafts specific issues, and reviews the plan for quality assurance.
Interviews users to clarify their thinking instead of writing for them. Use when asked to help with writing, content ideas, exploring topics, or reviewing drafts. Reads existing notes to identify themes, asks probing questions one at a time, pushes back on vague thinking, and tracks discussions from exploration to publication.
Draft detailed engineering specs from an approved PRD. Use when generating or updating the engineering specification for a feature, before implementation begins.