pages-contact

Guides contact page design and form optimization for conversions.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "pages-contact" with this command: npx skills add kostja94/marketing-skills/kostja94-marketing-skills-pages-contact

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

  • pages-about: Contact often linked from About

  • pages-legal: Privacy policy link near form

  • seo-on-page-title, seo-on-page-description, seo-on-page-metadata: Contact page metadata

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

google-search-console

No summary provided by upstream source.

Repository SourceNeeds Review
General

tiktok-captions

No summary provided by upstream source.

Repository SourceNeeds Review
General

email-marketing

No summary provided by upstream source.

Repository SourceNeeds Review
General

branding

No summary provided by upstream source.

Repository SourceNeeds Review