Skip to content

Now in the official shadcn registry directory.

Start free

Inputs

Five text-field treatments: an underline, a floating label, a focus glow, a filled surface and a leading icon. Each is sized, token-driven and wraps a real input element.

InputsText field

Installation

The styled layer is free and installs like any other ai2 component.

Run the following command

npx shadcn@latest add @ai2/inputs-styled

Dependencies, the @ai2/tokens theme and the component file are installed together.

Variations

5 takes on the same idea. Each is its own export, and every one accepts a size prop (sm, md, lg, xl) aligned to the base Button scale.

Underline

Borderless, with a token underline that grows from the center on focus.

sm
md
lg
xl

Float

A label that floats up on focus or when the field is filled.

sm
md
lg
xl

Glow

A token glow ring blooms on focus.

sm
md
lg
xl

Filled

A filled surface with a token accent bar on focus.

sm
md
lg
xl

Icon

A leading icon that turns a token color on focus.

sm
md
lg
xl

ai2 Inputs: 5 styled variations on the token system

The ai2 Inputs are a set of 5 decorative button variations from the styled layer of the @ai2 design system, built around text-field focus treatments. They are free and MIT licensed, and every color comes from a semantic token, so they theme with the rest of ai2 in light and dark.

Motion runs on framer-motion: focus effects run on token CSS transitions; transform-based ones respect reduced motion. The styled layer is opt-in, so the dependency only lands if you use it; the base components stay lean. Under reduced motion, the underline and label transitions are disabled and the fields still focus.

What is in the ai2 Inputs?

5 exports in one file: Underline, Float, Glow, Filled and Icon. Each renders a native button and takes a size prop (sm, md, lg, xl) aligned to the base Button. They are separate from the base Button on purpose: the base keeps its clean variant, tone and size axes, while the styled layer carries the effects.

You own the file. Copy the one category file and you have all 5 variations, with no runtime dependency on ai2 itself.

Why use it

  • On-system by construction: Every color resolves to an ai2 semantic token, so the buttons follow your theme in light and dark with no extra work.
  • Effect without the sprawl: The decorations live in a dedicated styled file, so the base Button keeps its clean, predictable API.
  • Accessible and honest: Each renders a real button element, keeps a visible focus ring, and respects prefers-reduced-motion.

Features

  • Token-driven color: No hardcoded hex or oklch; the look recolors with your theme tokens.
  • framer-motion: focus effects run on token CSS transitions; transform-based ones respect reduced motion.
  • Reduced-motion aware: Under prefers-reduced-motion, the underline and label transitions are disabled and the fields still focus.
  • Size aligned to the base: Every variation takes sm, md, lg and xl matching the base Button height scale, so styled and base buttons line up in a row.

Production tips

  • Use it for emphasis, not everywhere: Styled buttons draw the eye. Reserve them for the one action you want people to take on a screen, and use the base Button for the rest.
  • Keep labels as verbs: The decoration adds weight, so a clear action label keeps the button scannable.
  • Pick one variation per surface: The variations share a family; using two different ones in the same view competes for attention.

Works with the rest of ai2

The Inputs sit alongside the base Button and the rest of the @ai2 registry. They share the same token file, so a styled action next to a base button or a badge stays visually consistent in both modes.

FAQs

Get new components in your inbox

Component drops, new themes and release notes. No spam, and you can unsubscribe from any email.

© 2026 ai2 design system · MIT licensed · Built with its own components