When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Guides use case pages that bridge product features and real-world customer problems. Scenario-first is the primary organization. BOFU (bottom-of-funnel) pages for SaaS/B2B. Answer "when would I use it?" and "how does it help me?" — distinct from solutions (industry/outcome).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, ICP, and proof points.
Identify:
| Section | Purpose |
|---|---|
| Headline | "When you need to X, we help you Y" or "For [role]: solve X" |
| Problem | Pain points, day-to-day challenges |
| Solution | How product addresses them; link to relevant features (do not duplicate feature copy) |
| Proof | Case study, testimonial, metrics |
| CTA | Try free, book demo, contact |
| Related | Link to other use cases, parent solution |
| Dimension | Priority | Examples |
|---|---|---|
| By Scenario | Primary | Event marketing, Lead nurturing, Churn prevention, Customer onboarding |
| By Persona/Role | Primary | For Realtors, For CMOs, For Sales Reps |
| By Business Goal | Secondary | Acquisition, Retention, Upsell/Cross-sell |
| By Industry | Secondary (ICP) | Use as ICP tag; or as sub-page under Solutions |
Event marketing, Lead nurturing, Churn prevention, Customer onboarding, Patient scheduling, Telemedicine, Inventory management, Demand forecasting.
Acquisition (signups, trials), Retention (reduce churn, re-engagement), Upsell/Cross-sell (expand revenue).
| Page | Answers | Primary Organization |
|---|---|---|
| Features | What does it do? | Capabilities |
| Solutions | What outcome do I get? | By industry, company size, team |
| Use cases | When would I use it? | By scenario, persona, business goal |
Hierarchy: Use cases can be standalone or sub-pages under Solutions. Example: /solutions/healthcare/patient-scheduling (use case under industry solution).
| Need | Use |
|---|---|
| By scenario (Event marketing) | Use Cases |
| By persona (For Realtors, For CMOs) | Use Cases |
| By business goal (Acquisition, Retention) | Use Cases |
| By industry | Solutions |
| By company size (SMB, Enterprise) | Solutions |
| By team (Marketing, Sales) | Solutions |
| Industry-specific application | Use Cases (as Solutions sub-page) |
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
日本語の概要は準備中です。原文の説明を表示しています。