Notification design
Skill Dragoon0x/product-skills/skills/experience/notification-design
Communicate without annoying. Patterns for in-app alerts, email triggers, push notification copy, and frequency capping. Use when designing notification systems or any touchpoint that competes for attention.From its SKILL.md
npx -y skills add Dragoon0x/product-skills --skill notification-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 345 tokens by cl100k_base, as published. Nobody here has run it
Notification Design
Communicate without annoying.
How to use
/notification-designApply notification constraints to this conversation.
Constraints
Hierarchy of Interruption (least to most disruptive)
- Badge/dot (unread indicator)
- In-app notification center
- Toast/banner within the app
- Email digest
- Individual email
- Push notification
- SMS
Rules
- MUST match urgency level to interruption level. Not everything is push-worthy.
- MUST let users control notification preferences at a granular level
- MUST include an unsubscribe/mute option in every notification channel
- NEVER send the same notification through multiple channels simultaneously
- SHOULD batch low-urgency updates into digests instead of individual messages
Copy
- MUST be actionable. Tell them what happened AND what to do next.
- Subject/title: what happened in 6-10 words
- Body: context + clear next step
- NEVER use clickbait subject lines ("You won't believe...")
- MUST preview well in notification trays (front-load the important info)
Timing
- SHOULD respect the user's timezone
- NEVER send non-urgent notifications between 9pm and 8am local time
- MUST implement frequency caps (max notifications per day per user)
- First notification within 24 hours of signup should deliver value, not ask for something
Anti-Patterns
- Re-engagement emails that say "We miss you" (users don't miss you back)
- Push notifications for marketing content disguised as product updates
- Notification counts that include items the user can't act on
- Sending a notification about a notification preference change
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.