From resend-email-best-practices
Guides building deliverable, compliant, and accessible emails. Covers SPF/DKIM/DMARC, email capture, double opt-in, transactional vs marketing, webhooks, retry logic, and list hygiene.
How this skill is triggered — by the user, by Claude, or both
Slash command
/resend-email-best-practices:email-best-practicesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guidance for building deliverable, compliant, user-friendly emails.
Guidance for building deliverable, compliant, user-friendly emails.
[User] → [Email Form] → [Validation] → [Double Opt-In]
↓
[Consent Recorded]
↓
[Suppression Check] ←──────────────[Ready to Send]
↓
[Idempotent Send + Retry] ──────→ [Email API]
↓
[Webhook Events]
↓
┌────────┬────────┬─────────────┐
↓ ↓ ↓ ↓
Delivered Bounced Complained Opened/Clicked
↓ ↓
[Suppression List Updated]
↓
[List Hygiene Jobs]
| Need to... | See |
|---|---|
| Set up SPF/DKIM/DMARC, fix spam issues | Deliverability |
| Build password reset, OTP, confirmations | Transactional Emails |
| Plan which emails your app needs | Transactional Email Catalog |
| Build newsletter signup, validate emails | Email Capture |
| Send newsletters, promotions | Marketing Emails |
| Ensure CAN-SPAM/GDPR/CASL compliance | Compliance |
| Decide transactional vs marketing | Email Types |
| Handle retries, idempotency, errors | Sending Reliability |
| Process delivery events, set up webhooks | Webhooks & Events |
| Manage bounces, complaints, suppression | List Management |
| Make emails accessible (screen readers, alt text, contrast) | Accessibility |
New app? Start with the Catalog to plan which emails your app needs (password reset, verification, etc.), then set up Deliverability (DNS authentication) before sending your first email.
Spam issues? Check Deliverability first—authentication problems are the most common cause. Gmail/Yahoo reject unauthenticated emails.
Marketing emails? Follow this path: Email Capture (collect consent) → Compliance (legal requirements) → Marketing Emails (best practices).
Production-ready sending? Add reliability: Sending Reliability (retry + idempotency) → Webhooks & Events (track delivery) → List Management (handle bounces).
Accessibility?
Most emails fail basic accessibility checks. See Accessibility for lang/dir, presentational tables, headings, alt text, <title>, and contrast.
npx claudepluginhub resend/email-best-practicesGuides building deliverable, compliant, and accessible emails. Covers SPF/DKIM/DMARC, email capture, double opt-in, transactional vs marketing, webhooks, retry logic, and list hygiene.
Guides building deliverable, compliant emails: SPF/DKIM/DMARC, double opt-in, retry logic, webhooks. Fixes spam issues, high bounces, and decides transactional vs marketing.
Guides implementation of transactional email, marketing automation, deliverability (SPF/DKIM/DMARC), and infrastructure decisions for scalable email systems.