form-cro
当用户想要优化任何非注册/登记类的表单时使用——包括潜在客户获取表单、联系表单、演示请求表单、申请表、调查表单或结账表单。当用户提到“表单优化”“潜在客户表单转化”“表单摩擦”“表单字段”“表单完成率”或“联系表单”时也使用。注册/登记表单请参见 signup-flow-cro。包含表单的弹窗请参见 popup-cro。
机器翻译查看英文原文
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
适用对象：营销与增长。自动收录 · 待核查。
原作者说明节选
从固定版本的 SKILL.md 提取，保留原文语言。以下内容属于作者说明，本站尚未验证安装、兼容或运行结果。
查看英文原文
原文涵盖的主题
- Form CRO
- Initial Assessment
- Core Principles
- 1. Every Field Has a Cost
- 2. Value Must Exceed Effort
- 3. Reduce Cognitive Load
- Field-by-Field Optimization
- Email Field
You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters. Before providing recommendations, identify: 1. Form Type Lead capture (gated content, newsletter) Contact form Demo/sales request Application form Survey/feedback Checkout form Quote request 2. Current State How many fields? What's the current completion rate? Mobile vs. desktop split? Where do users abandon? 3. Business Context What happens with form submissions? Which fields are actually used in follow-up? Are there compliance/legal requirements? -- Each field reduces completion rate. Rule of thumb: 3 fields: Baseline 4-6 fields: 10-25% reduction 7+ fields: 25-50%+ reduction For each field, ask: Is this absolutely necessary before we can help them? Can we get this information another way? Can we ask this later? Clear value proposition above form Make what they get obvious Reduce perceived effort (field count, labels) One question per field Clear, conversational labels Logical grouping and order Smart defaults where possible -- Single field, no confirmation Inline validation Typo detection (did you mean gmail.com?) Proper mobile keyboard Single "Name" vs. F
这里只展示节选，请以完整原文和当前要求为准。
- 来源仓库
- davila7/claude-code-templates
- 源文件
- cli-tool/components/skills/business-marketing/form-cro/SKILL.md
- 固定版本
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
来源与内容状态
本条为自动发现的元数据，尚未完成人工文档核查；适用性与运行结果待核查。
原作者：davila7/claude-code-templates · 原作者仓库元数据。文档核查：未核查。最近来源检查：2026-11-09T14:01:43.556Z。
分类由名称、说明与路径规则生成，分类不代表已核实适配。
许可与权利归属
MIT。第三方内容及版权归原作者，使用条件以原文为准。
许可原文 ↗本站没有因同步、复制或用户自报成功而将资源标为运行验证通过。
限制与注意事项
- 元数据收录不代表本站已经安装、适配、实测或进行安全审查。