What problem does it solve? Building forms that stay synchronized with backend contracts is error-prone: developers hand-roll validation rules that drift from the API, misuse form state, and repeat the same dialog and wizard boilerplate. This Skill enforces a single pattern where the SDK's Zod schema is the source of truth for validation and TanStack Form owns all field state. ## Core Features & Use Cases - SDK-schema validation: Forms validate against the same Zod schema the controller declares, with safeParse guards in onSubmit and reactive submit buttons via form.Subscribe. - Three form types: Single forms, multi-step wizards (Zustand navigation store, step schema extraction, progressive save), and self-contained dialog forms opened via useDialogStore. - Field pattern library: Maskito masked inputs, enum-driven Select/Combobox, CurrencyInput, array fields, and a registry of bad practices (bp-01 through bp-19) to avoid. - Use Case: Add a create-patient dialog that validates against the SDK mutation schema, masks CPF and phone inputs, submits through the SDK mutation hook, and invalidates the relevant query keys on success. ## Quick Start Ask the agent to create a form for a specific SDK mutation in the React app, for example: create a dialog form for the createItem mutation with name and email fields.