What this prompt does
This prompt turns an LLM into an email designer that ships a complete transactional email system for a [store_type] store, not a single one-off template. You tell it which [email_types] you need and your [brand_style], and it generates the full set as production HTML: welcome, order confirmation, shipping notification, abandoned cart, review request, and win-back. Each one follows the same skeleton (logo header, content, single CTA, footer with a visible unsubscribe) so the system feels coherent across the whole customer lifecycle.
The structure works because it bakes in the constraints that actually break email. It is mobile-first because most opens happen on a phone, it bans web fonts because email clients silently strip them, and it enforces one primary CTA per message so the reader is never split between two actions. The [template_count] variable controls how many templates come back, and [brand_style] shapes the accent color and tone while keeping the white background and system fonts that make messages render reliably in Gmail, Apple Mail, and Outlook.
When to use it
- You are launching a new store and need the entire transactional email layer at once
- You are migrating off a templated ESP and want clean, client-safe HTML you control
- An existing flow renders badly on mobile or in Outlook and you want a rebuild
- You need A/B subject line variants and preview text written alongside the templates
- You want honest urgency in the abandoned-cart email rather than fake countdown timers
- You need send-timing recommendations to wire into your automation tool
Example output
You get a set of [template_count] templates, each delivered as a block: two A/B subject line variants, preview text, the full responsive HTML table-based template, and a send-timing recommendation. The HTML uses inline styles, system-safe fonts, and a single accent color for the CTA button, with alt text on images and a clearly visible unsubscribe link in every footer.
Pro tips
- Set
[store_type]precisely ("premium skincare" beats "ecommerce") so copy and imagery match your catalog - Trim
[email_types]to only the flows you will actually send; an unused win-back template just rots - Keep
[brand_style]to a few concrete words plus your hex accent so the AI does not over-design - Always test the returned HTML in Litmus or a real Outlook client before going live; rendering claims need verification
- Ask for a dark-mode pass as a follow-up if your audience skews toward Apple Mail
- Push back on any template that introduces a second primary CTA; regenerate that one rather than editing by hand
