When the user wants to design, optimize, or audit newsletter signup forms. Also use when the user mentions "newsletter," "email signup," "subscribe form," "email capture," "lead magnet," "newsletter form," "email opt-in," "subscribe CTA," "newsletter signup," or "email list building." For email strategy, use email-marketing.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for audience and value proposition.
Identify:
type="email" for mobile keyboards)| 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 |
| 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 |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/newsletter-signup · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/newsletter-signup"
cp -r "skills/components/conversion/newsletter-signup" ".claude/skills/newsletter-signup"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.