SuperAPI AI Directory

orpc

Coding & development

View repository

Updated 10-16 00:00

About this skill

oRPC

Use this skill to build and review oRPC code against the official documentation.

What it is: oRPC (OpenAPI Remote Procedure Call) defines and calls remote/local procedures through an end-to-end type-safe API that also adheres to the OpenAPI spec. Official docs: https://orpc.dev. Repo: https://github.com/unnoq/orpc.

How to use the references

oRPC ships LLM-friendly docs, not a code skill. Every reference below is a Markdown rendering of a docs page (.md suffix). Fetch only the pages relevant to the task.

Workflow

  1. Identify the surface: contract, router/procedure, handler (RPC vs OpenAPI), client (server-side vs link), or integration.
  2. Read only the relevant reference page(s) below — append .md, don't guess APIs.
  3. Prefer contract-first when client and server are separate packages; co-located code can use the router directly.
  4. Match the project's existing handler and serializer choices before introducing new ones.
  5. Validate type-safety end to end; throw Error instances, never literals.

Core Concepts

Contract First

Handlers

Clients

Adapters (server framework hosting)

Plugins

Integrations

Best Practices

Advanced

Guardrails

  • Don't invent API surface — fetch the relevant .md page; oRPC's API is versioned and changes between majors.
  • Throw Error instances, never literal values (oRPC error flow + type inference depend on it).
  • Keep contract and implementation types in sync; let the contract drive client types.
  • Respect the project's existing handler/serializer/adapter choices instead of mixing them.