003 Name Skill De640ff6

---
name: pages-features
description: 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."
metadata:
  version: 1.0.0
---

# 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:
1. **Feature set**: Core features, differentiators
2. **Audience**: Who evaluates features (buyer persona)
3. **Format**: Single page vs. per-feature pages
4. **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