loops-email-sending-best-practices

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Email 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.

此技能可帮助审核和规划健康的邮件运营方案。默认情况下它是通用型的，但会针对性地偏向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

loops-api

skill for those.

当任务聚焦于邮件质量、风险或策略，而非底层API实现时，可使用此技能。

典型使用场景：

诊断收件箱投放效果差或发件人声誉问题
审核用户许可流程、双重确认订阅（double opt-in）、邮件列表清洁或退订机制
优化主题行、预览文本、发件人身份、个性化设置或邮件渲染效果
在营销活动邮件、全生命周期自动化邮件与事务性邮件之间做选择
规划新用户引导、用户留存、用户重激活、催款或产品更新邮件方案
审核Loops配置，找出与最佳实践的差距

对于纯实现类任务，例如“通过Loops API发送事件”或“在Next.js中搭建事务性邮件功能”，请勿默认使用此技能，此类任务请使用

loops-api

技能。

Working 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.

激活此技能时：

确定核心问题：
- 邮件送达率（deliverability）
- 用户群体/用户许可
- 内容/设计
- 邮件类型/运营策略
- 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
```
addToAudience
```
, transactional tracking differences, attachments, webhooks, or multi-domain constraints: Read
```
references/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专属行为，例如
```
addToAudience
```
、事务性邮件跟踪差异、附件、webhook或多域名限制：阅读
```
references/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专属注意事项
更改后需要关注的指标或信号