Instructions
Build transactional email templates as React components (e.g. react-email style) with plain-text counterparts.
When to Use
- Use for receipts, password resets, invite links, and product notifications.
- Prefer
content-creatorfor social/marketing copy, not cold outreach from this skill. - Prefer
webhook-receivers/payments-handbookwhen the email is triggered by payment events.
- Layout: table-based width constraints; max width ~600px; system fonts or a web-safe stack.
- Images: absolute URLs only; alt text; never put critical info only in images.
- CTA: bulletproof button pattern (nested table) when Outlook support is required.
- Text version: mirror links and key numbers; do not leave empty
text/plain. - Testing: local preview command pattern; no live sends without user consent.
- Dark mode: test contrast; do not assume pure black on pure white.
- PII: placeholders only in samples; never paste real customer emails or addresses.
Outcomes
- One template file tree + style rules + text body outline + preview command.
Output Rules
No marketing growth hacks; transactional tone only.
Scope and boundaries
- In scope: receipts, resets, notifications.
- Out of scope: cold outreach campaigns, purchased lists.
Safety
- No real user PII in examples; placeholders only.
Troubleshooting
- Broken layout in Outlook: revert to nested tables; avoid flex/grid.
- Links rewrite by ESP: use absolute https URLs; test click tracking carefully.
- Dark mode email clients: verify contrast on both themes.
Related skills
payments-handbook- receipt triggerscontent-creator- social copy (not transactional)
GitHub: https://github.com/bh611627/skillcodex/tree/main/skills/react-email-templates/SKILL.md
npm: https://www.npmjs.com/package/@skillcodex/skills