Rezi Forms
Developmentrezi-formsRezi Forms is an Agent Skill for development published in the RtlZeroMemory/Rezi repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Set up form input handling with validation and submission. Use when building forms with inputs, selects, checkboxes, etc.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/RtlZeroMemory/Rezi/blob/HEAD/.claude/skills/rezi-forms/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/rezi-forms, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
When to use
Use this skill when:
- Building forms with multiple inputs
- Need field validation and error display
- Handling form submission with loading states
Source of truth
packages/core/src/forms/useForm.ts—useForm()hookpackages/core/src/widgets/types.ts—InputProps,FieldProps,CheckboxProps,SelectPropspackages/core/src/widgets/ui.ts—ui.input(),ui.field(),ui.checkbox(),ui.select()packages/core/src/ui/recipes.ts—recipe.input(),recipe.button(),recipe.select()for design-system styling
Steps
-
Use the
useForm()hook inside adefineWidget:import { defineWidget, ui, useForm } from "@rezi-ui/core"; const MyForm = defineWidget<{ onSubmit: (v: Values) => void }>((props, ctx) => { const form = useForm(ctx, { initialValues: { name: "", email: "" }, validate: (values) => { const errors: Record<string, string> = {}; if (!values.name) errors.name = "Required"; if (!values.email.includes("@")) errors.email = "Invalid email"; return errors; }, onSubmit: async (values) => props.onSubmit(values), }); return ui.column({ gap: 1 }, [ ui.field({ label: "Name", error: form.errors.name, children: ui.input({ id: "field-name", ...form.bind("name") }), }), ui.field({ label: "Email", error: form.errors.email, children: ui.input({ id: "field-email", ...form.bind("email") }), }), ui.actions([ ui.button({ id: "cancel", label: "Cancel", intent: "secondary", onPress: () => {} }), ui.button({ id: "save", label: "Save", intent: "primary", onPress: form.handleSubmit }), ]), ]); }, { name: "MyForm" }); -
Bind fields using
form.bind("fieldName")— returns object-form input props (value,onInput,onBlur,disabled) -
Use
ui.field()to wrap inputs with labels and error display -
Access form state via
form.errors,form.touched,form.dirty,form.submitting -
Use success/warning for non-submit side actions:
ui.button({ id: "approve", label: "Approve", intent: "success", onPress: handleApprove }); ui.button({ id: "review", label: "Needs Review", intent: "warning", onPress: handleReview });
Design system note
Inputs are recipe-styled by default when semantic color tokens are available (for example via a ThemeDefinition preset).
Manual overrides merge on top via the same mergeTextStyle(baseStyle, ownStyle) pattern used by the renderer.
Use manual style only for targeted overrides (merged on top of recipe output).
For button visuals, use intent (primary, secondary, danger, success, warning, link) in app code.
Do not use dsVariant/dsTone in app-level form code.
Verification
- Validation errors display next to fields
- Submission works and calls
onSubmit - Touched/dirty state tracked correctly