features-page-generator
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.
Best use case
features-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using features-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/features/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How features-page-generator Compares
| Feature / Agent | features-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
serp-features
When the user wants to understand or optimize for SERP feature types (PAA, sitelinks, rich results, AI Overviews). Also use when the user mentions "SERP," "SERP features," "search result features," "People Also Ask," "PAA," "sitelinks," "knowledge panel," "local pack," "rich results," "zero-click," "SERP types," "AI Overviews," "Bing Copilot," or "Yandex AI." For JSON-LD and rich result implementation, use schema-markup. For organic strategy and roadmap, use seo-strategy.
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.