newsletter-signup-generator
# newsletter-signup-generator This Claude Code skill guides the design and optimization of email newsletter signup forms across placements like headers, footers, popups, and inline sections. Use it when users need to create, audit, or improve newsletter subscription forms, capture leads, or discuss email list building strategies. The skill covers form field minimization, value proposition clarity, mobile-responsive design, accessibility standards, and technical implementation including validation and privacy compliance.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/newsletter-signup-generator && cp -r /tmp/newsletter-signup-generator/skills/components/conversion/newsletter-signup ~/.claude/skills/newsletter-signup-generatorSKILL.md
# Components: Newsletter Signup Guides newsletter signup form design for list growth. Email subscribers spend 138% more than non-subscribers; top popups convert at 23%+. **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 audience and value proposition. Identify: 1. **Placement**: Header, footer, popup, inline, sidebar 2. **Incentive**: What subscribers receive 3. **Platform**: Web, mobile, both ## Form Design ### Minimal Fields - **Email only** when possible; highest conversion - Add name only if needed for personalization - Wrong number of fields significantly impacts conversion ### Value Proposition - Clear: what subscribers receive, how often - Transparent: avoid disappointing subscribers - Incentive: lead magnet, discount, exclusive content ### Visual Design - Clearly clickable submit button - Mobile-first; responsive layout - Appropriate input types (e.g., `type="email"` for mobile keyboards) - Trust marks or security indicators ## Placement | Placement | Best For | Pros | Cons | |-----------|----------|------|------| | **Header** | High visibility | Always visible | Limited space | | **Footer** | Secondary capture | Non-intrusive | Lower visibility | | **Footer bar** | Persistent | Sticky | Can annoy | | **Popup** | High intent | High conversion | Intrusive | | **Inline** | Content pages | Contextual | Depends on scroll | - Avoid hiding forms behind unclicked buttons/links - Don't place competing forms nearby ## Accessibility | Requirement | Practice | |-------------|----------| | **Labels** | `<label>` for each input; `for`/`id` association | | **Placeholders** | Don't replace labels; supplement only | | **Error messages** | Clear, associated with field | | **Keyboard** | Full tab order; submit via Enter | | **Touch targets** | ≥44×44px for submit button | ## Technical - **Validation**: Client-side; server-side required - **Privacy**: Link to privacy policy; GDPR/CCPA compliance - **Double opt-in**: When required by jurisdiction or best practice ## Output Format - **Form structure** (fields, copy) - **Placement** recommendation - **Value proposition** suggestions - **Accessibility** checklist ## Related Skills - **signup-login-page-generator**: Full account signup; form design principles apply - **landing-page-generator**: Lead capture landing page contains signup form; LP exchanges value for email - **email-marketing**: Full email marketing strategy; EDM, newsletter, deliverability, content types - **footer-generator**: Footer often hosts signup forms - **cta-generator**: Submit button is a CTA - **trust-badges-generator**: Trust marks near form
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.