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 analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
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 promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.