email-sending-best-practices
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseEmail Sending Best Practices
邮件发送最佳实践
This skill helps review and plan healthy email programs. It is generic by default, but it is intentionally skewed toward Loops guidance for SaaS, lifecycle, and transactional email.
此Skill可帮助审核和规划健康的邮件运营方案。默认情况下它是通用型指南，但会针对性地偏向Loops针对SaaS、用户生命周期及事务性邮件的指导规范。
When To Use
使用场景
Use this skill when the task is about email quality, risk, or strategy rather than low-level API implementation.
Typical use cases:
- diagnose poor inbox placement or sender reputation
- review consent flows, double opt-in, list hygiene, or unsubscribe behavior
- improve subject lines, preview text, sender identity, personalization, or rendering
- choose between campaign, lifecycle automation, and transactional email
- plan onboarding, retention, re-engagement, dunning, or product-update email programs
- review a Loops setup for best-practice gaps
Do not default to this skill for pure implementation tasks like "send an event with the Loops API" or "wire up transactional email in Next.js". Use the skill for those.
api当任务聚焦于邮件质量、风险或策略，而非底层API实现时，可使用此Skill。
典型使用场景：
- 诊断收件箱投递效果差或发件人信誉不佳的问题
- 审核用户同意流程、双重确认订阅、邮件列表清洁度或退订行为
- 优化主题行、预览文本、发件人身份、个性化设置或邮件渲染效果
- 选择营销活动邮件、生命周期自动化邮件或事务性邮件的类型
- 规划新用户引导、用户留存、用户重激活、催款或产品更新邮件方案
- 检查Loops配置是否符合最佳实践要求
纯实现类任务（如“通过Loops API发送事件”或“在Next.js中对接事务性邮件”）请勿默认使用此Skill，此类任务请使用 Skill。
apiWorking Style
工作流程
When this skill is active:
- Identify the primary problem:
- deliverability
- audience/consent
- content/design
- email type/program strategy
- Loops-specific operational behavior
- Load only the relevant reference files.
- Give generic email best-practice guidance first.
- Add Loops-specific caveats, defaults, and product behavior where relevant.
- If the user is drifting into cold email or promotional use of transactional email, call that out directly and steer toward opt-in lifecycle or marketing sends instead.
激活此Skill时：
- 确定核心问题类型：
- 邮件送达率
- 受众/用户同意机制
- 内容/设计
- 邮件类型/运营策略
- Loops专属操作行为
- 仅加载相关参考文件
- 首先提供通用邮件最佳实践指导
- 在相关场景下补充Loops专属注意事项、默认设置及产品特性
- 若用户倾向于冷邮件或滥用事务性邮件进行推广，需直接指出并引导其转向基于用户订阅的生命周期邮件或营销邮件
Category Routing
分类指引
- Deliverability, sender reputation, domain setup, warming, inbox placement, Postmaster, BIMI, or large-list sends:
Read
references/deliverability.md - Consent, list hygiene, double opt-in, preference centers, mailing lists, segmentation, or stale audiences:
Read
references/audience-and-consent.md - Subject lines, preview text, sender fields, personalization, styling, themes, dark mode, or template/design review:
Read
references/content-and-design.md - Campaign vs loop vs transactional, onboarding/lifecycle sequencing, product updates, or email KPI framing:
Read
references/email-types-and-program-strategy.md - Loops-specific behavior such as , transactional tracking differences, attachments, webhooks, or multi-domain constraints: Read
addToAudiencereferences/loops-operational-caveats.md
- 涉及邮件送达率、发件人信誉、域名配置、域名预热、收件箱投递位置、Postmaster、BIMI或大规模邮件发送：
阅读
references/deliverability.md - 涉及用户同意、邮件列表清洁度、双重确认订阅、偏好设置中心、邮件列表、用户细分或沉睡受众：
阅读
references/audience-and-consent.md - 涉及主题行、预览文本、发件人字段、个性化设置、样式、主题、深色模式或模板/设计审核：
阅读
references/content-and-design.md - 涉及营销活动邮件vs循环邮件vs事务性邮件、新用户引导/生命周期邮件序列、产品更新或邮件KPI设定：
阅读
references/email-types-and-program-strategy.md - 涉及Loops专属行为（如、事务性邮件追踪差异、附件、webhooks或多域名限制）： 阅读
addToAudiencereferences/loops-operational-caveats.md
Output Checklist
输出检查清单
Aim to leave the user with:
- the most likely root cause or opportunity
- a concrete set of recommended changes
- any Loops-specific caveats that materially change the recommendation
- the metrics or signals that should be watched after the change
When relevant, explicitly separate:
- immediate fixes
- medium-term program improvements
- things that are out of scope or risky to infer from limited evidence
需为用户提供以下内容：
- 最可能的根本原因或优化机会
- 具体的建议修改方案
- 任何会实质性改变建议的Loops专属注意事项
- 修改后需关注的指标或信号
必要时需明确区分：
- 即时修复措施
- 中期运营方案优化
- 超出范围或基于有限证据难以推断的内容