Pages: Contact
Guides contact page design and form optimization for conversions.
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 brand voice.
Identify:
- 1. Contact types: Sales, support, general, press
- Form purpose: Lead capture, support ticket, demo request
- Alternative channels: Email, phone, chat, social
Best Practices
Form Design
| Principle | Guideline |
|---|
| Short | 3-5 fields for basic contact; long forms increase abandonment |
| Single column |
Vertical layout; works better on mobile |
|
Logical grouping | Name+email together; address fields together |
|
Required fields | Mark clearly (asterisk); avoid surprises |
|
Progressive disclosure | Show relevant fields based on selections |
Field Labels
- - Clear language: "Email Address" not "Email ID"
- Conversational: Friendly, welcoming
- No jargon: Universally understood terms
CTA Button
- - Action verbs: "Send Message," "Get in Touch," "Start a Conversation"
- Avoid generic: "Submit" ? "Send Message"
- Stand out: Contrasting color, clear hierarchy
Page-Level
| Element | Guideline |
|---|
| Visibility | "Contact" or "Support" in main nav, not just footer |
| Mobile |
Appropriate input types (tel for phone), large tap targets |
|
Proofreading | No typos--credibility at conversion moment |
|
Alternatives | Email, phone, chat if form isn't right |
Trust
- - Response time: "We reply within 24 hours"
- Privacy: Link to privacy policy near form
- Security: HTTPS, visible trust signals
Output Format
- - Form structure (fields, order)
- Copy (labels, placeholder, CTA)
- Page layout and placement
- SEO metadata
- Accessibility checklist
Related Skills
- - landing-page-generator: Lead capture LP contains contact form; demo request CTA destination
- about-page-generator: Contact often linked from About
- legal-page-generator: Privacy policy link near form
- title-tag, meta-description, page-metadata: Contact page metadata
页面:联系页面
指导联系页面设计和表单优化以提高转化率。
调用时:在首次使用时,如有帮助,可用1-2句话介绍此技能涵盖的内容及其重要性,然后提供主要输出。在后续使用或用户要求跳过时,直接进入主要输出。
初始评估
首先检查项目上下文: 如果存在 .claude/project-context.md 或 .cursor/project-context.md,请读取以了解品牌语调。
识别:
- 1. 联系类型:销售、支持、一般咨询、媒体
- 表单目的:线索捕获、支持工单、演示请求
- 替代渠道:电子邮件、电话、在线聊天、社交媒体
最佳实践
表单设计
| 原则 | 指南 |
|---|
| 简洁 | 基本联系表单3-5个字段;长表单会增加放弃率 |
| 单列 |
垂直布局;在移动设备上效果更佳 |
|
逻辑分组 | 姓名+邮箱放在一起;地址字段放在一起 |
|
必填字段 | 清晰标记(星号);避免意外 |
|
渐进式展示 | 根据选择显示相关字段 |
字段标签
- - 清晰语言:使用电子邮件地址而非邮箱ID
- 对话式:友好、热情
- 无术语:使用普遍理解的词汇
行动号召按钮
- - 行动动词:发送消息、联系我们、开始对话
- 避免通用:提交 → 发送消息
- 突出显示:对比色、清晰的层级
页面层级
| 元素 | 指南 |
|---|
| 可见性 | 联系我们或支持放在主导航中,而不仅仅是页脚 |
| 移动端 |
适当的输入类型(电话使用tel),大点击目标 |
|
校对 | 无错别字——转化时刻的可信度 |
|
替代方案 | 如果表单不合适,提供电子邮件、电话、在线聊天 |
信任
- - 响应时间:我们会在24小时内回复
- 隐私:表单附近提供隐私政策链接
- 安全:HTTPS、可见的信任信号
输出格式
- - 表单结构(字段、顺序)
- 文案(标签、占位符、行动号召按钮)
- 页面布局和位置
- SEO元数据
- 无障碍检查清单
相关技能
- - 着陆页生成器:线索捕获着陆页包含联系表单;演示请求行动号召目标页面
- 关于页面生成器:联系页面通常从关于页面链接
- 法律页面生成器:表单附近的隐私政策链接
- 标题标签、元描述、页面元数据:联系页面元数据