Back to Details

features-page-generator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
指导功能页的内容、结构设计以及转化优化。
调用说明：首次使用时，如果合适，可以先用1-2句话介绍本技能的覆盖范围和价值，再提供核心输出。后续使用或用户要求跳过介绍时，直接输出核心内容即可。

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
优先核对产品营销上下文：如果存在
.claude/product-marketing-context.md
或
.cursor/product-marketing-context.md
文件，先读取文件获取产品信息、差异化优势和佐证数据。
明确以下信息：
  1. 功能集合：核心功能、差异化优势
  2. 目标受众：评估功能的人群（购买者画像）
  3. 呈现形式：单页汇总 vs 拆分多个单功能详情页
  4. 核心目标：申请演示、注册、了解更多

Features Page Structure

功能页结构

SectionPurpose
HeadlineBenefit-led; "Everything you need to..."
Feature grid/listEach feature: name, benefit, optional screenshot
Use case links"For marketers," "For developers"
Social proofTestimonials, logos
CTATry free, see demo, contact
模块作用
大标题以价值为导向，比如「你所需的一切都在这里...」
功能网格/列表每个功能包含：名称、价值、可选截图
用例跳转链接比如「面向营销人员」、「面向开发者」
社交证明用户评价、客户品牌logo
CTA按钮免费试用、查看演示、联系我们

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
  • 把价值放在最前面：比如写「每周节省10小时」而不是「自动化报表」
  • 关注客户结果：突出用户能获得什么，而不是产品能做什么
  • 内容具体：用数字、案例，避免模糊的表述

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

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
  • 页面标题：「功能 | [产品名]」或者「[功能名] | [产品名]」
  • 标题层级：H1展示核心价值；每个功能或模块用H2标题
  • Schema：适用的话添加SoftwareApplication标记
  • 内部链接：链向定价页、用例页、博客

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.
  • 功能页 = 是什么：能力+价值，不要出现场景叙事，不要写「当你需要做X的时候...」，这类内容属于用例页
  • 跳转而非重复：通过「用例跳转链接」（比如「面向营销人员」、「面向开发者」）引导用户到用例页，不要复制场景内容
  • 避免内容互搏：两类页面都面向商业/决策阶段用户，要通过角度区分（能力vs场景），让每个页面匹配不同的用户意图

Output Format

输出格式

  • Feature list with benefit-first copy
  • Structure (sections, order)
  • Headline options
  • Per-feature content (if separate pages)
  • SEO metadata and schema
  • 价值优先的功能列表文案
  • 结构设计（模块、排序）
  • 大标题备选方案
  • 单功能页内容（如果需要拆分页面）
  • SEO元数据和Schema标记

vs. Tools

功能页 vs 工具页

PagePurposeMonetization
FeaturesPaid product capabilities; conversionPrimary revenue
ToolsFree utilities; lead gen; excerpt from productNot primary; drives signups
See tools-page-generator for free tools pages.
页面作用monetization 定位
功能页付费产品能力，促进转化核心收入相关
工具页免费工具，获客，是产品功能的子集非核心收入，驱动注册
免费工具页相关内容参考 tools-page-generator。

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
  • card：功能卡片结构（名称、价值、截图）、网格/列表布局
  • grid, list：功能网格或列表布局
  • tools-page-generator：工具页=免费获客载体；功能页=付费能力展示；从工具页添加跳转链接到产品/功能页
  • use-cases-page-generator：功能页=产品能做什么；用例页=什么时候/怎么用产品；页面间互相跳转；不要在功能页重复场景内容
  • landing-page-generator：产品落地页「价值说明」模块的功能内容；产品落地页添加跳转链接到功能页
  • url-slug-generator：单功能页的URL slug（比如/features/feature-name），长度3-5个单词
  • homepage-generator：首页添加跳转链接到功能页
  • pricing-page-generator：功能是套餐分级的依据
  • schema-markup：SoftwareApplication Schema标记
  • heading-structure：功能页标题结构设计