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 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.