email-systems · travisjneuman — Claude Code skill: what it does, how to install
email-systems — a skill for Claude Code that guides transactional email setup, template design, and deliverability records. Runs when configuring sending infrastructure, building HTML templates, or troubleshooting inboxing.
MIT 132 installs ★ 114 updated 2026-11-10
npx skills add travisjneuman/.claude --skill email-systems -a claude-codeWhat email-systems does
This skill supplies architecture patterns and reference files for transactional email services like Resend, AWS SES, SendGrid, and Postmark. It guides coding responsive templates with React Email or MJML, handling background queues with retry mechanisms, and processing bounce webhooks.
It enforces separation between marketing and transactional domains, keeping bounce rates under 2% and complaint rates under 0.1%. Modern layout techniques like flexbox and CSS grid are ruled out in favor of table-based structures with inline styling, matching legacy client render engines.
What it helps with
- configure SPF, DKIM, and DMARC records for sender domains
- build responsive HTML email templates using React Email or MJML
- set up background queues with retries for outbound messages
- separate marketing and transactional sending domains
- handle bounce notifications and spam complaints
Example prompts for the agent
- Set up transactional sending with Resend and React Email templates
- Generate DNS records for SPF, DKIM, and DMARC for our sending domain
- Build an asynchronous email queue with retry handling and bounce webhooks
How to install email-systems
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill email-systems -a claude-code2Manually: put the files in place
~/.claude/skills/email-systems/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/email-systems/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill email-systems -a codex2Manually: put the files in place
.agents/skills/email-systems/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill email-systems -a cursor2Manually: put the files in place
.cursor/skills/email-systems/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install travisjneuman/.claude skills/email-systems2Manually: put the files in place
.github/skills/email-systems/SKILL.md1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill email-systems -a gemini-cli2Platform CLI
gemini skills install https://github.com/travisjneuman/.claude --path skills/email-systemsManually: put the files in place
.devin/skills/email-systems/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill email-systems -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about email-systems
How do I install email-systems in Claude Code?
Run npx skills add travisjneuman/.claude --skill email-systems -a claude-code. Alternatively, copy the skill definition directly into ~/.claude/skills/email-systems/SKILL.md.
What does email-systems do?
It provides architectural rules, queuing patterns, and HTML guidelines for sending emails from web apps. The AI agent uses these files when scaffolding Resend or SES integrations and writing MJML or React Email components.
What is required to use email-systems?
The skill itself requires no runtime dependencies, but working implementations need an account with an email provider like Resend, AWS SES, SendGrid, or Postmark, plus DNS access to verify domain records.
Source text
SKILL.md · MIT
--- name: email-systems description: >- Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability. --- # Email Systems ## Overview This skill covers building reliable email systems for web applications, including transactional email sending, template design, deliverability optimization, and inbox placement. It addresses integration with email service providers (Resend, AWS SES, SendGrid, Postmark), building responsive HTML email templates with React Email and MJML, configuring DNS records for deliverability (SPF, DKIM, DMARC), managing email types (transactional, notification, marketing), queue management, and bounce/complaint handling. Use this skill when sending welcome emails, password resets, order confirmations, notification digests, marketing campaigns, or any system-generated email. Also use when debugging deliverability issues or migrating between email providers. --- ## Core Principles 1. **Transactional and marketing are different** - Transactional emails (password reset, receipt) must arrive instantly and reliably. Marketing emails (newsletter, promo) can be batched and should have unsubscribe links. Never mix them on the same sending domain. 2. **HTML email is not web development** - Email clients render HTML from 2004. No flexbox, no grid, no modern CSS. Use tables for layout, inline styles, and test across clients. React Email and MJML abstract this pain. 3. **Deliverability is earned** - SPF, DKIM, and DMARC are table stakes, not guarantees. Maintain low bounce rates (< 2%), low complaint rates (< 0.1%), and warm up new sending domains gradually. 4. **Queue everything** - Never send email synchronously in a request handler. Queue email sends to avoid blocking user requests and to enable retry on failure. 5. **Test before sending** - Use Mailtrap or Ethereal in development, preview in multiple clients (Litmus, Email on Acid), and verify every link works. --- ## Reference files Detailed material is in separate files so this overview stays short. Read only the file whose topic matches the task; each one is self-contained. Paths are relative to the folder that holds this `SKILL.md` (in the full toolkit install, `~/.claude/skills/email-systems/`). | Topic | File | Covers | | --- | --- | --- | | Key Patterns | [`references/key-patterns.md`](references/key-patterns.md) | Pattern 1: React Email Templates with Resend; Pattern 2: Email Queue with Retry Logic; Pattern 3: DNS Configuration for Deliverability; Pattern 4: Bounce and Complaint Handling | | Anti-Patterns | [`references/anti-patterns.md`](references/anti-patterns.md) | 14 lines | | Checklist | [`references/checklist.md`](references/checklist.md) | 18 lines | ## Email Provider Comparison | Provider | Best For | Pricing | React Email | Key Feature | |---|---|---|---|---| | **Resend** | Developer-friendly transactional | 100/day free, $20/mo for 50k | Native | Best DX, React Email team | | **AWS SES** | High volume, cost optimization | $0.10 per 1,000 | Via render | Cheapest at scale | | **SendGrid** | Marketing + transactional | 100/day free | Via render | Marketing automation | | **Postmark** | Transactional reliability | $15/mo for 10k | Via render | Best transactional deliverability | --- ## Related Resources - **Skills:** `authentication-patterns` (password reset emails), `payment-integration` (invoice/receipt emails) - **Skills:** `event-driven-architecture` (email as async event) - **Rules:** `docs/reference/stacks/react-typescript.md` (React Email component patterns)
© travisjneuman · MIT · travisjneuman/.claude
Similar skills
All skills for Backend and APIs →email-systems by other authors comes first.