Installation
Section titled “Installation”pnpm dlx shadcn@latest add pxl-ui/registry/field
Copy and paste the following code into your project.
Update the import paths to match your project setup.
import { Field, FieldContent, FieldDescription, FieldError, FieldGroup, FieldLabel, FieldLegend, FieldSeparator, FieldSet, FieldTitle,} from "@/components/ui/pxl/field"<FieldSet> <FieldLegend>Profile</FieldLegend> <FieldDescription>This appears on invoices and emails.</FieldDescription> <FieldGroup> <Field> <FieldLabel htmlFor="name">Full name</FieldLabel> <Input id="name" autoComplete="off" placeholder="Evil Rabbit" /> <FieldDescription>This appears on invoices and emails.</FieldDescription> </Field> <Field> <FieldLabel htmlFor="username">Username</FieldLabel> <Input id="username" autoComplete="off" aria-invalid /> <FieldError>Choose another username.</FieldError> </Field> <Field orientation="horizontal"> <Switch id="newsletter" /> <FieldLabel htmlFor="newsletter">Subscribe to the newsletter</FieldLabel> </Field> </FieldGroup></FieldSet>Composition
Section titled “Composition”A single control with label, helper text, and validation.
Field├── FieldLabel├── Input / Textarea / Switch / Select├── FieldDescription└── FieldErrorFieldGroup
Section titled “FieldGroup”Related fields in one group. Use FieldSeparator between sections when needed.
FieldGroup├── Field│ ├── FieldLabel│ ├── Input / Textarea / Switch / Select│ ├── FieldDescription│ └── FieldError├── FieldSeparator└── Field ├── FieldLabel └── Input / Textarea / Switch / SelectFieldSet
Section titled “FieldSet”Semantic grouping with a legend and description, usually containing a FieldGroup.
FieldSet├── FieldLegend├── FieldDescription└── FieldGroup ├── Field │ ├── FieldLabel │ ├── Input / Textarea / Switch / Select │ ├── FieldDescription │ └── FieldError └── Field ├── FieldLabel └── Input / Textarea / Switch / SelectAnatomy
Section titled “Anatomy”The Field family is designed for composing accessible forms. A typical field is structured as follows:
<Field> <FieldLabel htmlFor="input-id">Label</FieldLabel> {/* Input, Select, Switch, etc. */} <FieldDescription>Optional helper text.</FieldDescription> <FieldError>Validation message.</FieldError></Field>Fieldis the core wrapper for a single field.FieldContentis a flex column that groups label and description. Not required if you have no description.- Wrap related fields with
FieldGroup, and useFieldSetwithFieldLegendfor semantic grouping.
See the Form documentation for building forms with the Field component and React Hook Form, Tanstack Form, or Formisch.
Responsive Layout
Section titled “Responsive Layout”- Vertical fields: Default orientation stacks label, control, and helper text—ideal for mobile-first layouts.
- Horizontal fields: Set
orientation="horizontal"onFieldto align the label and control side-by-side. Pair withFieldContentto keep descriptions aligned. - Responsive fields: Set
orientation="responsive"for automatic column layouts inside container-aware parents. Apply@container/field-groupclasses onFieldGroupto switch orientations at specific breakpoints.
Validation and Errors
Section titled “Validation and Errors”- Add
data-invalidtoFieldto switch the entire block into an error state. - Add
aria-invalidon the input itself for assistive technologies. - Render
FieldErrorimmediately after the control or insideFieldContentto keep error messages aligned with the field.
<Field data-invalid> <FieldLabel htmlFor="email">Email</FieldLabel> <Input id="email" type="email" aria-invalid /> <FieldError>Enter a valid email address.</FieldError></Field>Accessibility
Section titled “Accessibility”FieldSetandFieldLegendkeep related controls grouped for keyboard and assistive tech users.Fieldoutputsrole="group"so nested controls inherit labeling fromFieldLabelandFieldLegendwhen combined.- Apply
FieldSeparatorsparingly to ensure screen readers encounter clear section boundaries.
API Reference
Section titled “API Reference”FieldSet
Section titled “FieldSet”Container that renders a semantic fieldset with spacing presets.
| Prop | Type | Default |
|---|---|---|
className |
string |
<FieldSet> <FieldLegend>Delivery</FieldLegend> <FieldGroup>{/* Fields */}</FieldGroup></FieldSet>FieldLegend
Section titled “FieldLegend”Legend element for a FieldSet. Switch to the label variant to align with label sizing.
| Prop | Type | Default |
|---|---|---|
variant |
"legend" | "label" |
"legend" |
className |
string |
<FieldLegend variant="label">Notification Preferences</FieldLegend>The FieldLegend has two variants: legend and label. The label variant applies label sizing and alignment. Handy if you have nested FieldSet.
FieldGroup
Section titled “FieldGroup”Layout wrapper that stacks Field components and enables container queries for responsive orientations.
| Prop | Type | Default |
|---|---|---|
className |
string |
<FieldGroup className="@container/field-group flex flex-col gap-6"> <Field>{/* ... */}</Field> <Field>{/* ... */}</Field></FieldGroup>The core wrapper for a single field. Provides orientation control, invalid state styling, and spacing.
| Prop | Type | Default |
|---|---|---|
orientation |
"vertical" | "horizontal" | "responsive" |
"vertical" |
className |
string |
|
data-invalid |
boolean |
<Field orientation="horizontal"> <FieldLabel htmlFor="remember">Remember me</FieldLabel> <Switch id="remember" /></Field>FieldContent
Section titled “FieldContent”Flex column that groups control and descriptions when the label sits beside the control. Not required if you have no description.
| Prop | Type | Default |
|---|---|---|
className |
string |
<Field> <Checkbox id="notifications" /> <FieldContent> <FieldLabel htmlFor="notifications">Notifications</FieldLabel> <FieldDescription>Email, SMS, and push options.</FieldDescription> </FieldContent></Field>FieldLabel
Section titled “FieldLabel”Label styled for both direct inputs and nested Field children.
| Prop | Type | Default |
|---|---|---|
className |
string |
<FieldLabel htmlFor="email">Email</FieldLabel>FieldTitle
Section titled “FieldTitle”Renders a title with label styling inside FieldContent.
| Prop | Type | Default |
|---|---|---|
className |
string |
<FieldContent> <FieldTitle>Enable Touch ID</FieldTitle> <FieldDescription>Unlock your device faster.</FieldDescription></FieldContent>FieldDescription
Section titled “FieldDescription”Helper text slot that automatically balances long lines in horizontal layouts.
| Prop | Type | Default |
|---|---|---|
className |
string |
<FieldDescription>We never share your email with anyone.</FieldDescription>FieldSeparator
Section titled “FieldSeparator”Visual divider to separate sections inside a FieldGroup. Accepts optional inline content.
| Prop | Type | Default |
|---|---|---|
className |
string |
<FieldSeparator>Or continue with</FieldSeparator>FieldError
Section titled “FieldError”Accessible error container that accepts children or an errors array (e.g., from react-hook-form).
| Prop | Type | Default |
|---|---|---|
errors |
Array<{ message?: string } | undefined> |
|
className |
string |
<FieldError errors={errors.username} />When the errors array contains multiple messages, the component renders a list automatically.
FieldError also accepts issues produced by any validator that implements Standard Schema, including Zod, Valibot, and ArkType. Pass the issues array from the schema result directly to render a unified error list across libraries.