email

name	email
description	Email and notifications. SendGrid, SES, Postmark, Resend, MJML, React Email, delivery tracking, DNS auth.

Email — Email & Notification Systems

Activate When

• User invokes /godmode:email
• User says "send emails", "email templates"
• User says "notification system", "push notifications"
• User says "bounce handling", "deliverability"
• Application needs email or notification infrastructure

Workflow

Step 1: Requirements Discovery

# Detect existing email infrastructure
grep -r "resend\|sendgrid\|aws-sdk.*ses\|postmark" \
  package.json pyproject.toml go.mod 2>/dev/null

# Find existing templates
find . -path ./node_modules -prune -o \
  -name "*.mjml" -o -name "*.email.tsx" \
  -o -path "*/emails/*" 2>/dev/null | head -20

# Check for queue system
grep -r "bullmq\|bull\|sqs\|celery" \
  package.json pyproject.toml 2>/dev/null

NOTIFICATION REQUIREMENTS:
  Channels: Email | Push | SMS | In-app
  Email types: Auth (critical) | Transactional (high)
    | Product (medium) | Marketing (low)
  Volume: Trans <N>/day, Marketing <N>/month
  Compliance: CAN-SPAM, GDPR, CASL

IF no queue system: add one (never send sync)
IF no provider: recommend based on needs
IF no DNS auth: set up SPF/DKIM/DMARC

Step 2: Email Service Selection

| Feature     | SendGrid | SES    | Postmark | Resend |
|-------------|----------|--------|----------|--------|
| Best for    | Full feat| Volume | Transact | Dev DX |
| Free tier   | 100/day  | 62K/mo | 100/mo   | 3K/mo  |
| Delivery    | Good     | Good   | Excellent| Good   |
| Templates   | Yes      | SES v2 | Yes      | React  |

IF startup/dev-focused: Resend (best DX)
IF high-volume transactional: Postmark
IF full marketing + transactional: SendGrid
IF AWS-native / cost-sensitive: SES