What problem does it solve? Writing Zod validation code without established patterns leads to unsafe type handling, unhandled parse exceptions, cryptic error messages, and duplicated schemas that drift out of sync across a TypeScript codebase. ## Core Features & Use Cases - Schema Definition Guidance: 43 rules across 8 prioritized categories covering primitives, enums, coercion, string validations, and avoiding z.any() in favor of z.unknown(). - Parsing & Error Handling Patterns: Correct use of safeParse(), parseAsync() for async refinements, flatten() for form errors, and custom or internationalized error messages. - Composition & Performance: Rules for pick/omit/partial/extend, discriminated unions, recursive schemas with z.lazy(), schema caching, and Zod Mini for bundle-sensitive apps. - Use Case: When building an API endpoint that accepts user registration data, apply these rules to define a strict schema with coercion, validate with safeParse at the boundary, and return flattened field-level errors to the client. ## Quick Start Ask the agent to review or write a Zod schema for your form or API payload following the zod best practices rules.