Use Cases Page Generator
Structure and write BOFU use-case pages that map personas and scenarios to product value for solo SaaS founders shipping marketing sites.
Overview
use-cases-page-generator is an agent skill most often used in Launch (also Grow/content, Validate/landing) that designs scenario-first BOFU use case pages for SaaS and B2B sites.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill use-cases-page-generatorWhat is this skill?
- Scenario-first page architecture with headline, problem, workflow, proof, and CTA sections
- Initial assessment for personas, business goals, single vs per-use-case URL strategy
- Reads `.claude/project-context.md` or `.cursor/project-context.md` when present for ICP and proof
- Explicit BOFU focus for SaaS/B2B—distinct from industry/outcome solutions pages
- Hands off to website-structure for sitewide planning when scope is broader than use cases
- 7-section use case page structure table (headline through CTA-oriented sections in SKILL.md)
Adoption & trust: 744 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have features and ICP notes but no clear, searchable pages that show real situations where your product wins.
Who is it for?
Solo founders publishing or refreshing marketing sites who need persona- and scenario-specific conversion pages with a consistent BOFU structure.
Skip if: Teams that only need a full sitemap or nav hierarchy without use-case copy—use website-structure instead, or builders with no defined scenarios or proof points yet.
When should I use this skill?
When the user wants to create, optimize, or audit use case pages, or mentions use cases, use case page, for [role], by persona, by scenario, by business goal, ICP pages, or audience-specific pages.
What do I get? / Deliverables
You get a concrete use-case page blueprint—sections, headlines, and scenario/persona mapping—ready to draft or ship on your marketing site.
- Use-case page outline with section purposes filled
- Format decision (single vs per-use-case pages)
- Primary conversion goal (demo, sign up, contact sales)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Use-case pages are primary go-to-market assets that turn positioning into conversion paths when you launch or expand distribution. Distribution covers persona- and scenario-specific landing surfaces that drive demo, signup, or contact-sales goals.
Where it fits
Draft a landing-style use case page to test one ICP before full site build.
Ship per-role URLs (e.g. for realtors) tied to demo or signup as primary CTA.
Expand a single high-intent scenario into a full BOFU page with proof and workflow sections.
Translate early persona hypotheses into page scenarios before committing to positioning.
How it compares
Use for job-to-be-done landing pages; use solutions-style pages when the story is industry or outcome, not a specific scenario.
Common Questions / FAQ
Who is use-cases-page-generator for?
Solo and indie SaaS or B2B builders who want agent-guided structure for use case, persona, or ICP-specific marketing pages—not generic feature blurbs.
When should I use use-cases-page-generator?
When you mention use cases, use case pages, for [role], by persona, by scenario, by business goal, ICP pages, or audience-specific pages; also during launch distribution planning, validate landing drafts, or grow content that ties stories to signup or demo CTAs.
Is use-cases-page-generator safe to install?
Review the Security Audits panel on this Prism page and the kostja94/marketing-skills source before enabling the skill in your agent; it is prose guidance without bundled scripts in this excerpt.
SKILL.md
READMESKILL.md - Use Cases Page Generator
# 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. - **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) | 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 | ### 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 | 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). ### When to Use Use Cases vs Solutions | Need | U