Schema validation best practices for TypeScript with 43 prioritized rules across type safety, parsing, and error handling.
Works with
Covers 8 rule categories from schema definition and parsing (CRITICAL) through type inference, error handling, and performance (LOW-MEDIUM)
Distinguishes safeParse() for user input, parseAsync() for async refinements, and parse() for trusted data; emphasizes validation at system boundaries
Provides guidance on z.infer for type inference, z.unknown() over z.any(),
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionzodExecute the skills CLI command in your project's root directory to begin installation:
Fetches zod from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate zod. Access via /zod in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
95
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
95
stars
Comprehensive schema validation guide for Zod in TypeScript applications. Contains 43 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Schema Definition | CRITICAL | schema- |
| 2 | Parsing & Validation | CRITICAL | parse- |
| 3 | Type Inference | HIGH | type- |
| 4 | Error Handling | HIGH | error- |
| 5 | Object Schemas | MEDIUM-HIGH | object- |
| 6 | Schema Composition | MEDIUM | compose- |
| 7 | Refinements & Transforms | MEDIUM | refine- |
| 8 | Performance & Bundle | LOW-MEDIUM | perf- |
schema-use-primitives-correctly - Use correct primitive schemas for each typeschema-use-unknown-not-any - Use z.unknown() instead of z.any() for type safetyschema-avoid-optional-abuse - Avoid overusing optional fieldsschema-string-validations - Apply string validations at schema definitionschema-use-enums - Use enums for fixed string valuesschema-coercion-for-form-data - Use coercion for form and query dataparse-use-safeparse - Use safeParse() for user inputparse-async-for-async-refinements - Use parseAsync for async refinementsparse-handle-all-issues - Handle all validation issues not just firstparse-validate-early - Validate at system boundariesparse-avoid-double-validation - Avoid validating same data twiceparse-never-trust-json - Never trust JSON.parse outputtype-use-z-infer - Use z.infer instead of manual typestype-input-vs-output - Distinguish z.input from z.infer for transformstype-export-schemas-and-types - Export both schemas and inferred typestype-branded-types - Use branded types for domain safetytype-enable-strict-mode - Enable TypeScript strict modeerror-custom-messages - Provide custom error messageserror-use-flatten - Use flatten() for form error displayerror-path-for-nested - Use issue.path for nested error locationerror-i18n - Implement internationalized error messageserror-avoid-throwing-in-refine - Return false instead of throwing in refineobject-strict-vs-strip - Choose strict() vs strip() for unknown keysobject-partial-for-updates - Use partial() for update schemasobject-pick-omit - Use pick() and omit() for schema variantsobject-extend-for-composition - Use extend() for adding fieldsobject-optional-vs-nullable - Distinguish optional() from nullable()object-discriminated-unions - Use discriminated unions for type narrowingcompose-shared-schemas - Extract shared schemas into reusable modulescompose-intersection - Use intersection() for type combinationscompose-lazy-recursive - Use z.lazy() for recursive schemascompose-preprocess - Use preprocess() for data normalizationcompose-pipe - Use pipe() for multi-stage validationrefine-vs-superrefine - Choose refine() vs superRefine() correctlyrefine-transform-coerce - Distinguish transform() from refine() and coerce()refine-add-path - Add path to refinement errorsrefine-defaults - Use default() for optional fields with defaultsrefine-catch - Use catch() for fault-tolerant parsingperf-cache-schemas - Cache schema instancesperf-zod-mini - Use Zod Mini for bundle-sensitive applicationsperf-avoid-dynamic-creation - Avoid dynamic schema creation in hot pathsperf-lazy-loading - Lazy load large schemasperf-arrays - Optimize large array validationRead individual reference files for detailed explanations and code examples:
references/{prefix}-{slug}.mdFor the complete guide with all rules expanded: AGENTS.md
react-hook-form skillorval skillMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
pproenca/dot-skills
pproenca/dot-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
We added zod from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in zod — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
zod fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: zod is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for zod matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend zod for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
zod reduced setup friction for our internal harness; good balance of opinion and flexibility.
zod is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: zod is focused, and the summary matches what you get after install.
zod has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 54