api-design

Design production-grade HTTP APIs by composing thin handlers that map HTTP requests directly to domain logic. This approach enforces ORPC server framework usage, Zod input validation, and deterministic routing to keep boundaries clean.

Handle error mapping in HTTP APIs by implementing a standardized error envelope. This ensures consistent error responses across typical service boundaries while keeping your HTTP handlers focused on domain logic translation.

Set up routing with dependency injection by creating modular route factories. This pattern allows you to build scalable API routers where handlers receive their dependencies injected rather than instantiating them directly.

Yes, you can use Zod for input validation in HTTP API design. The skill enforces Zod-based input validation to ensure deterministic routing and reliable mapping of HTTP requests to your underlying domain logic.

Add health and readiness endpoints to your API as part of standard operational patterns. These endpoints work alongside consistent error envelopes, CORS, and idempotency middleware to ensure service reliability.

Yes, this API design approach works with and enforces the ORPC server framework. It leverages ORPC for deterministic routing, Zod-based input validation, and consistent error mapping across typical service boundaries.