More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Forms Master: React Forms With Server Actions

    1

    Form architecture for React 19 and Next.js: native Server Actions or React Hook Form, one Zod schema for both sides, pending and failure states, accessible errors.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Forms Master: React Forms With Server Actions

    Forms Master: React Forms With Server Actions

    Example session with this skill installed

    Design the form architecture for our clinic's appointment booking: patient details, a reason-for-visit picker that changes which follow-up questions appear, an insurance card photo upload, and a review step before confirming.

    • Read your context and instructions
    • Compiled the forms master

    ARCHITECTURE RECORD — produced by applying the skill.

    Classification: 4 steps; 14 fields; one genuinely conditional block (follow-ups depend on the visit reason); one upload; no per-keystroke validation; losing entered data would be costly — patients will abandon and phone instead. Those signals decide everything below.

    Decision: server-driven wizard, native Server Actions throughout — React Hook Form not installed. The conditional follow-ups render per step on the server from the chosen reason, so interactivity never reaches the library threshold; and server-driven steps stash validated progress in the session, so a refresh or a dead phone battery loses nothing.

    Per step

    1. Patient details — native action; Zod schema with coercion for the date of birth; errors return as structured state, linked per field.
    2. Reason and follow-ups — the reason posts first; the step re-renders with that reason's follow-up set. One schema per reason variant, discriminated on the reason field, so answers are never validated against the wrong question set.
    3. Insurance card — its own upload action: File read from FormData, size capped at 10 MB, MIME allowlist checked server-side (the accept attribute is a hint only); the form stores the returned reference, never the file.
    4. Review — read-only summary of the stashed steps with edit links back; the confirm action re-validates every step's data server-side against the same schemas before booking — nothing is trusted because a step checked it earlier.

    States: submit buttons take pending state from useFormStatus and disable — no double booking; a failed step keeps the patient's entries and announces errors via an alert region, with focus moved to an error summary linked to each field; no optimistic updates — a booking is not where "probably confirmed" is acceptable.

    Accessibility pass: every input labeled, required marked and announced, aria-invalid and aria-describedby wired as in the native pattern, step headings announce progress ("step 2 of 4").

    Rubric: 10/10 — validation integrity 2 (one schema per step, server always validates), input survival 2 (nothing clears before confirmation), state coverage 2, accessibility 2, fit 2.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    React 19 changed the default answer for forms: Server Actions plus useActionState now cover most of what used to require a form library. The skill is knowing where native patterns end and a library begins. This skill starts by classifying the form — field count, conditional fields, computed values, field arrays, validation timing — and turns that into an architecture decision: native, React Hook Form, or a deliberate split, with the deciding signals recorded for the next maintainer. Then it builds properly: one Zod schema driving validation on both sides with types inferred from it, a Server Action returning structured state, pending handling that makes double submits impossible, optimistic updates that reconcile honestly, and failure states that never eat the user's input. File uploads get server-side size and type checks (the accept attribute is not a check), multi-step wizards get a deliberate server-driven or client-driven shape, and every form closes with an accessibility pass — labeled inputs, errors linked to fields and announced, focus moved to an error summary on failed submits. Includes the full native pattern in code, a form worksheet, a pre-ship checklist, and a quality rubric.

    • React 19 / Next.js only; the patterns do not transfer to other frameworks by analogy.
    • It decides and wires form behavior — it is not a component library and ships no prebuilt fields.
    • Extremely interactive forms (live spreadsheets, drag-and-drop builders) exceed even the split pattern and need a dedicated state approach.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Sometimes — for 10+ fields with heavy conditional logic, computed values, or dynamic field arrays. The skill gives you the decision table, and the two compose: RHF can run the interaction while a Server Action still handles submission and final validation.

    Because two copies of the rules always drift. One Zod schema validates on both sides, and the TypeScript types are inferred from it, so the types and the validation can never disagree.

    Pending state disables the submit so a form cannot fire twice, the action is designed to be safe to retry, and a failed submit keeps the draft with inline, announced errors. Clearing the form happens only on confirmed success.

    New in Workflow Automation