lifecycle-messaging
Installation
SKILL.md
Lifecycle messaging — deliverable, consented, compliant
Messages that don't arrive (poor deliverability) or that arrive without consent (TCPA/ CAN-SPAM violations) are both fatal for an SMB product. This skill makes both correct by construction. Design the consent + deliverability posture before the first send.
1. Transactional vs marketing — split them
Decide per message which bucket it is; they have different rules and should use different sending identities (often different subdomains / providers):
| Transactional | Marketing / lifecycle | |
|---|---|---|
| Examples | receipt, booking confirm/reminder, password reset | win-back, promo, newsletter, nurture step |
| Consent | implied by the transaction | explicit opt-in required |
| Unsubscribe | not required (but honor STOP) | required, one-click, honored fast |
| Sending domain | txn. subdomain |
mail./news. subdomain |