Skip to main content
All skills

API Design

REST, tRPC, webhooks and MCP tool surfaces — designed around the caller rather than the schema.

How I use it

  1. Idempotent webhook receivers

    Payment and catalogue webhooks keyed on event identity rather than arrival. Providers guarantee at-least-once delivery, which makes duplicates the receiver’s job.

  2. Typed contracts end to end

    tRPC and Hono where both ends are mine, so a changed shape is a compile error rather than a support ticket.

  3. Validation at the trust boundary

    Schema validation on everything crossing it. "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.

Get in touch