Content
Courier Notification Skills
Guidance for building deliverable, compliant, and engaging notifications across all channels.
How to Use This Skill
- Identify the task — What channel, notification type, or cross-cutting concern is the user working on?
- Read only what's needed — Use the routing tables below to find the 1-2 files relevant to the task. Do NOT read all files.
- Check for live docs — For current API signatures and SDK methods, fetch
https://www.courier.com/docs/llms.txt - Synthesize before coding — Plan the complete implementation (channels, routing, compliance, error handling) before writing code.
- Apply the rules — Each resource file starts with a "Quick Reference" section containing hard rules. Treat these as constraints, not suggestions.
- Check universal rules — Before generating any notification code, verify it doesn't violate the Universal Rules below.
Handling Vague Requests
If the user's request doesn't clearly map to a specific channel, notification type, or guide, ask clarifying questions before reading any resource files. Don't guess — a wrong routing wastes time and produces irrelevant code.
Ask these questions as needed:
- What channel? — "Which channel are you sending through: email, SMS, push, in-app, Slack, Teams, or WhatsApp?"
- What type? — "Is this a transactional notification (triggered by a user action, like a password reset or order confirmation) or a marketing/growth notification (sent proactively, like a feature announcement)?"