uniform-best-practices

Enforce schema-first UniForm form building from Zod V4 schemas.

2|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/UniFormTS/UniForm --skill uniform-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uniform-best-practices
Source: https://github.com/UniFormTS/UniForm/tree/main/.agents/skills/uniform-best-practices
Command: npx skills add https://github.com/UniFormTS/UniForm --skill uniform-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates common mistakes, bugs, and anti-patterns when building forms with UniForm (@uniform-ts/core), ensuring you follow the library's intended schema-first workflow instead of hand-wiring inputs, mixing data and UI concerns, or using non-existent APIs.

Core Features & Use Cases

  • Schema-first form building: Enforces using a single Zod V4 schema as the single source of truth for data shape, validation, and types, eliminating drift between your form and submitted data.
  • Idiomatic API guidance: Prevents common errors like conflating createForm and createAutoForm, baking UI metadata into schemas, or manually toggling field visibility instead of using UniForm's built-in condition system.
  • Specialized agent pipeline: For complex multi-step forms, delegates work to role-specific agents (Schema Architect, Form Builder, Form Reviewer) to separate data modeling, presentation, and auditing for clean, maintainable code. Use case: For example, when building an onboarding form with conditional employment fields and a repeating list of references, this Skill ensures the schema stays clean, presentation is layered correctly, and the final code is audited for idiomatic use before shipping.

Quick Start

Ask this Skill to build a UniForm form from your Zod schema, add conditional field reveals, configure a custom component registry, or audit existing form code for non-idiomatic usage.

Frequently Asked Questions about uniform-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build React forms from a Zod schema without mixing UI and validation logic?

Schema-first form building with UniForm uses a single Zod schema as the source of truth for data shape and validation, separating presentation concerns by configuring component registries and field overrides to keep your React form code clean.

What is the best way to handle conditional field reveals in a Zod-driven React form?

Conditional field reveals in React forms should use UniForm's built-in condition system rather than manually toggling field visibility, preventing common anti-patterns and ensuring idiomatic schema-first workflow.

How do I configure a custom component registry for schema-first form building?

Schema-first form building allows you to configure component registries and field overrides via createAutoForm, enabling design system reuse while keeping UI metadata out of your Zod validation schemas.

Can I use createAutoForm and createForm interchangeably for React form validation?

No, createAutoForm and createForm serve distinct purposes in schema-first form building; conflating them is a common API misuse that this approach prevents by enforcing UniForm's official API surface for React form development.

How do I manage repeating array rows and dynamic lists in a Zod schema React form?

Schema-first form building supports adding array rows natively through the UniForm API, allowing you to maintain a single Zod schema for dynamic lists without hand-wiring inputs or drifting from submitted data types.

Why should I audit existing React form code for non-idiomatic UniForm usage?

Auditing existing React form code for non-idiomatic UniForm usage ensures compliance with the official API surface, eliminating bugs from hand-wired inputs, mixed data and UI concerns, and non-existent APIs.