contact-page-generator
The contact-page-generator skill guides the design and optimization of contact pages and web forms to improve conversion rates. Use this skill when creating new contact pages, refining existing contact forms, auditing page effectiveness, or when users reference contact pages, contact forms, support forms, inquiry forms, or similar terminology. The skill provides structured guidance on form field design, copy optimization, page layout, mobile responsiveness, trust-building elements, and accessibility considerations tailored to different contact purposes like sales inquiries, support tickets, or demo requests.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/contact-page-generator && cp -r /tmp/contact-page-generator/skills/pages/brand/contact ~/.claude/skills/contact-page-generatorSKILL.md
# 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
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.