From ccds-core
Cross-channel user notifications — push, email, SMS, in-app, webhook, batching / throttling / quiet-hours, preferences, deliverability. Auto-invoked when designing notification flows, investigating open-rate drops, or implementing preferences UI.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ccds-core:common-notificationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Notifications are the fastest way to ruin user trust: too many and users silence
Notifications are the fastest way to ruin user trust: too many and users silence you, too few and they don't know you exist, wrong channel and they miss what matters.
transactional_order), per-channel toggles, a working
global unsubscribe — and default-on only where legally permitted.| Message type | Primary channel | Backup | Default opt-in | Quiet hours |
|---|---|---|---|---|
| Security alert (login, password change) | email + push | SMS | yes (mandatory) | ignored |
| Transactional (order, receipt, reset) | push | yes | ignored | |
| Action needed (approval, mention, reply) | push | yes | digested | |
| Lifecycle / engagement | in-app | opt-in | respected | |
| Marketing / broadcast | — | opt-in only | respected + send-time optimized | |
| System status (incident, maintenance) | in-app banner | yes | respected unless critical |
Related: common-privacy (consent and opt-out mechanics), common-i18n (template
localization), common-product-analytics (attribution events), common-a11y
(accessible email HTML) · pulled by any domain agent · output/ADR format:
playbook-conventions
npx claudepluginhub ggrace519/claude-code-dev-studio --plugin ccds-coreProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.