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 product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-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."4---56# Pages: Contact78Guides contact page design and form optimization for conversions.910**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.1112## Initial Assessment1314**Check for product marketing context first:** If `.claude/product-marketing-context.md` or `.cursor/product-marketing-context.md` exists, read it for brand voice.1516Identify:171. **Contact types**: Sales, support, general, press182. **Form purpose**: Lead capture, support ticket, demo request193. **Alternative channels**: Email, phone, chat, social2021## Best Practices2223### Form Design2425| 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 |3233### Field Labels3435- **Clear language**: "Email Address" not "Email ID"36- **Conversational**: Friendly, welcoming37- **No jargon**: Universally understood terms3839### CTA Button4041- **Action verbs**: "Send Message," "Get in Touch," "Start a Conversation"42- **Avoid generic**: "Submit" ? "Send Message"43- **Stand out**: Contrasting color, clear hierarchy4445### Page-Level4647| 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 |5354### Trust5556- **Response time**: "We reply within 24 hours"57- **Privacy**: Link to privacy policy near form58- **Security**: HTTPS, visible trust signals5960## Output Format6162- **Form** structure (fields, order)63- **Copy** (labels, placeholder, CTA)64- **Page** layout and placement65- **SEO** metadata66- **Accessibility** checklist6768## Related Skills6970- **landing-page-generator**: Lead capture LP contains contact form; demo request CTA destination71- **about-page-generator**: Contact often linked from About72- **legal-page-generator**: Privacy policy link near form73- **title-tag, meta-description, page-metadata**: Contact page metadata
ulpi-io