react-hook-form
Build and modify forms that use React Hook Form or whose project conventions require it. Use when implementing controlled widgets, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, or dirty-state handling. For review o
Install
npx skills add https://github.com/kriscard/Skills/tree/main/skills/dev/react-hook-form
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install kriscard-skills@llmmart
git clone https://github.com/kriscard/Skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole kriscard/skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
React Hook Form
Build around four decisions: ownership, schema tree, adapter, and baseline. RHF evidence is the invocation boundary; an ordinary React form request does not itself justify introducing the library.
Process
1. Establish the form contract
Inspect the installed RHF, React, resolver, schema, data-fetching, and UI-library versions before writing code. Identify:
- create or edit form;
- submitted value shape and API payload shape;
- client snapshot or live server-data ownership;
- native input contracts versus controlled adapters;
- conditional, array, or wizard branches;
- stable v7 APIs versus installed v8 APIs.
Completion: the value owner, form type, installed versions, and required branches are explicit.
2. Define the schema tree and defaults
Create one canonical form-value model. Compose section or wizard schemas into the full schema;
when parsing transforms values, distinguish schema input from output types. Supply a complete
non-undefined default for every tracked field and transform API values at the boundary.
Completion: every registered path exists in the typed model and has a valid default; the full submission schema can validate the complete form.
3. Build the field boundary
Use register when a component preserves the native input contract. Use Controller or
useController when a widget exposes a controlled or non-native value/change contract. Apply the
accessible field contract to every control.
Completion: every field has one registration path, correct value/event/ref wiring, and an associated label, description when present, and error message.
4. Implement lifecycle and branches
Load the relevant reference before implementing a branch:
| Priority | Load when | Reference |
|---|---|---|
| 1 — High | Fetched edit data, background refresh, mutation, reset, dirty baseline | references/server-data-and-lifecycle.md |
| 2 — High | UI-library or custom controlled components, accessibility wiring | references/adapters-and-accessibility.md |
| 3 — High | Wizard, step validation, cross-step rule, conditional or hidden field | references/wizards-and-conditionals.md |
| 4 — High | Dynamic or nested rows with useFieldArray |
references/field-arrays.md |
| 5 — Medium | Installed project uses or is migrating to RHF v8 | references/version-8.md |
| 6 — Medium | React 19 action or Next.js Server Action appears in the same flow | references/actions-boundary.md |
| 7 — Medium | Tests requested or affected; async submission, baseline, conditional/wizard, or field-array behavior changed | references/testing.md |
Completion: every detected branch has loaded and applied its reference; no branch is handled from memory alone.
5. Verify
Run the project's TypeScript typecheck and fix every error caused by the change. Run focused existing tests when present. When the testing reference was loaded, add or update its behavioral tests. Otherwise tests are optional. Exercise the form manually when runtime tooling is available.
Completion: typecheck passes, or unrelated pre-existing failures are named with evidence; modified paths, submission mapping, and failure behavior have all been checked.
Universal rules
- Uncontrolled first. Native contract means
register; design-system component does not automatically meanController. - One registration path. A controlled field is never also registered.
- Complete defaults. Avoid
undefined; defaults are the dirty-state comparison baseline. - Validation is a UX choice. Select
modeandreValidateModefrom interaction cost and feedback needs rather than prescribing one mode globally. - Narrow observation. Use
useWatchfor local reactive UI,useFormStatefor local form state,getValuesfor snapshots, andsubscribefor non-render effects. - Visible and semantic errors. Connect labels and descriptions, put
aria-invalidon the interactive element, and render an associated message. Useroot.*for form-wide failures. - Caught submission. Catch transport failures, preserve edits on failure, and prevent duplicate submissions while work is pending.
- Serialization is a boundary. Hidden-field policy, disabled-field omission, coercion, and dirty-only PATCH behavior are explicit domain decisions.
- Server validation remains authoritative. Client validation improves interaction; it never replaces server validation, authorization, or conflict handling.
Handoff
Report the ownership model, schema/default strategy, adapter choices, lifecycle behavior, version gates, changed files, typecheck command and result, tests run or skipped, and remaining risks.
Files (skills)
-
references
-
actions-boundary.md 1.1 KB
Loading… -
adapters-and-accessibility.md 2.8 KB
Loading… -
field-arrays.md 1.3 KB
Loading… -
server-data-and-lifecycle.md 3 KB
Loading… -
testing.md 1.2 KB
Loading… -
version-8.md 1.1 KB
Loading… -
wizards-and-conditionals.md 2.4 KB
Loading…
-
-
SKILL.md 5 KB
--- name: react-hook-form description: >- Build and modify forms that use React Hook Form or whose project conventions require it. Use when implementing controlled widgets, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, or dirty-state handling. For review or diagnosis, use react-hook-form-audit. --- # React Hook Form Build around four decisions: **ownership**, **schema tree**, **adapter**, and **baseline**. RHF evidence is the invocation boundary; an ordinary React form request does not itself justify introducing the library. ## Process ### 1. Establish the form contract Inspect the installed RHF, React, resolver, schema, data-fetching, and UI-library versions before writing code. Identify: - create or edit form; - submitted value shape and API payload shape; - client snapshot or live server-data ownership; - native input contracts versus controlled adapters; - conditional, array, or wizard branches; - stable v7 APIs versus installed v8 APIs. Completion: the value owner, form type, installed versions, and required branches are explicit. ### 2. Define the schema tree and defaults Create one canonical form-value model. Compose section or wizard schemas into the full schema; when parsing transforms values, distinguish schema input from output types. Supply a complete non-`undefined` default for every tracked field and transform API values at the boundary. Completion: every registered path exists in the typed model and has a valid default; the full submission schema can validate the complete form. ### 3. Build the field boundary Use `register` when a component preserves the native input contract. Use `Controller` or `useController` when a widget exposes a controlled or non-native value/change contract. Apply the accessible field contract to every control. Completion: every field has one registration path, correct value/event/ref wiring, and an associated label, description when present, and error message. ### 4. Implement lifecycle and branches Load the relevant reference before implementing a branch: | Priority | Load when | Reference | | --- | --- | --- | | 1 — High | Fetched edit data, background refresh, mutation, reset, dirty baseline | `references/server-data-and-lifecycle.md` | | 2 — High | UI-library or custom controlled components, accessibility wiring | `references/adapters-and-accessibility.md` | | 3 — High | Wizard, step validation, cross-step rule, conditional or hidden field | `references/wizards-and-conditionals.md` | | 4 — High | Dynamic or nested rows with `useFieldArray` | `references/field-arrays.md` | | 5 — Medium | Installed project uses or is migrating to RHF v8 | `references/version-8.md` | | 6 — Medium | React 19 action or Next.js Server Action appears in the same flow | `references/actions-boundary.md` | | 7 — Medium | Tests requested or affected; async submission, baseline, conditional/wizard, or field-array behavior changed | `references/testing.md` | Completion: every detected branch has loaded and applied its reference; no branch is handled from memory alone. ### 5. Verify Run the project's TypeScript typecheck and fix every error caused by the change. Run focused existing tests when present. When the testing reference was loaded, add or update its behavioral tests. Otherwise tests are optional. Exercise the form manually when runtime tooling is available. Completion: typecheck passes, or unrelated pre-existing failures are named with evidence; modified paths, submission mapping, and failure behavior have all been checked. ## Universal rules 1. **Uncontrolled first.** Native contract means `register`; design-system component does not automatically mean `Controller`. 2. **One registration path.** A controlled field is never also registered. 3. **Complete defaults.** Avoid `undefined`; defaults are the dirty-state comparison baseline. 4. **Validation is a UX choice.** Select `mode` and `reValidateMode` from interaction cost and feedback needs rather than prescribing one mode globally. 5. **Narrow observation.** Use `useWatch` for local reactive UI, `useFormState` for local form state, `getValues` for snapshots, and `subscribe` for non-render effects. 6. **Visible and semantic errors.** Connect labels and descriptions, put `aria-invalid` on the interactive element, and render an associated message. Use `root.*` for form-wide failures. 7. **Caught submission.** Catch transport failures, preserve edits on failure, and prevent duplicate submissions while work is pending. 8. **Serialization is a boundary.** Hidden-field policy, disabled-field omission, coercion, and dirty-only PATCH behavior are explicit domain decisions. 9. **Server validation remains authoritative.** Client validation improves interaction; it never replaces server validation, authorization, or conflict handling. ## Handoff Report the ownership model, schema/default strategy, adapter choices, lifecycle behavior, version gates, changed files, typecheck command and result, tests run or skipped, and remaining risks.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.