zod-validation
Zod v4 schema validation for TypeScript. Covers primitives, string formats, objects, arrays, unions, coercion, transforms, refinements, parsing, type inference, error customization, JSON Schema, file validation, and metadata. Use when writing schemas, validating input, parsing data, inferring types, or converting schemas with Zod.
What this skill does
# Zod Validation (v4)
Type-safe schema validation for TypeScript. Zod v4 introduces top-level format functions, `z.stringbool()`, `z.iso.*` date formats, `z.overwrite()` transforms, `z.file()`, `z.toJSONSchema()`, getter-based recursive types, `.meta()`, and the unified `error` function.
**Package:** `zod` (also `zod/mini` for smaller bundles)
## Quick Reference
| Pattern | Usage |
| ------------------------------------------ | ---------------------------------------------- |
| `z.object({ ... })` | Define object schemas |
| `z.string()`, `z.number()` | Primitive types |
| `z.email()`, `z.url()`, `z.uuid()` | Top-level string formats (v4) |
| `z.iso.date()`, `z.iso.datetime()` | ISO date/time formats (v4) |
| `z.int()`, `z.float32()`, `z.int32()` | Fixed-width number formats (v4) |
| `z.templateLiteral([...])` | Template literal type validation (v4) |
| `z.enum([...])`, `z.literal()` | Enums and literals |
| `z.union([...])`, `z.discriminatedUnion()` | Union types |
| `z.array()`, `z.tuple()` | Array and tuple types |
| `z.record()`, `z.map()` | Key-value collections |
| `.optional()`, `.nullable()` | Optional and nullable modifiers |
| `.default()`, `.catch()` | Default values and fallbacks |
| `.prefault()` | Pre-parse default (parsed through schema, v4) |
| `z.coerce.number()` | Type coercion before validation |
| `z.stringbool()` | String-to-boolean parsing (v4) |
| `.transform()`, `.overwrite()` | Output transforms |
| `z.pipe()` | Chain schemas (output feeds next input) |
| `.refine()`, `.superRefine()` | Custom validation logic |
| `.parse()`, `.safeParse()` | Validate and extract data |
| `z.infer<typeof Schema>` | Extract TypeScript type from schema |
| `z.input<>`, `z.output<>` | Input vs output types with transforms |
| `z.file()` | File instance validation (v4) |
| `z.toJSONSchema()` | Convert schema to JSON Schema (v4) |
| `.meta()`, `.describe()` | Attach metadata to schemas (v4) |
| `z.prettifyError()` | Human-readable error formatting (v4) |
| `z.treeifyError()` | Structured error tree (replaces .format(), v4) |
| `z.registry()` | Typed schema registry (v4) |
| `{ error: (issue) => ... }` | Unified error customization (v4) |
| Getter-based recursion | Recursive types without `z.lazy()` (v4) |
| `z.globalRegistry` | Global schema metadata registry (v4) |
| `z.config(z.locales.en())` | Internationalized error messages (v4) |
## Common Mistakes
| Mistake | Fix |
| --------------------------------------- | ------------------------------------------------------------- |
| `z.string().email()` | `z.email()` (v4 top-level format) |
| `z.string().url()` | `z.url()` (v4 top-level format) |
| Using `parse` without try/catch | Use `safeParse` for error handling |
| Forgetting `.optional()` | Add when field may be undefined |
| `z.any()` for unknown data | Use `z.unknown()` for type-safe unknown |
| `.transform()` for same-type changes | Use `.overwrite()` (introspectable, v4) |
| Missing `.min(1)` on strings | Empty strings pass `z.string()` by default |
| `z.number().parse(Infinity)` | `z.number()` rejects `Infinity` in v4 |
| `z.number().safe()` for floats | `.safe()` equals `.int()` in v4 (no floats) |
| `z.lazy()` for recursive types | Use getter syntax in v4 (retains object methods) |
| `required_error` / `invalid_type_error` | Use unified `error` function in v4 |
| `.refine(fn, (val) => ({ message }))` | Function-as-second-arg overload removed; use `.superRefine()` |
| `errorMap` on schemas | Replaced by `error` function in v4 |
| `z.record(z.string())` single arg | v4 requires two args: `z.record(z.string(), z.string())` |
| `.format()` / `.flatten()` on ZodError | Deprecated; use `z.treeifyError(err)` in v4 |
| `.default()` with input type value | v4 `.default()` uses output type; use `.prefault()` for input |
## Delegation
Use this skill for Zod schema definition, validation, parsing, type inference, coercion, error formatting, metadata, and JSON Schema conversion. For form integration, delegate to the tanstack-form skill.
## References
- [Schema Types](references/schema-types.md) — primitives, string formats, number formats, template literals, objects, arrays, enums, unions, records, optional, nullable
- [Transforms and Parsing](references/transforms-and-parsing.md) — coercion, stringbool, transforms, overwrite, pipe, refinements, parsing, type inference
- [Error Handling](references/error-handling.md) — unified error function, prettifyError, treeifyError, ZodError, error formatting, internationalization
- [Common Patterns](references/common-patterns.md) — form validation, API responses, environment variables, schema composition, recursive types, branded types
- [Metadata and JSON Schema](references/metadata-and-json-schema.md) — meta, describe, globalRegistry, toJSONSchema, file validation, Zod Mini
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.