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.