What problem does it solve? Defining consistent runtime validation across API boundaries, environment variables, and background job payloads is error-prone when done ad hoc. This Skill provides standardized Zod schema patterns for the DropFlow monorepo so every input is validated at the boundary with shared, type-safe definitions. ## Core Features & Use Cases - Input Schema + DTO Pattern: Define paired schemas where CreateOrderInput validates client data and OrderDTO shapes API responses, with inferred TypeScript types exported from packages/types. - Indian Localization Conventions: Built-in patterns for +91 phone numbers, 6-digit PIN codes, GSTIN format, and integer-paise money handling with dual formatted responses. - Environment & Worker Payload Validation: Parse process.env with a strict Zod schema and validate worker job payloads (orders, invoices) before processing. - Use Case: When adding a new API route that accepts order creation requests, use this Skill to generate the input schema, DTO, and inferred types following the established packages/types conventions. ## Quick Start Create a Zod input schema and DTO for a new shipment tracking endpoint following the DropFlow patterns in packages/types.