features-page-generator
features-page-generator helps marketers and product teams create, optimize, or audit features pages that convert visitors into customers. It provides structure, copy guidance, and best practices for organizing features by priority or capability, writing benefit-first descriptions, and avoiding overlap with use cases pages. Use this skill when developing a features page from scratch, improving existing features content, or auditing page effectiveness against conversion goals.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/features-page-generator && cp -r /tmp/features-page-generator/skills/pages/content/features ~/.claude/skills/features-page-generatorSKILL.md
# 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
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When 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.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.