Claude Design email design systems — the repeatable recipe
How to stand up an on-brand email design system for ANY freelance/agency client fast, using Claude Design for the visual system and Claude Code for the email-safe build. Written 2026-06-12 (Field Trip + FixMyOculus lanes). Mirrors the proven Salvo feed pattern (Downloads\Salvo-ClaudeDesign-Feed).
What Claude Design is (verified June 2026)
- Anthropic product (research preview Apr 2026, Pro/Max included). Prompt → polished artifact (mockups, frames, decks, one-pagers), refined via conversation, direct edits, and generated sliders.
- Brand input: upload live website URL, logos, palette images, style guide PDFs, PPTX, and links to front-end code. It analyzes these and produces a UI kit / design system it then applies to everything.
- It does NOT reliably read .fig files directly. Highest-fidelity input = a design-tokens .md file (colors, type scale, spacing, grid) + logos + style guide PDF + code examples. Figma round-trips go through Claude Code or html.to.design.
- It outputs web frames/mockups, NOT email-safe HTML. The email build (tables, VML, dark mode, ALT text) is a Claude Code job using
email_cta_playbook.md+effects_matrix.md.
The pipeline (per client)
- Feed folder (one per client, pattern below) → give to Claude Design, ask for the email design system + frames per concept.
- Moodboard first (a Claude Code session builds it: brand read, reference lineage, tokens, module set, 2 wireframed concepts). The moodboard IS the creative direction input and doubles as a client deliverable. Template:
dev/jobs/fieldtrip/moodboard.html. - Claude Design: generate the design system + per-email frames from the feed + moodboard.
- Claude Code: convert frames to 600px table-based email HTML (hybrid CTA, 60/40 image-text, dark-mode border trick, styled ALT text, GIF first-frame rule, single ask per email).
- Review dashboard: clone
/root/fieldtrip-review(zero-dependency node app, port-per-client, Caddyhandle_path /<client>*). Client flips desktop/mobile, comments, approves. QA-drive before sharing (screenshots both viewports + API failure modes). - Approved → build in the client's ESP (Klaviyo / SendSquared / etc.), QA per playbook, schedule.
Feed folder pattern (mirror of Salvo-ClaudeDesign-Feed)
<Client>-ClaudeDesign-Feed/
READ ME FIRST.txt <- copy-paste form blurb + hard copy rules (no em dashes, no AI-isms, client naming rules)
1-logos/ <- transparent PNG/SVG, light + dark
2-style-guide/ <- brand PDF if exists + tokens.md (colors hex, type scale, spacing, voice)
3-code-examples/ <- on-brand HTML we already built (emails, landing pages) = target styling
4-references/ <- moodboard PDF/screens, winning email screenshots
The READ ME copy-paste blurb always includes: company one-liner, what we build with the system, primary CTA per asset type, positioning rules, and the hard copy rules.
Reference library for editorial email direction
- Soho House actual email component library (their designer, public): https://alecdrewitt.com/email-component-library
- RGE screenshots hotlink fine:
https://pro-really-good-emails.s3.eu-west-1.amazonaws.com/emails/<slug>.png - Editorial digest archetype: Domino "Your Daily Edit" (alternating rows, tinted sections). Type-inside-image + witty single CTA: Trunk Club.
Concept hooks library (from Wellcopy "Pixel Picassos" email-of-the-week awards, calls #1365 + #1395)
Wellcopy ran a biweekly award for best emails; the Apr 10 2026 call narrates the winners. Patterns extracted, reusable on any account (never name the award client-facing):
- "In case of X, break glass" — product behind glass, benefit-swappable (in case of dry skin / IBS / dead headset).
- Themed narrative welcome — e.g. detective theme: "10% off is waiting in the evidence room", typewriter type, "rookie badge unlocked". Welcome flows are the highest-CTR real estate (5.58% avg), spend the creativity there.
- POV / before-after comic — "POV: you finally upgraded" framing for upgrades/repairs.
- Education hook tied to product — "Always fidgeting in your chair? There's a reason why" → why that's bad → product.
- Photo gallery moments, cute-and-cheeky galleries (Royal Codes style), blur-reveal effects for education emails.
- Ranked lists — rank by something sensory/fun (pool temperature at golden hour), not specs. Rule: ONE concept per send. Concepts replace discounting, they don't stack with it.
Hard rules that always apply (enforce in code, not prompts)
- No em dashes anywhere; strip post-LLM. No AI-trope words. Per-client naming rules (e.g. "Salvo Software" never "Salvo").
- Never name marita-os/driftbymar inside client-facing copy or client systems. Review links on driftbymar.app follow the EVG precedent (reviewers use them) but never go into a client's own system/workflow.
- Approval gate: drafts only, nothing sends without explicit OK.