solutions-page-generator

# Pages: Solutions Guides solutions pages focused on business outcomes. **Industry-first** is the B2B norm (Salesforce, HubSpot). Answer "what outcome do I get for my industry/team/size?" rather than "what does it do?" Distinct from features (capabilities) and use cases (scenarios); solutions emphasize measurable value by segment. **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, outcomes, and proof points. Identify: 1. **Outcomes**: Revenue growth, cost savings, efficiency, compliance 2. **Segments**: Industry (primary), company size, team 3. **Format**: Hub + per-solution pages, or single solutions page 4. **Primary goal**: Demo, sign up, contact ## Solutions Page Structure | Section | Purpose | |---------|---------| | **Headline** | Outcome-led; "Achieve X with [Product]" | | **Challenge** | Business problem, context | | **Solution** | How product delivers the outcome | | **Proof** | Metrics, case study, ROI | | **Features used** | Link to relevant features | | **CTA** | Book demo, start trial, see case study | | **Related** | Other solutions, use cases (as sub-applications) | ## Best Practices ### Outcome-First - **Lead with result*...