orpc-trpc

Integrate oRPC with tRPC to generate OpenAPI specs and use OpenAPIHandler.

8|Updated Mar 3, 2026

Search Tags:#OpenAPI #API development #tRPC #oRPC #middleware integration

Ready to run

npx skills add https://github.com/ali-master/skills --skill orpc-trpc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orpc-trpc
Source: https://github.com/ali-master/skills/tree/main/skills/orpc-trpc
Command: npx skills add https://github.com/ali-master/skills --skill orpc-trpc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @orpc/trpc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides an easy way to incorporate oRPC features into existing tRPC applications, enabling developers to leverage both frameworks' strengths without significant overhead.

Core Features & Use Cases

oRPC Integration: Migrate a tRPC router to an oRPC router to gain access to oRPC's OpenAPI specs and OpenAPIHandler.
OpenAPI Support: Generate OpenAPI specifications for tRPC services and use them with various tools.
Request Handling: Customize request handling through interceptors for additional functionality like CORS handling and error logging.
Use Case: If you are using tRPC and want to benefit from oRPC's OpenAPI support without rebuilding your service from scratch.

Quick Start

Integrate oRPC with your tRPC application by installing @orpc/trpc and converting your tRPC router to an oRPC router.

Frequently Asked Questions about orpc-trpc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add OpenAPI spec generation to an existing tRPC application?▼

Yes, you can generate OpenAPI specifications for your existing tRPC services by integrating oRPC. This approach bridges tRPC routers to oRPC, allowing you to leverage OpenAPIHandler and various OpenAPI tools without discarding your current tRPC setup.

What is the process to migrate a tRPC router to an oRPC router?▼

Migrating a tRPC router to an oRPC router involves installing the @orpc/trpc dependency and using it as a bridge. This conversion process allows you to leverage oRPC's advanced router capabilities and OpenAPI specs while maintaining your existing tRPC application structure.

Can I use oRPC interceptors for CORS handling and error logging in my tRPC API?▼

Yes, integrating oRPC with your tRPC application allows you to customize request handling through interceptors. You can use these interceptors to implement additional functionality such as CORS handling and error logging within your API request workflow.

Does integrating oRPC with tRPC require rebuilding my current API service?▼

No, integrating oRPC with tRPC does not require rebuilding your current API service. The integration is specifically designed for existing tRPC applications to enhance them with oRPC features, providing a seamless bridge for OpenAPI support without significant overhead.

Why use oRPC OpenAPIHandler instead of standard tRPC for API development?▼

Using oRPC's OpenAPIHandler provides advanced router capabilities and OpenAPI spec generation that standard tRPC lacks. It enables you to generate OpenAPI specifications for your services and utilize them with various tools, enhancing interoperability and documentation.

What are the limitations of using oRPC and tRPC integration for API services?▼

The oRPC and tRPC integration is specifically designed as a bridge for existing tRPC applications to gain OpenAPI support. While it provides advanced router capabilities and interceptor customization, its primary limitation is that it serves as a migration bridge rather than a standalone replacement framework.