What problem does it solve?
This Skill solves inconsistent and error-prone oRPC API implementations by enforcing a strict contract-first workflow, consistent routing/resource naming, and standardized schema and error handling conventions.
Core Features & Use Cases
- Contract-first development guardrails: Enforces singular API path/resource naming and a clear pattern for defining Zod schemas before building oRPC contracts.
- Production-ready server patterns: Guides implementers to use oRPC server utilities and standard ORPCError codes for predictable failures.
- React Query integration guidance: Shows how to create an RPC contract client and wire it into React Query for type-safe querying.
- Schema and validation constraints: Requires consistent use of .describe for strings, z.coerce.date for dates, nullish optional handling, and correct File typing with z.instanceof(File).
Quick Start
Ask an engineer to implement your new oRPC endpoints by following the Skill rules for contract definition, server handler implementation, and React Query client usage.