transactional-email
SolidAdding transactional or alert email, choosing a provider, 'sent twice', 'never arrived': app email sent once, never lost, with one-click unsubscribe.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- phuryn
- Repository
- phuryn/product-engineering
- Created
- 2 weeks ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
add-transactional-email
Make the email an application owes a person actually arrive: receipts, password resets and sign-in codes, from an authenticated sending domain with SPF, DKIM and DMARC, a return path that accepts bounces, dedupe so a retry does not send twice, and suppression so a bounced or complained address is never mailed again. Use when mail lands in spam or nowhere, when an app has no sending domain, or when someone asks for transactional email.
email-and-templating
Send transactional email correctly — provider choice (Resend/Postmark/SES), react-email/MJML templating, and SPF/DKIM/DMARC deliverability basics. Use when a task sends email — signup confirmation, password reset, receipt, notification digest. Triggers on email, transactional email, Resend, Postmark, SES, react-email, MJML, SPF, DKIM, DMARC, deliverability.
transactional-email
Set up, diagnose and unify transactional email across projects — SPF/DKIM/DMARC, MX and inbound mail, Spamhaus/blocklist checks, provider choice (Brevo, Resend, SMTP, Postmark, SES), a single sendEmail() module with one env schema, and per-tenant reputation isolation for multi-tenant SaaS. Use whenever email is being added to a project, when mail is not arriving or landing in spam, when a domain is on a blocklist, or when a product needs to send mail on behalf of its customers.