zodlisted

# Zod ## 1. Establish the version and boundary Read the consuming package's resolved Zod version, imports, TypeScript settings, existing schemas, adapters, and nearest tests. Account for multiple installed versions. Match the project's import style and preserve its validation layer. Use strict TypeScript checking; investigate incompatible adapters before changing their schema types. This skill targets Zod 4 Classic, with **4.6.5** as its documentation baseline; not every 4.x API is interchangeable. | Task branch | Read before implementing | | --- | --- | | Zod 3 maintenance, major upgrade, or changing 4.x behavior | [migration.md](./migration.md) | | Forms, query strings, environment variables, defaults, custom checks, errors | [boundaries.md](./boundaries.md) | | Codecs, JSON Schema, metadata, Mini, library adapters, performance | [interop.md](./interop.md) | | Unclear API availability or disputed behavior | Installed types and the [official documentation](https://zod.dev/api) for the resolved version | Identify the raw representation, accepted values, parsed output, failure consumer, and synchronous or asynchronous execution. Finish with those five decisions explicit for each changed boundary. ## 2. Encode the contract Reuse existing domain schemas where their accepted values and unknown-key policy match. Infer application-owned types from schemas; for externally owned contracts, check compatibility without erasing the concrete schema's inferred type. | Contract deci