Email Sequence Designer

Stop staring at a blank screen trying to figure out what email comes next. This skill builds full email sequences — welcome flows, nurture campaigns, re-engagement drips, onboarding series — with specific timing between sends, subject line strategies, and copy structure for every single email.

What Makes This a Claude Code Skill

Claude Code reads your product context from .claude/ files, figures out your audience and offer, then writes multi-email sequences as structured files in your project. Each email gets a defined purpose, send timing, subject line variants, and copy broken into hook/context/value/CTA blocks. No copy-pasting from a chat window — you get files you can hand to your email tool or developer.

Based on the email-sequence skill from coreyhaines31/marketingskills.

Core Principles

The generated sequences follow three rules that actually matter:

• One Email, One Job — each email has a single purpose, not five competing CTAs
• Value Before Ask — build trust with useful content before pushing for a sale
• Relevance Over Volume — fewer, better-timed emails beat daily spam

Supported Sequence Types

Setup

Create .claude/commands/email-sequence.md:

mkdir -p .claude/commands

Then add this content to .claude/commands/email-sequence.md:

Design a complete email sequence based on $ARGUMENTS.

## Step 1: Gather Context

Read product and audience context from:
- `.claude/brand-voice.md` (if exists) for tone
- `.claude/` directory for product details
- `src/content/` for existing marketing copy and positioning

Ask the user if not specified:
- Sequence type: welcome, nurture, re-engagement, or onboarding
- Target audience and where they signed up
- Primary conversion goal

## Step 2: Build the Sequence

For each email in the sequence, define:
- **Email number and send timing** (e.g., "Email 3 — Day 5, 10am")
- **Purpose** — the one job this email does
- **Subject line** — 2-3 variants, under 50 characters
- **Preview text** — 80-100 characters
- **Copy structure**:
  - Hook (opening line that earns the next line)
  - Context (why this matters right now)
  - Value (the useful thing — tip, insight, resource)
  - CTA (single, clear next step)
- **Estimated word count** — keep under 200 words per email

## Rules
- One Email, One Job — never split attention across multiple CTAs
- Value Before Ask — at least 2 value emails before any sales push
- Relevance Over Volume — cut emails that don't earn their spot
- Subject lines: specific > clever, curiosity > clickbait

## Step 3: Output

Write the full sequence to `./email-sequences/[sequence-type].md`.
Include a summary table at the top with email number, day, subject, and purpose.
Print the summary table to terminal.

Usage

/project:email-sequence welcome sequence for a SaaS trial signup

Claude reads your project context, asks any missing details, then writes a complete email sequence with timing, subject lines, and copy structure for every email in the flow.

Tips

• Run it once per sequence type, then edit the output to match your voice
• The subject line variants give you A/B test options out of the box
• Pair with the Brand Voice Linter to check the generated copy against your guidelines