360 Secure SkillHub
360 安全技能中心

contact-page-generator

为联系页面和表单提供设计与优化指南,覆盖表单字段数量与单列布局、字段标签、CTA 文案、页面可见性与移动端输入类型、信任要素,并输出表单结构、文案、页面布局、SEO 元数据与无障碍检查清单;首次使用时会先读取项目上下文文件以获取品牌语调。

kostja94
kostja94
热度 48.90
最近更新 2026-05-11 17:34:12
分类:营销依赖:纯提示词应用场景:文案创作 / 模板

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add contact-page-generator
Metadata
name
contact-page-generator
description
When the user wants to create, optimize, or audit contact page and forms. Also use when the user mentions "contact page," "contact form," "get in touch," "support form," "contact us," "reach us," "contact information," "support contact," or "inquiry form." For sitewide page planning, use website-structure.
metadata
{"version":"1.0.1"}

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
  2. Form purpose: Lead capture, support ticket, demo request
  3. 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