knock-migrate-to-knock
Investigate existing messaging infrastructure in a codebase and recommend how it maps to Knock. Use when migrating from Braze, Courier, Customer.io, Iterable, SendGrid, or custom notification code, or when planning a move to Knock.
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/knock-migrate-to-knock/SKILL.md
- skills/knock-migrate-to-knock/rules/inventory-existing-messaging.md
- skills/knock-migrate-to-knock/rules/map-concepts-to-knock.md
- skills/knock-migrate-to-knock/rules/migration-plan.md
Every link opens the file at its source, pinned to the revision this page describes.