What problem does it solve? Migrating an existing codebase to oRPC is error-prone because pretrained knowledge of oRPC describes v1 and is often wrong for v2, and the v1-to-v2 upgrade hides silent behavior changes that never surface at compile time. This Skill provides a verified, step-by-step playbook for both migrations so each change can be typechecked and tested incrementally. ## Core Features & Use Cases - tRPC to oRPC migration: Choose between incremental wrapping of an existing tRPC router via @orpc/trpc (toORPCRouter, toTRPCMeta) or a full rewrite using a complete tRPC-to-oRPC concept mapping table. - oRPC v1 to v2 upgrade: Ordered steps covering package renames (e.g., @orpc/react-query to @orpc/tanstack-query), hard breaking changes with no aliases, silent behavior changes (wire format, middleware deduplication, batch plugin filter), and deprecated alias sweeps. - Docs-first retrieval: Directs every import path, builder method, and option name to authoritative pages at orpc.dev and v1.orpc.dev instead of relying on memory. - Use Case: You inherit an Express app with a large tRPC router that must keep shipping. Use this Skill to wrap the router with toORPCRouter, then rewrite leaf routers to native oRPC one at a time while typechecking after each step. ## Quick Start Migrate my tRPC router in src/server to oRPC v2 using the incremental wrapping approach and verify each step with typecheck.