zodlisted
Install: claude install-skill ValentinNikolaev/agent-skills
# Zod Schemas and Parsing
Implement validation at a named trust boundary using the project's installed Zod version. Selected boundary-validation, inference, and migration topics adapt [secondsky's Zod skill](https://github.com/secondsky/claude-skills/blob/88378361314f558fb719aec0af9fd898ab36f0b2/plugins/zod/skills/zod/SKILL.md), under the bundled `LICENSE.secondsky-claude-skills`. Examples here are rewritten and do not inherit its claim that every upstream example is verified.
## Route precisely
- Use to create or change Zod schemas, parsing, coercion, transforms, refinements, codecs, or validation-error mapping for API payloads, forms, files, configuration, or external responses.
- Use `code-review` for a read-only diff review, `vet-dependency` to decide whether to adopt Zod, `api-and-interface-design` for an undecided public contract, and `typescript-type-design` for pure type-level mechanisms.
- Use `deprecation-and-migration` for a live contract rollout. A Zod upgrade can change accepted data, defaults, serialized output, and clients; a library upgrade alone does not authorize those changes.
## Establish version and boundary
Read repository instructions, package/lock metadata, actual import path (`zod`, `zod/v4`, `zod/mini`, or core), compiler support, and local parsing/error conventions. Read installed declarations or version-matched official docs before using APIs. Do not infer a major version from the presence of `z.codec`: it arrived after the first Zod 4 release