--- name: marketing-email-template-builder description: "Builds a complete modular marketing email — subject line variants, preheader, and a stack of reusable content blocks in both responsive HTML and plain-text versions — populated from a campaign brief. Use when building a marketing email, creating a reusable email template system, or producing send-ready HTML and text for a nurture, promo, announcement, or lifecycle campaign." argument-hint: "[campaign-type] [audience]" allowed-tools: ["Read"] --- # Marketing Email Template Builder ## Purpose Produce a send-ready marketing email as a stack of modular content blocks — subject lines, preheader, hero, body sections, and CTA — delivered in responsive inline-styled HTML plus a plain-text version, populated directly from a campaign brief. Lets a lifecycle team ship on-brand emails at scale without routing every send through an agency or designer. ## When to Use Invoke this skill when the user asks to: - Build a marketing email or email template from a campaign brief - Create send-ready HTML for a promo, announcement, or nurture email - Produce a modular block system they can reuse across future sends - Generate matching subject line and preheader options for an email - Convert a campaign concept into both HTML and plain-text versions - Draft a lifecycle email (welcome, re-engagement, upsell, event) with a clear CTA ## Inputs Required Before starting, collect: - **Campaign type**: Promo / announcement / newsletter / welcome / re-engagement / event / product update - **Primary goal**: The one action this email should drive (click to page, RSVP, redeem code, reply, upgrade) - **Audience**: Who receives this — segment, lifecycle stage, or list description - **Core message**: The single most important thing the reader must take away - **Offer/CTA details**: Button text, destination URL, and any offer specifics (discount, deadline, feature) - **Brand basics**: Brand name, primary color (hex), tone (bold / warm / professional / playful) - **Personalization tokens**: Any merge fields to use (e.g., first name, plan name) and the ESP's token syntax if known If brand color or token syntax is missing, default to a neutral palette and `{{first_name}}` style tokens, and note the assumption. ## Instructions ### Step 1: Map the Block Stack Choose the block sequence that fits the campaign type. Use this as the default skeleton, adding or removing blocks per goal: - **Preheader** (hidden inbox preview text, 40–90 chars) - **Header block** — logo/brand name, optional nav or tagline - **Hero block** — headline + supporting line + primary CTA button (above the fold) - **Body block(s)** — 1–3 sections carrying the core message; each is a self-contained module - **Secondary CTA / reinforcement block** — restates the action for skimmers - **Social proof or urgency block** — optional; use only when real (testimonial, stat, deadline) - **Footer block** — address line, unsubscribe, preference center, legal Match stack density to type: promos run lean (hero + one body + CTA), newsletters run modular (multiple stacked body blocks), lifecycle emails lead with one clear message and one CTA. ### Step 2: Write Subject Lines and Preheader Produce **5 subject line variants** across distinct angles, each ≤50 characters: 1. Direct/benefit — states the payoff plainly 2. Curiosity — opens a loop tied to the core message 3. Urgency/timeliness — only if a real deadline exists 4. Personalized — uses a token or segment reference 5. Short/punchy — 3–5 words for inbox scannability Write **1 preheader** (40–90 chars) that complements the subject rather than repeating it, and does not leave dead preview text. ### Step 3: Write Block Content For each block in the stack, write copy calibrated to the brand tone and audience: - **Hero headline**: one line, ≤10 words, leads with the reader's benefit - **Body sections**: each has a mini-headline and 1–3 short sentences; one idea per block; scannable - **CTA buttons**: action-first, ≤4 words (e.g., "Claim my spot," "Start free trial") — never "Click here" - Insert personalization tokens where they earn attention, not decoratively ### Step 4: Build the Responsive HTML Assemble the blocks into a single email-safe HTML document: - Use table-based layout (``), not divs/flexbox — required for Outlook and older clients - Apply **inline styles** on every element; do not rely on a `