跳到正文
cccskills
免费在 GitHub 公开

use-cases-page-generator

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.

中文简介正在准备中。当前显示原文说明。

dalroot/agentic-seo星标 25(GitHub 25 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md5.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Pages: Use Cases

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.

Initial Assessment

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:

  1. Scenarios: Concrete situations (event marketing, lead nurturing)
  2. Personas: Roles (Marketer, Sales Rep, Realtor)
  3. Business goals: Acquisition, Retention, Upsell
  4. Format: Single page vs. per-use-case pages; standalone or under solutions
  5. Primary goal: Demo, sign up, contact sales

Use Case Page Structure

SectionPurpose
Headline"When you need to X, we help you Y" or "For [role]: solve X"
ProblemPain points, day-to-day challenges
SolutionHow product addresses them; link to relevant features (do not duplicate feature copy)
ProofCase study, testimonial, metrics
CTATry free, book demo, contact
RelatedLink to other use cases, parent solution

Best Practices

Scenario-First

  • Concrete situations: "When you need to run event marketing at scale..."
  • Before-after: Show transformation, not just features
  • One scenario per page: Don't mix "event marketing" and "lead nurturing"

Content Differentiation (vs Features)

  • Use case = scenario + problem + outcome: Write the story (when, who, why, result); reference features via links.
  • Do not duplicate feature copy: Avoid repeating capability lists or benefit bullets from the features page; instead, describe how the product solves this scenario and link to /features for details.
  • Avoid content cannibalization: Each use case page targets a unique scenario intent; overlap with features (both Commercial/Consideration) dilutes SEO — differentiate by content angle (scenario vs capability).

Organization (Primary → Secondary)

DimensionPriorityExamples
By ScenarioPrimaryEvent marketing, Lead nurturing, Churn prevention, Customer onboarding
By Persona/RolePrimaryFor Realtors, For CMOs, For Sales Reps
By Business GoalSecondaryAcquisition, Retention, Upsell/Cross-sell
By IndustrySecondary (ICP)Use as ICP tag; or as sub-page under Solutions

Scenario Examples

Event marketing, Lead nurturing, Churn prevention, Customer onboarding, Patient scheduling, Telemedicine, Inventory management, Demand forecasting.

Business Goal Examples

Acquisition (signups, trials), Retention (reduce churn, re-engagement), Upsell/Cross-sell (expand revenue).

vs. Solutions vs. Features

PageAnswersPrimary Organization
FeaturesWhat does it do?Capabilities
SolutionsWhat outcome do I get?By industry, company size, team
Use casesWhen 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).

When to Use Use Cases vs Solutions

NeedUse
By scenario (Event marketing)Use Cases
By persona (For Realtors, For CMOs)Use Cases
By business goal (Acquisition, Retention)Use Cases
By industrySolutions
By company size (SMB, Enterprise)Solutions
By team (Marketing, Sales)Solutions
Industry-specific applicationUse Cases (as Solutions sub-page)

Internal Linking

  • Use cases ↔ features ↔ solutions ↔ customer stories
  • If under a solution: link to parent solution; parent links to use cases

SEO

  • Intent: Commercial; "X software for [scenario]" or "[Product] for [role]"
  • Title: "When to Use [Product] for [Scenario]" or "[Product] for [Role]"
  • Differentiate: Unique workflows, pain points per scenario/persona

Output Format

  • Use case list (scenarios/personas to cover)
  • Per-page structure (sections, messaging)
  • Headline options per segment
  • Internal linking plan (including parent solution if applicable)
  • SEO metadata

Related Skills

  • features-page-generator: Features = what it does; use cases = when/how to use it; reference features via links, don't duplicate; see Content Differentiation above
  • solutions-page-generator: Solutions are industry/outcome-focused; use cases are scenario-focused; use cases can be sub-pages under solutions
  • customer-stories-page-generator: Case studies as proof on use case pages
  • landing-page-generator: Use case pages are a type of landing page; apply LP principles
  • pricing-page-generator: Use case pages link to pricing

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。

dalroot/agentic-seo252026年10月27日 更新

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.

中文简介正在准备中。当前显示原文说明。

dalroot/agentic-seo252026年10月27日 更新

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.

中文简介正在准备中。当前显示原文说明。

dalroot/agentic-seo252026年10月27日 更新

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.

中文简介正在准备中。当前显示原文说明。

dalroot/agentic-seo252026年10月27日 更新

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.

中文简介正在准备中。当前显示原文说明。

dalroot/agentic-seo252026年10月27日 更新

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.

中文简介正在准备中。当前显示原文说明。

dalroot/agentic-seo252026年10月27日 更新

查看 dalroot 的全部技能

报告此技能的问题