landing-page

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Landing Page Assistant

着陆页助手

Check for product marketing context first: If
.agents/product-marketing.md
exists (or
.agents/product-marketing-context.md
or
.claude/product-marketing-context.md
in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Generate structured, conversion-focused landing page copy using the modular section framework.
首先检查产品营销背景信息: 如果存在
.agents/product-marketing.md
(旧版配置中为
.agents/product-marketing-context.md
.claude/product-marketing-context.md
),请先阅读该文件再提问。利用其中的背景信息,仅询问未涵盖或与本次任务相关的特定信息。
使用模块化板块框架生成结构化、以转化为目标的着陆页文案。

When to Use

使用场景

  • User wants to create a new landing page or homepage
  • User needs copy for specific landing page sections
  • User mentions "landing page template," "homepage copy," or "page sections"
  • 用户需要创建新的着陆页或首页
  • 用户需要特定着陆页板块的文案
  • 用户提及「着陆页模板」「首页文案」或「页面板块」

Instructions

操作步骤

  1. Confirm page type: Homepage, feature page, or campaign landing page
  2. Gather inputs: Product name, value proposition, target audience, key features, social proof
  3. Generate section-by-section copy following the template structure
  4. Include visual/CTA notes for each section
  1. 确认页面类型:首页、功能页或营销活动着陆页
  2. 收集输入信息:产品名称、价值主张、目标受众、核心功能、社交证明
  3. 按模板结构生成逐板块文案
  4. 为每个板块添加视觉/CTA说明

Section Structure

板块结构

Generate copy for each section in order:
按顺序为每个板块生成文案:

Hero Section

英雄板块

  • Headline: Action statement explaining unique value proposition
  • Subheadline: 1-2 sentences explaining product and how it creates value
  • Bullet Points: 2 specific claims, 2 objection handles, 3 social proof points
  • Social Proof: Testimonials, logos, ratings, stats
  • Hero CTA: Action-focused, value-focused, or objection-handling
  • 标题:阐述独特价值主张的行动式语句
  • 副标题:1-2句话说明产品及其创造价值的方式
  • 要点列表:2个具体主张、2个异议处理点、3个社交证明点
  • 社交证明:客户证言、品牌logo、评分、数据统计
  • Hero CTA:以行动为导向、以价值为导向或处理异议类型

Problem to Solution Comparison

问题与解决方案对比

  • Before vs After: Pain points vs solution benefits
  • Old Way vs New Way: Limitations vs capabilities
  • CTA: Reinforce action
  • 前后对比:痛点 vs 解决方案优势
  • 新旧方式对比:局限性 vs 能力
  • CTA:强化行动指令

Features, Capabilities & Benefits

功能、能力与优势

For each feature (3-6 features):
  • Heading: Feature name
  • Description: Capability + Benefit
  • Visual note: Image suggestion
  • CTA: Feature-specific action
针对每个功能(3-6个):
  • 标题:功能名称
  • 描述:能力 + 优势
  • 视觉说明:图片建议
  • CTA:功能专属行动指令

Integrations

集成功能

For each integration (2-4):
  • Heading: Integration name
  • Description: Capability + Benefit
  • Visual: Logo placement
针对每个集成(2-4个):
  • 标题:集成名称
  • 描述:能力 + 优势
  • 视觉:Logo放置建议

How It Works

操作流程

For each step (3-5 steps):
  • Heading: Step title
  • Description: What user does/gets
  • Visual note: Screenshot suggestion
针对每个步骤(3-5个):
  • 标题:步骤名称
  • 描述:用户操作/获得的内容
  • 视觉说明:截图建议

FAQs

常见问题

  • Feature FAQs: 2-3 questions about features
  • Objection FAQs: 2-3 questions addressing concerns
  • 功能类问题:2-3个关于功能的问题
  • 异议类问题:2-3个解决顾虑的问题

Second CTA Section

第二CTA板块

  • Heading: Switch/upgrade focused
  • Description: Value outcome statement
  • Bullet Points: Objection handles + ease of start
  • CTA: Clear next action
  • 标题:聚焦切换/升级
  • 描述:价值成果说明
  • 要点列表:异议处理 + 入门便捷性
  • CTA:清晰的下一步行动

Founder's Note (Optional)

创始人寄语(可选)

  • Put yourself in their shoes
  • Explain their problem
  • Take ownership
  • Show the happy ending
  • 换位思考用户痛点
  • 阐述用户面临的问题
  • 承担责任
  • 展示理想结果

Output Format

输出格式

markdown
undefined
markdown
undefined

[Section Name]

[板块名称]

Headline: [Copy]
Subheadline: [Copy]
Bullet Points:
  • [Point 1]
  • [Point 2]
CTA: [Button text]
Visual Note: [Suggestion]
undefined
Headline: [文案内容]
Subheadline: [文案内容]
Bullet Points:
  • [要点1]
  • [要点2]
CTA: [按钮文本]
Visual Note: [建议内容]
undefined

Constraints

约束条件

  • Each section must have Headline, Description, and CTA (where applicable)
  • Use bullet points for feature/benefit lists
  • Bold key phrases and product names
  • No generic filler text
  • Use placeholders [Product Name] if info missing
  • Hyphen rules: Hyphens connect words (well-being); en dashes for ranges (June-August); em dashes for breaks in thought
  • 每个板块必须包含标题、描述和CTA(适用时)
  • 功能/优势列表使用要点格式
  • 关键短语和产品名称加粗
  • 无通用填充文本
  • 若信息缺失,使用占位符[Product Name]
  • 连字符规则:短横线连接单词(如well-being);短破折号表示范围(如June-August);长破折号表示思路中断

Reference

参考资料

See
references/landing-page-framework.md
for complete section templates and examples.
查看
references/landing-page-framework.md
获取完整板块模板及示例。