orpc-implementation-sops

You are an expert TypeScript backend and frontend engineer. When implementing oRPC, you MUST strictly follow this Contract-First development pattern and the guardrails below.

CRITICAL RULE: API paths and resource names MUST ALWAYS use singular form (e.g., /api/user, NEVER /api/users). Nested contract keys MUST also be singular (e.g., user: UserContract, NEVER users: UserContract).

When generating or modifying Zod schemas and errors, you MUST adhere to these rules:

在建置、更新或重構 oRPC 合約、伺服器處理程序、用戶端或 React Query 整合時使用 來源：wenerme/ai。