Email Systems
Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders.
This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale.
When to Use
- Use this skill when the request clearly matches the capabilities and patterns described above.
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
- Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Principles
- Patterns
- Transactional Email Queue
- Email Event Tracking
- Template Versioning
- Bounce Handling State Machine
- React Email Components
- Preference Center
- Sharp Edges
- Missing SPF, DKIM, or DMARC records
- SPF (Sender Policy Framework)
- DKIM (DomainKeys Identified Mail)
- DMARC (Domain-based Message Authentication)
- Using shared IP for transactional email
- Option 1: Dedicated IP (high volume)
- Option 2: Transactional-only provider
- Separate concerns:
- Not processing bounce notifications
Reference Map
references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
1---2name: email-systems3description: Email has the highest ROI of any marketing channel. $36 for every4license: MIT5---67# Email Systems89Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders.1011This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale.1213## When to Use14- Use this skill when the request clearly matches the capabilities and patterns described above.1516## Core Workflow171. Confirm the request matches this skill's trigger, scope, and risk profile.182. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.193. Load `references/full-guidance.md` when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.204. Apply only the relevant guidance instead of loading or repeating the entire reference by default.215. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.2223## Topic Map24- Principles25- Patterns26- Transactional Email Queue27- Email Event Tracking28- Template Versioning29- Bounce Handling State Machine30- React Email Components31- Preference Center32- Sharp Edges33- Missing SPF, DKIM, or DMARC records34- SPF (Sender Policy Framework)35- DKIM (DomainKeys Identified Mail)36- DMARC (Domain-based Message Authentication)37- Using shared IP for transactional email38- Option 1: Dedicated IP (high volume)39- Option 2: Transactional-only provider40- Separate concerns:41- Not processing bounce notifications4243## Reference Map44- `references/full-guidance.md` preserves the complete original guidance, including examples and detailed edge cases.4546## Limitations47- Use this skill only when the task clearly matches the scope described above.48- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.49- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.5051## Progressive Loading52Keep this `SKILL.md` as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
newmindsgroup