Agent skill · writing content · kostja94
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.
Why this skill is useful
Provides structured templates and best practices for creating audience-specific use case pages that enhance SEO and conversion strategies.
What it needs
About 3k tokens when loaded. Last updated 2026-06-09. 860 stars on the source repository.
What this skill does
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 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 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills kostja94/use-cases