Combines uncontrolled registration with Zod schema validation and full TypeScript inference via z.infer ; supports dynamic fields, multi-step wizards, and conditional validation patterns
Includes resolver setup, error handling, useFieldArray for dynamic lists, and Controller integration for third-party components
Documents 20 known issues and workarounds, including large-form performanc
Fetches react-hook-form-zod from jezweb/claude-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/react-hook-form-zod
Restart Cursor to activate react-hook-form-zod. Access via /react-hook-form-zod in your agent's command palette.
⚠
Security Notice
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.
// SAME schema on serverconst data = schema.parse(await req.json())
Key Patterns
useForm Options (validation modes):
mode: 'onSubmit' (default) - Best performance
mode: 'onBlur' - Good balance
mode: 'onChange' - Live feedback, more re-renders
shouldUnregister: true - Remove field data when unmounted (use for multi-step forms)
Zod Refinements (cross-field validation):
z.object({ password: z.string(), confirm: z.string()}).refine((data)=> data.password === data.confirm,{ message:"Passwords don't match", path:['confirm'],// CRITICAL: Error appears on this field})
Zod Transforms:
z.string().transform((val)=> val.toLowerCase())// Data manipulationz.string().transform(parseInt).refine((v)=> v >0)// Chain with refine
Zod v4.3.0+ Features:
// Exact optional (can omit field, but NOT undefined)z.string().exactOptional()// Exclusive union (exactly one must match)z.xor([z.string(), z.number()])// Import from JSON Schemaz.fromJSONSchema({ type:"object", properties:{ name:{ type:"string"}}})
zodResolver connects Zod to React Hook Form, preserving type safety
Registration
register (for standard HTML inputs):
<input {...register('email')}/>// Uncontrolled, best performance
Controller (for third-party components):
<Controller
name="category" control={control} render={({ field })=><CustomSelect {...field}/>}// MUST spread {...field}/>
When to use Controller: React Select, date pickers, custom components without ref. Otherwise use register.
const{ fields, append, remove }=useFieldArray({ control, name:'contacts'}){fields.map((field, index)=>(<div key={field.id}>{/* CRITICAL: Use field.id, NOT index */}<input {...register(`contacts.${index}.name`asconst)}/>{errors.contacts?.[index]?.name &&<span>{errors.contacts[index].name.message}</span>}<button onClick={()=>remove(index)}>Remove</button></div>))}<button onClick={()=>append
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
