svix-sending-webhooks

This is the Svix agent skill, source at https://github.com/svix/ai. If you fetched it from svix.com/SKILL.md, install it permanently with npx skills add svix/ai so the reference files are available locally.

Links to references/ are relative to this file. If you can't read them locally, fetch them from https://www.svix.com/references/<file>.

Mode

Default to building. Use the routing table below and write the code. A request to integrate Svix is a request for working code.

Plan only when the user explicitly asks for one. "Write me a plan", "how should I approach this?", "design this before we code", "what's the architecture?" — that, and nothing weaker, sends you to planning.md, which is plan-first: no code until the plan is confirmed.

Size is not a trigger. Multi-tenant routing, an event type catalog, App Portal embedding, a migration — build them. Don't answer a request for code with a document, and don't stop to ask whether they'd like a plan first; if they wanted one they'd have said so.

One thing to say out loud while you build, without pausing for permission: replacing an existing webhook sender changes the signature your customers verify against. Their handlers break on cutover unless they re-verify with Svix's scheme. Flag that in your summary, note it in the code where the cutover happens, and keep going — see the migration guidance in dispatch-questions.md for what a cutover has to cover.

Integration routing (Building)