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:
- 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---2name: contact-page-generator3description: 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.4---5
6# Pages: Contact
7
8Guides contact page design and form optimization for conversions.
9
10**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.
11
12## Initial Assessment
13
14**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand voice.
15
16Identify:
171. **Contact types**: Sales, support, general, press
182. **Form purpose**: Lead capture, support ticket, demo request
193. **Alternative channels**: Email, phone, chat, social
20
21## Best Practices
22
23### Form Design
24
25| Principle | Guideline |
26|-----------|-----------|
27| **Short** | 3-5 fields for basic contact; long forms increase abandonment |
28| **Single column** | Vertical layout; works better on mobile |
29| **Logical grouping** | Name+email together; address fields together |
30| **Required fields** | Mark clearly (asterisk); avoid surprises |
31| **Progressive disclosure** | Show relevant fields based on selections |
32
33### Field Labels
34
35- **Clear language**: "Email Address" not "Email ID"
36- **Conversational**: Friendly, welcoming
37- **No jargon**: Universally understood terms
38
39### CTA Button
40
41- **Action verbs**: "Send Message," "Get in Touch," "Start a Conversation"
42- **Avoid generic**: "Submit" ? "Send Message"
43- **Stand out**: Contrasting color, clear hierarchy
44
45### Page-Level
46
47| Element | Guideline |
48|---------|-----------|
49| **Visibility** | "Contact" or "Support" in main nav, not just footer |
50| **Mobile** | Appropriate input types (tel for phone), large tap targets |
51| **Proofreading** | No typos--credibility at conversion moment |
52| **Alternatives** | Email, phone, chat if form isn't right |
53
54### Trust
55
56- **Response time**: "We reply within 24 hours"
57- **Privacy**: Link to privacy policy near form
58- **Security**: HTTPS, visible trust signals
59
60## Output Format
61
62- **Form** structure (fields, order)
63- **Copy** (labels, placeholder, CTA)
64- **Page** layout and placement
65- **SEO** metadata
66- **Accessibility** checklist
67
68## Related Skills
69
70- **landing-page-generator**: Lead capture LP contains contact form; demo request CTA destination
71- **about-page-generator**: Contact often linked from About
72- **legal-page-generator**: Privacy policy link near form
73- **title-tag, meta-description, page-metadata**: Contact page metadata
kostja94