What problem does it solve? Writing Zod schemas without established patterns leads to type-unsafe validation, unhandled parse exceptions, cryptic error messages, and duplicated schema definitions that drift out of sync across a TypeScript codebase. ## Core Features & Use Cases - 43 Prioritized Rules Across 8 Categories: Covers schema definition, parsing, type inference, error handling, object schemas, composition, refinements, and performance, each ranked by impact from CRITICAL to LOW-MEDIUM. - Incorrect vs. Correct Code Examples: Every rule includes real-world TypeScript examples showing the wrong approach and the recommended fix with impact explanations. - Use Case: When building an API endpoint that accepts user registration data, apply the safeParse, custom error messages, and boundary validation rules to return all field errors at once instead of crashing on invalid input. ## Quick Start Ask the AI to review your Zod schema file and apply the validation best practices, starting with the critical parsing and schema definition rules.
