uniform-best-practices

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.