/api-email-setup-resend

name: api-email-setup-resend
description: Resend email setup, domain verification

Resend Email & React Email Setup

> **Quick Guide:** Resend email API with React Email templates. Use the `react` prop to pass components directly to `resend.emails.send()` -- no manual `render()` needed. Keep email templates in a dedicated package for monorepo separation. Verify your sending domain before production. Use `@react-email/render` (not `@react-email/components`) if you need to render to HTML strings manually.

---

<critical_requirements>

CRITICAL: Before Using This Skill

**(You MUST use `RESEND_API_KEY` environment variable -- NEVER hardcode API keys)**

**(You MUST verify your sending domain in Resend dashboard before production -- unverified domains only send to your own email)**

**(You MUST use `@react-email/components` for email UI components and `@react-email/render` for HTML rendering -- these are separate packages)**

**(You MUST use `resend.emails.send({ react: MyTemplate(props) })` as the primary sending pattern -- manual `render()` to HTML is only needed for non-Resend senders)**

</critical_requirements>

---

**Auto-detection:** Resend setup, resend install, React Email setup, email templates setup, RESEND_API_KEY, domain verification, SPF DKIM DMARC, transactional email setup, email preview server, @react-email/components, react-email

**When to use:**

• Initial Resend + React Email setup in a project
• Configuring domain verification and DNS records
• Setting up the email preview dev server
• Structuring email templates in a monorepo

**When NOT to use:**

• Marketing email campaigns (use a dedicated marketing email platform)
• SMS or push notifications (different service)
• Non-JavaScript backends (this skill covers React Email templates, which require Node.js)
• Need SMTP relay (Resend is API-only)

**Detailed Resources:**

• [examples/core.md](examples/core.md) - Client setup, sending patterns, template structure, preview server

---

<philosophy>

Philosophy

Resend is a **developer-first email API** built by the creators of React Email. React Email brings modern component patterns to email development, replacing legacy table-based HTML.

**Core principles:**

1. **Emails as React components** - Write emails with JSX, Tailwind CSS, and TypeScript 2. **Preview before send** - Local dev server shows exact email rendering 3. **Monorepo separation** - Email templates in dedicated package, not mixed with app code 4. **`react` prop over `render()`** - Resend SDK renders components internally when you pass them via the `react` prop

</philosophy>

---

<patterns>

Core Patterns

Pattern 1: Sending with the `react` Prop (Preferred)

The Resend SDK accepts React components directly via the `react` prop -- no manual HTML rendering needed.

const { data, error } = await resend.emails.send({
  from: "Your App <noreply@yourdomain.com>",
  to: ["user@example.com"],
  subject: "Welcome!",
  react: WelcomeEmail({ userName: "John" }),
});

**Why good:** No manual `render()` call, SDK handles conversion internally, cleaner code

**When to use `render()` instead:** Only when sending via a non-Resend email provider that needs an HTML string. Import from `@react-email/render`, not `@react-email/components`.

See [examples/core.md](examples/core.md) for full sending and rendering examples.

---

Pattern 2: Domain Verification

Verify your domain to send from custom addresses. Unverified accounts can only send to your own email.

1. Go to Resend Dashboard > Domains > Add Domain 2. Add the DNS records Resend provides to your DNS provider:

• **SPF** (TXT): `v=spf1 include:amazonses.com ~all`
• **DKIM** (3 CNAME records): Values provided by Resend
• **DMARC** (TXT, recommended): `v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com`

3. Click Verify -- DNS propagation can take up to 48 hours

**Why this matters:** Unverified domains are limited to sending to your account email only. Production sending requires verification. Proper DNS records prevent emails from landing in spam.

---

Pattern 3: Monorepo Package Structure

Keep email templates in a dedicated package, separate from your application code.

packages/emails/
├── package.json
├── tsconfig.json
├── src/
│   ├── index.ts              # Re-export all templates
│   ├── client.ts             # Resend client singleton
│   ├── layouts/
│   │   └── base-layout.tsx   # Shared layout wrapper
│   ├── components/
│   │   ├── button.tsx        # Reusable email button
│   │   └── footer.tsx        # Email footer
│   └── templates/
│       ├── verification-email.tsx
│       ├── password-reset.tsx
│       └── welcome-email.tsx
└── emails/                   # For react-email dev server

**Why good:** Reusable across apps, prevents bundling issues, clean separation of concerns

See [examples/core.md](examples/core.md) for full client setup and template examples.

---

Pattern 4: Email Error Handling

Resend returns `{ data, error }` -- always check the error.

const { data, error } = await resend.emails.send(emailOptions);

if (error) {
  console.error("[Email] Send failed:", error.name, error.message);
  return { success: false, error: error.message };
}

return { success: true, id: data?.id };

**Why good:** Explicit error checking, structured logging, returns typed result. Never ignore the error response -- the SDK does not throw on send failures.

---

Pattern 5: Webhook Verification

Always verify webhook signatures before processing events. The `verify()` method **throws** on invalid signatures.

const payload = await request.text(); // Raw body, NOT parsed JSON

try {
  const event = resend.webhooks.verify({
    payload,
    headers: {
      id: request.headers.get("svix-id") ?? "",
      timestamp: request.headers.get("svix-timestamp") ?? "",
      signature: request.headers.get("svix-signature") ?? "",
    },
    webhookSecret: process.env.RES