orpc-contract-creation

Define oRPC contracts with Zod schemas in packages/shared for server-client sync.

1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/CatOfJupit3r/ultimate-starter --skill orpc-contract-creation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orpc-contract-creation
Source: https://github.com/CatOfJupit3r/ultimate-starter/tree/main/.github/skills/orpc-contract-creation
Command: npx skills add https://github.com/CatOfJupit3r/ultimate-starter --skill orpc-contract-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain a single source of truth for oRPC contracts to ensure server and client stay in sync via centralized, well-typed contracts.

Core Features & Use Cases

  • Contract generation: Define new namespaces and procedures by following a standard template and example.
  • Type-safe governance: Enforce Zod schemas and OC router patterns across the monorepo.
  • Real-world usage: Deploy new endpoints with confidence, knowing client and server contracts align.

Quick Start

Create a new contract file in packages/shared/src/contract for a chosen namespace following the complete-contract.ts example.

Frequently Asked Questions about orpc-contract-creation

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

FAQPage Schema
How do I create type-safe oRPC contracts to sync server and client?▼

Define TypeScript interfaces and Zod schemas in a central file within packages/shared to create type-safe oRPC contracts, establishing a single source of truth for server-client communication.

What is the best way to structure shared API contracts in a monorepo?▼

The best way to structure shared API contracts is to centralize them in packages/shared/src/contract, using an OC router and Zod schemas to enforce type-safe governance across your monorepo.

How does using Zod schemas with oRPC improve API design?▼

Using Zod schemas with oRPC improves API design by enforcing runtime validation and static type safety, ensuring server and client contract definitions remain strictly aligned across packages.

Do I need TypeScript to implement shared oRPC contracts?▼

Yes, you need TypeScript to implement shared oRPC contracts, as the workflow relies on TypeScript types, the OC router pattern, and Zod schemas to validate procedures and maintain consistency.

How do I validate oRPC contract types after adding new endpoints?▼

You validate oRPC contract types after adding new endpoints by running pnpm run check-types, ensuring that your newly defined namespaces and procedures align across the server and client.