notification-best-practices

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Notification best practices skill

通知系统最佳实践 Skill

This skill provides comprehensive guidelines and best practices for designing, writing, and implementing effective notification systems across all channels.

本Skill提供了跨所有渠道设计、编写及实现高效通知系统的综合指南与最佳实践。

Overview

概述

The notification best practices skill includes six detailed rule sets covering:

Channel-specific notification guidelines - Specifications for email, push, SMS, in-app, and chat notifications
Notification copy best practices - Core principles for writing effective notification copy
Notification system implementation rules - Technical implementation guidelines including timing, preferences, error handling, and compliance
Notification template examples - Ready-to-use templates for common notification use cases
Transactional email best practices - Deliverability, templates, localization, and dynamic content for transactional emails
Welcome email best practices - Guidelines for crafting effective SaaS welcome emails

通知系统最佳实践Skill包含六大详细规则集，涵盖：

渠道专属通知指南 - 邮件、推送、短信、应用内及聊天通知的规范要求
通知文案最佳实践 - 撰写高效通知文案的核心原则
通知系统实现规则 - 包含时机选择、偏好设置、错误处理及合规性的技术实现指南
通知模板示例 - 适用于常见通知场景的即用型模板
事务性邮件最佳实践 - 事务性邮件的送达率、模板、本地化及动态内容相关指南
欢迎邮件最佳实践 - 打造高效SaaS欢迎邮件的指南

How to use this skill

如何使用本Skill

For writing notifications

撰写通知文案时

When you need to write notification copy:

Start with copy best practices (
```
rules/notification-copy-best-practices.md
```
)
- Follow core principles: be specific, include context, use active voice
- Choose the right tone and structure for your notification type
Check channel-specific guidelines (
```
rules/channel-specific-notifications-guidelines.md
```
)
- Verify character limits for your target channel
- Follow channel-specific formatting requirements
- Ensure your message fits the channel's constraints
Reference templates (
```
rules/notification-template-examples.md
```
)
- Find similar use cases to your notification
- Adapt template structure and variables
- Use provided examples as starting points

当你需要撰写通知文案时：

从文案最佳实践入手 (
```
rules/notification-copy-best-practices.md
```
)
- 遵循核心原则：具体明确、包含上下文、使用主动语态
- 根据通知类型选择合适的语气与结构
查阅渠道专属指南 (
```
rules/channel-specific-notifications-guidelines.md
```
)
- 确认目标渠道的字符限制
- 遵循渠道专属的格式要求
- 确保消息符合渠道的约束条件
参考模板 (
```
rules/notification-template-examples.md
```
)
- 找到与你的通知场景相似的案例
- 调整模板结构与变量
- 以提供的示例为起点进行创作

For email notifications

处理邮件通知时

When working with email notifications:

Review transactional email best practices (
```
rules/transactional-email-best-practices.md
```
)
- Follow deliverability guidelines
- Use componentized templates and partials
- Implement proper localization
For welcome emails specifically (
```
rules/welcome-email-best-practices.md
```
)
- Choose the right pattern for your product
- Follow timing best practices
- Focus on value and clear CTAs

当处理邮件通知时：

查阅事务性邮件最佳实践 (
```
rules/transactional-email-best-practices.md
```
)
- 遵循送达率相关指南
- 使用组件化模板与局部文件
- 实现恰当的本地化设置
针对欢迎邮件 (
```
rules/welcome-email-best-practices.md
```
)
- 为你的产品选择合适的模式
- 遵循时机选择的最佳实践
- 聚焦价值传递与清晰的CTA

For system implementation

实现通知系统时

When implementing a notification system:

Follow system implementation rules (
```
rules/notification-system-implementation.md
```
)
- Understand channel selection criteria
- Implement proper timing and frequency controls
- Set up preference management
- Handle errors and retries correctly
- Ensure compliance with regulations
Use channel-specific guidelines for technical constraints
- Character limits
- Formatting requirements
- Delivery specifications

当实现通知系统时：

遵循系统实现规则 (
```
rules/notification-system-implementation.md
```
)
- 理解渠道选择标准
- 实现恰当的时机与频率控制
- 搭建偏好管理功能
- 正确处理错误与重试逻辑
- 确保符合法规要求
参考渠道专属指南了解技术约束
- 字符限制
- 格式要求
- 送达规范

Rule files reference

规则文件参考

rules/channel-specific-notifications-guidelines.md

- Channel specifications and constraints

rules/notification-copy-best-practices.md

- Writing principles and guidelines

rules/notification-system-implementation.md

- Technical implementation rules

```
rules/notification-template-examples.md
```
- Template library with examples

rules/transactional-email-best-practices.md

- Email-specific best practices

```
rules/welcome-email-best-practices.md
```
- Welcome email patterns and guidelines

rules/channel-specific-notifications-guidelines.md

- 渠道规范与约束

rules/notification-copy-best-practices.md

- 文案撰写原则与指南

rules/notification-system-implementation.md

- 技术实现规则

```
rules/notification-template-examples.md
```
- 示例模板库

rules/transactional-email-best-practices.md

- 邮件专属最佳实践

```
rules/welcome-email-best-practices.md
```
- 欢迎邮件模式与指南

Quick reference

快速参考

Channel selection

渠道选择

Email: Persistent reference, detailed content, non-time-critical
Push: Time-sensitive, requires app return, urgent actions
SMS: Guaranteed delivery, authentication, extreme time-criticality
In-app: User active in product, can wait until next session
Chat: Team collaboration, immediate visibility needed

邮件：持久化参考内容，适合详细信息，非时间敏感场景
推送：时间敏感，需要用户返回应用，适用于紧急操作
短信：送达有保障，用于身份验证，极端时间敏感场景
应用内：用户正活跃于产品内，可等待至下次会话
聊天：团队协作场景，需要即时可见

Copy principles

文案原则

Be specific and actionable
Include maximum context
Use active voice
Maintain consistent terminology
Format for each channel

具体明确且具备可操作性
包含足够的上下文信息
使用主动语态
保持术语一致
针对各渠道进行格式调整

Common patterns

常见模式

Transactional: Confirm what happened, include identifiers, provide next steps
System: Translate technical events to user impact, offer actionable steps
Lifecycle: Balance value with frequency, use social proof appropriately
Promotional: Lead with benefits, make offers specific and time-bound

事务性：确认已发生的事件，包含标识符，提供后续步骤
系统类：将技术事件转化为对用户的影响说明，提供可操作步骤
生命周期类：平衡价值传递与发送频率，合理使用社交证明
营销类：以利益点为核心，提供具体且有时间限制的优惠

Best practices summary

最佳实践总结

Always provide context - Users need enough information to decide whether to act
Respect channel constraints - Follow character limits and formatting requirements
Use appropriate timing - Consider immediate vs. batched vs. scheduled sends
Implement preferences - Give users control over notification types and channels
Test thoroughly - Verify across channels, devices, and with real data
Monitor and optimize - Track delivery, engagement, and user satisfaction metrics

始终提供上下文 - 用户需要足够信息来决定是否采取行动
尊重渠道约束 - 遵循字符限制与格式要求
选择合适的时机 - 考虑即时发送、批量发送或定时发送
实现偏好设置 - 让用户能够控制通知类型与接收渠道
全面测试 - 跨渠道、设备及真实数据进行验证
监控与优化 - 跟踪送达率、参与度及用户满意度指标