features-page-generator

$npx mdskill add kostja94/marketing-skills/features-page-generator

Generate, optimize, or audit features page content for products.

  • Helps users create or improve features pages for their product.
  • Reads project context files for product and differentiation details.
  • Identifies feature set, audience, format, and primary goal.
  • Outputs structured page sections with best practices and CTAs.

SKILL.md

.github/skills/features-page-generatorView on GitHub ↗
---
name: features-page-generator
description: When the user wants to create, optimize, or audit features page content. Also use when the user mentions "features page," "product features," "capabilities," "what it does," "feature list," "feature comparison," "product capabilities," or "features section." For sitewide page planning, use website-structure.
metadata:
  version: 1.1.1
---

# 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 project context first:** If `.claude/project-context.md` or `.cursor/project-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 capability**: Group by product area or capability (e.g., Analytics, Automation, Integrations) — avoid organizing by use case to prevent overlap with use cases pages
- **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

### Avoid Overlap with Use Cases

- **Features = What**: Capability + benefit; no scenario narratives. Do not write "When you need to X..." — that belongs on use cases pages.
- **Link, don't duplicate**: Use "Use case links" (e.g., "For marketers," "For developers") to send users to use cases pages; do not replicate scenario content.
- **Content cannibalization**: Both target Commercial/Consideration; differentiate by angle (capability vs scenario) so each page serves unique intent.

## Output Format

- **Feature list** with benefit-first copy
- **Structure** (sections, order)
- **Headline** options
- **Per-feature** content (if separate pages)
- **SEO** metadata and schema

### vs. Tools

| Page | Purpose | Monetization |
|------|---------|--------------|
| **Features** | Paid product capabilities; conversion | Primary revenue |
| **Tools** | Free utilities; lead gen; excerpt from product | Not primary; drives signups |

See **tools-page-generator** for free tools pages.

## Related Skills

- **card**: Feature card structure; name, benefit, screenshot; grid/list layout
- **grid, list**: Feature grid or list layout
- **tools-page-generator**: Tools = free lead gen; features = paid capabilities; link from tools to product/features
- **use-cases-page-generator**: Features = what it does; use cases = when/how to use it; link between; avoid duplicating scenario content on features page
- **landing-page-generator**: Features content for product LP "Explain value" step; product LP links to features
- **url-slug-generator**: URL slug for per-feature pages (e.g. /features/feature-name); 3-5 words
- **homepage-generator**: Homepage links to features
- **pricing-page-generator**: Features inform plan tiers
- **schema-markup**: SoftwareApplication schema
- **heading-structure**: Feature page heading structure

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.