angelocolocado/clcd-agent-skills / skills/rrv7-zod-form
rrv7-zod-form
VerifiedUse this skill whenever building or wiring forms in React Router v7 (RRv7) Framework Mode (NO-SSR) using Zod, React Hook Form with real-time validation, `useFetcher`, `useEffect` response handling, and shadcn/ui `Field`, `Input`, `Button`, and `Spinner` components.
RRv7 + React Hook Form + Zod Form Pattern
Follow this architecture whenever creating or wiring up validated forms that submit mutations to a parent route's clientAction (paired with rrv7-api-mutation-handler).
Strict Implementation Rules
- Schema & Real-Time Validation (
zod+react-hook-form):- Define a strict
z.object(...)schema and infer its TypeScript type viaz.infer<typeof formSchema>. - Initialize
useFormwithresolver: zodResolver(formSchema)andmode: "onChange"so field validation runs in real time as the user types.
- Define a strict
- Submission via
useFetcher:- Use RRv7's
useFetcher<typeof clientAction>()(or typed fetcher) to submit form values directly to the parent route'sclientActionwithout a full-page navigation. - Always include the matching
intentkey infetcher.submit({ ...values, intent: "<intent-name>" }, { method: "POST" })soclientActionroutes the request properly.
- Use RRv7's
- Response & Status Code Handling (
useEffect):- Watch
fetcher.stateandfetcher.datainside auseEffecthook (guarding withif (fetcher.state !== "idle" || !fetcher.data) return;). - On
success === true: Reset the form viaform.reset()and trigger any post-success UI callbacks (such as closing a modal/dialog). Rely on RRv7's automaticclientLoaderrevalidation to refresh displayed page data. - On
success === false: Preserve user inputs and inspectcode:- If
code === 422anddata?.errorsexists (Laravel validation errors), loop throughObject.entries(data.errors)and attach each message to its corresponding field usingform.setError(field, { type: "server", message }). - For other error codes (e.g.,
403,500), optionally set a root form error viaform.setError("root", { message })alongside the toast handled byclientAction.
- If
- Watch
- shadcn/ui Components & Pending State:
- Use
@/components/ui/field(Field,FieldLabel,FieldDescription,FieldError),@/components/ui/input(Input),@/components/ui/button(Button), and@/components/ui/spinner(Spinner)—adjusting@/or~/to matchtsconfig.json. - Derive
const isSubmitting = fetcher.state !== "idle";. - Strictly disable the submit
<Button disabled={isSubmitting}>(and form inputs if appropriate) while submitting, and render<Spinner />inside the button during pending states.
- Use
Reference Boilerplate
import { useEffect } from "react";
import { useFetcher } from "react-router";
import { Controller, useForm } from "react-hook-form";
import { zodResolver } from "@hookform/resolvers/zod";
import { z } from "zod";
import {
Field,
FieldDescription,
FieldError,
FieldLabel,
} from "@/components/ui/field";
import { Input } from "@/components/ui/input";
import { Button } from "@/components/ui/button";
import { Spinner } from "@/components/ui/spinner";
// 1. Define Zod Schema
const createOrderSchema = z.object({
name: z.string().min(2, "Order name must be at least 2 characters."),
quantity: z.coerce.number().min(1, "Quantity must be at least 1."),
});
type CreateOrderValues = z.infer<typeof createOrderSchema>;
interface CreateOrderFormProps {
onSuccess?: () => void; // e.g., close modal/dialog
}
export function CreateOrderForm({ onSuccess }: CreateOrderFormProps) {
const fetcher = useFetcher();
const isSubmitting = fetcher.state !== "idle";
// 2. Initialize React Hook Form with real-time validation
const form = useForm<CreateOrderValues>({
resolver: zodResolver(createOrderSchema),
mode: "onChange",
defaultValues: {
name: "",
quantity: 1,
},
});
// 3. Submit to parent route's clientAction with intent
function onSubmit(values: CreateOrderValues) {
fetcher.submit(
{ ...values, intent: "process-order" },
{ method: "POST" }
);
}
// 4. Detect success or map Laravel error codes via useEffect
useEffect(() => {
if (fetcher.state !== "idle" || !fetcher.data) return;
const result = fetcher.data as {
success: boolean;
code?: number;
data?: { message?: string; errors?: Record<string, string[]> };
};
if (result.success) {
form.reset();
onSuccess?.();
return;
}
// Handle Laravel 422 field validation errors
if (result.code === 422 && result.data?.errors) {
Object.entries(result.data.errors).forEach(([field, messages]) => {
const message = Array.isArray(messages) ? messages[0] : String(messages);
form.setError(field as keyof CreateOrderValues, {
type: "server",
message,
});
});
return;
}
// Handle non-422 errors (e.g., 403, 500) if needed in UI
if (result.data?.message) {
form.setError("root", {
type: "server",
message: result.data.message,
});
}
}, [fetcher.state, fetcher.data, form, onSuccess]);
return (
<form onSubmit={form.handleSubmit(onSubmit)} className="space-y-4">
<Controller control="{form.control}" field, fieldState name="name" render="{({"> (
<Field data-invalid="{fieldState.invalid}">
<FieldLabel htmlFor="order-name">Order Name</FieldLabel>
<Input aria-invalid="{fieldState.invalid}" disabled="{isSubmitting}" id="order-name" placeholder="Enter order name" {...field}/>
<FieldDescription>
Provide a descriptive name for this order.
</FieldDescription>
{fieldState.invalid && <FieldError errors="{[fieldState.error]}"/>}
</Field>
)}
/>
<Controller control="{form.control}" field, fieldState name="quantity" render="{({"> (
<Field data-invalid="{fieldState.invalid}">
<FieldLabel htmlFor="order-quantity">Quantity</FieldLabel>
<Input aria-invalid="{fieldState.invalid}" disabled="{isSubmitting}" id="order-quantity" type="number" {...field}/>
{fieldState.invalid && <FieldError errors="{[fieldState.error]}"/>}
</Field>
)}
/>
{form.formState.errors.root && (
<p className="text-sm font-medium text-destructive">
{form.formState.errors.root.message}
</p>
)}
<Button disabled="{isSubmitting}" type="submit">
{isSubmitting && <Spinner/>}
{isSubmitting ? "Submitting..." : "Submit Order"}
</Button>
</form>
);
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |