Pages: Features
Guides features page content, structure, and conversion optimization.
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 product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-context.md exists, read it for product, differentiation, and proof points.
Identify:
- Feature set: Core features, differentiators
- Audience: Who evaluates features (buyer persona)
- Format: Single page vs. per-feature pages
- Primary goal: Demo, sign up, learn more
Features Page Structure
| Section |
Purpose |
| Headline |
Benefit-led; "Everything you need to..." |
| Feature grid/list |
Each feature: name, benefit, optional screenshot |
| Use case links |
"For marketers," "For developers" |
| Social proof |
Testimonials, logos |
| CTA |
Try free, see demo, contact |
Best Practices
Benefit-First
- Lead with benefit: "Save 10 hours/week" not "Automated reporting"
- Customer outcome: What they get, not what it does
- Specificity: Numbers, examples, not vague claims
Organization
- By use case: Group by job-to-be-done
- By priority: Most important/differentiating first
- By journey: Discovery -> evaluation -> decision
Per-Feature Pages
- Use when features are substantial or rank separately
- Each page: feature name, benefit, how it works, proof
- Internal link from main features page
SEO
- Title: "Features | [Product]" or "[Feature] | [Product]"
- H1: Main value; H2 per feature or section
- Schema: SoftwareApplication if applicable
- Internal links: To pricing, use cases, blog
Output Format
- Feature list with benefit-first copy
- Structure (sections, order)
- Headline options
- Per-feature content (if separate pages)
- SEO metadata and schema
Related Skills
- components-url-slug: URL slug for per-feature pages (e.g. /features/feature-name); 3-5 words
- pages-home: Homepage links to features
- pages-pricing: Features inform plan tiers
- seo-on-page-schema: SoftwareApplication schema
- seo-on-page-heading: Feature page heading structure
1---2name: pages-features3description: When the user wants to create, optimize, or audit features page content. Also use when the user mentions "features page," "product features," "capabilities," or "what it does."4---56# Pages: Features78Guides features page content, structure, and conversion optimization.910**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.1112## Initial Assessment1314**Check for product marketing context first:** If `.claude/product-marketing-context.md` or `.cursor/product-marketing-context.md` exists, read it for product, differentiation, and proof points.1516Identify:171. **Feature set**: Core features, differentiators182. **Audience**: Who evaluates features (buyer persona)193. **Format**: Single page vs. per-feature pages204. **Primary goal**: Demo, sign up, learn more2122## Features Page Structure2324| Section | Purpose |25|---------|---------|26| **Headline** | Benefit-led; "Everything you need to..." |27| **Feature grid/list** | Each feature: name, benefit, optional screenshot |28| **Use case links** | "For marketers," "For developers" |29| **Social proof** | Testimonials, logos |30| **CTA** | Try free, see demo, contact |3132## Best Practices3334### Benefit-First3536- **Lead with benefit**: "Save 10 hours/week" not "Automated reporting"37- **Customer outcome**: What they get, not what it does38- **Specificity**: Numbers, examples, not vague claims3940### Organization4142- **By use case**: Group by job-to-be-done43- **By priority**: Most important/differentiating first44- **By journey**: Discovery -> evaluation -> decision4546### Per-Feature Pages4748- Use when features are substantial or rank separately49- Each page: feature name, benefit, how it works, proof50- Internal link from main features page5152## SEO5354- Title: "Features | [Product]" or "[Feature] | [Product]"55- H1: Main value; H2 per feature or section56- Schema: SoftwareApplication if applicable57- Internal links: To pricing, use cases, blog5859## Output Format6061- **Feature list** with benefit-first copy62- **Structure** (sections, order)63- **Headline** options64- **Per-feature** content (if separate pages)65- **SEO** metadata and schema6667## Related Skills6869- **components-url-slug**: URL slug for per-feature pages (e.g. /features/feature-name); 3-5 words70- **pages-home**: Homepage links to features71- **pages-pricing**: Features inform plan tiers72- **seo-on-page-schema**: SoftwareApplication schema73- **seo-on-page-heading**: Feature page heading structure
tools-only