backend-trpc-openapi

REST endpoints from tRPC routers are generated using the trpc-to-openapi package, which converts your type-safe tRPC procedures into standard REST endpoints. Install trpc-to-openapi, annotate your routers with metadata, and the package automatically produces both the endpoints and OpenAPI documentation. This enables third-party consumption and cross-language interoperability without manually defining REST contracts.

Yes. OpenAPI documentation is auto-generated from your tRPC routers using trpc-to-openapi, which produces both a machine-readable OpenAPI spec and an interactive Swagger UI. This standardized documentation makes your API accessible to third-party developers, mobile apps, and tools that consume REST APIs, without duplicating your type definitions.

You need tRPC v11 or later and Zod for schema validation. The trpc-to-openapi package handles the conversion from tRPC routers to REST endpoints and OpenAPI specs. These are the core technical requirements; no additional dependencies are listed as hard constraints for the base workflow.

REST endpoints are served via an Express-compatible middleware generated by trpc-to-openapi. After generating the middleware from your annotated tRPC routers, mount it on your Express app to expose REST routes. This allows existing tRPC clients to coexist with REST consumers on the same backend.

Yes. This Skill is designed for internal tRPC apps that require REST interfaces for third-party consumption, mobile clients, or public API access. It eliminates the need to maintain separate REST adapters by deriving REST endpoints and OpenAPI specs directly from your type-safe tRPC definitions.