All skills
API Design
REST, tRPC, webhooks and MCP tool surfaces — designed around the caller rather than the schema.
How I use it
Webhooks delivered twice
Payment and catalogue webhooks handled idempotently, keyed on event identity rather than arrival. Providers guarantee at-least-once delivery, which means duplicates are the receiver’s job.
Contracts discovered at runtime
tRPC and Hono where both ends are mine, so a changed shape is a compile error rather than a support ticket.
Validation assumed at the boundary
Schema validation on everything crossing the trust line. "Only our form calls this" stops being true the first time anything else does.
What I use
- tRPC
- Hono
- Zod
- REST
- Model Context Protocol
Related skills
Want the detail behind any of this?
I can walk through any of it in as much depth as you want.