What problem does it solve? Writing Zod validation code without guidance leads to unsafe schemas, unhandled parse exceptions, cryptic error messages, and duplicated type definitions that drift out of sync with validation logic. ## Core Features & Use Cases - Prioritized Rule Set: 43 rules across 8 categories (schema definition, parsing, type inference, error handling, object schemas, composition, refinements, performance), each ranked by impact from CRITICAL to LOW-MEDIUM. - Incorrect vs. Correct Examples: Every rule shows real TypeScript code comparing the wrong approach with the right one, plus impact explanations and guidance on when not to apply the pattern. - Use Case: When building a NestJS API endpoint that accepts user registration data, apply the safeParse, custom error messages, and boundary validation rules to reject invalid input with actionable feedback instead of crashing the server. ## Quick Start Ask the agent to review your Zod schema file and apply the validation best practices, such as converting parse() calls to safeParse() for user input.