zod
Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, and v3→v4 migration. Baseline: zod ^4.0.0. Triggers on: zod imports, z.object, z.string, z.infer, safeParse, mentions of "zod", "schema validation", "zod v4", or "z.enum".
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/anivar/zod-skillWhat This Skill Does
The zod skill provides specialized expertise for Zod v4, the industry-standard TypeScript schema validation library. As Zod v4 introduces significant breaking changes—such as the removal of z.lazy() and changes to error handling patterns—this skill acts as a guardrail, ensuring your implementation avoids deprecated v3 methods while leveraging new v4 capabilities. It covers the entire lifecycle of schema validation, from initial object definition and type inference to advanced cross-field validation, performance-tuned parsing, and secure error management. Whether you are migrating a legacy codebase or starting a new project, this skill ensures your data boundaries are type-safe, performant, and secure.
Installation
To integrate this skill into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/anivar/zod-skill
Use Cases
- API Boundary Protection: Validate incoming JSON payloads, headers, and query parameters to ensure they match expected TypeScript interfaces before reaching your business logic.
- Form Validation: Seamlessly integrate with frontend form libraries to provide type-safe, user-friendly validation schemas.
- Environment Configuration: Parse and validate process.env variables at application startup, providing clear error messages for missing or malformed configuration keys.
- Type Migration: Upgrade existing Zod v3 projects to v4, specifically targeting replacements for removed features like
z.lazy()and the updated error reporting system. - Complex Data Transformation: Using
.pipe()and.transform()to safely coerce and clean messy external data inputs into clean, internal domain models.
Example Prompts
- "I am getting a type error migrating from Zod v3 to v4 regarding recursive types. How do I use the new getter pattern instead of z.lazy?"
- "Can you help me write a cross-field validation schema using superRefine that compares password and confirmPassword fields in my registration object?"
- "Review this schema implementation for a user profile; I need to make sure I am using safeParse correctly and that I'm not exposing sensitive raw input in my error logs."
Tips & Limitations
- Rule Priority: Always prioritize
parse-andschema-rules. These represent critical security and type-safety boundaries. - Performance: For high-throughput applications, prefer
z.discriminatedUnion()over standard unions to reduce schema evaluation time. - Security: Never enable
reportInput: truein production environments, as this can leak PII or credentials via error messages. - Version Control: This skill is tuned for Zod ^4.0.0. If you are locked to an older version, please specify the version in your prompt so the agent can provide legacy-compatible guidance.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-anivar-zod-skill": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Related Skills
zod-testing
Testing patterns for Zod schemas using Jest and Vitest. Covers schema correctness testing, mock data generation, error assertion patterns, integration testing with API handlers and forms, snapshot testing with z.toJSONSchema(), and property-based testing. Baseline: zod ^4.0.0. Triggers on: test files for Zod schemas, zod-schema-faker imports, mentions of "test schema", "schema test", "zod mock", "zod test", or schema testing patterns.
jest
Jest best practices, patterns, and API guidance for JavaScript/TypeScript testing. Covers mock design, async testing, matchers, timer mocks, snapshots, module mocking, configuration, and CI optimization. Baseline: jest ^29.0.0 / ^30.0.0. Triggers on: jest imports, describe, it, test, expect, jest.fn, jest.mock, jest.spyOn, mentions of "jest", "unit test", "test suite", or "mock".
redux-saga-testing
Write tests for Redux Sagas using redux-saga-test-plan, runSaga, and manual generator testing. Covers expectSaga (integration), testSaga (unit), providers, partial matchers, reducer integration, error simulation, and cancellation testing. Works with Jest and Vitest. Triggers on: test files for sagas, redux-saga-test-plan imports, mentions of "test saga", "saga test", "expectSaga", "testSaga", or "redux-saga-test-plan".
redux-saga
Redux-Saga best practices, patterns, and API guidance for building, testing, and debugging generator-based side-effect middleware in Redux applications. Covers effect creators, fork model, channels, testing with redux-saga-test-plan, concurrency, cancellation, and modern Redux Toolkit integration. Baseline: redux-saga 1.4.2. Triggers on: saga files, redux-saga imports, generator-based middleware, mentions of "saga", "takeEvery", "takeLatest", "fork model", or "channels".
msw
MSW (Mock Service Worker) v2 best practices, patterns, and API guidance for API mocking in JavaScript/TypeScript tests and development. Covers handler design, server setup, response construction, testing patterns, GraphQL, and v1-to-v2 migration. Baseline: msw ^2.0.0. Triggers on: msw imports, http.get, http.post, HttpResponse, setupServer, setupWorker, graphql.query, mentions of "msw", "mock service worker", "api mocking", or "msw v2".