Textarea Component

Inputs textarea shadcn/ui textarea

component

Overview

Collect longer text without making the form feel heavy. This entry is written as a registry-ready component spec: useful to humans, copyable by AI tools, and easy to map to a future shadcn registry item.

structure

Anatomy

Root
Label
Control
Helper text
Error text

visual API

Variants

default
muted
error
disabled

behavior

States

default
hover
focus-visible
disabled
error
filled

copy-ready details

Component spec

tokens

Styling tokens

radius8px or less

border1px solid rgba(237, 237, 236, 0.14)

backgroundneutral surface with subtle contrast

foregroundhigh-contrast text

mutedForegroundsecondary text at 68-74% contrast

focusRing2px neutral ring with offset

shadowsoft elevation only when interaction needs tactility

motionDuration120ms-220ms

a11y

Accessibility notes

Use semantic HTML or the matching Radix primitive before custom roles.
Keep focus-visible states obvious without adding decorative glow.
Ensure icon-only controls have an accessible label.
Do not rely on color alone for state or validation.

shadcn/ui textarea

shadcn implementation

No extra primitive required beyond React and Tailwind.

Use shadcn tokens for background, border, ring, muted text, radius, and state variants. Keep component-specific classes local and copyable.

optional adapter

HeroUI mapping

Textarea can map to a HeroUI component only as an optional adapter. Keep UnBoring copy and token language framework-neutral.

AI Prompt

Create a Textarea component for an AI-generated interface using shadcn-style composition. Use shadcn/ui textarea as the implementation base. The component should support default, muted, error, disabled variants and default, hover, focus-visible, disabled, error, filled states. Include clear anatomy for Root, Label, Control, Helper text, Error text. Keep the visual language black, white, and gray with subtle borders, practical spacing, accessible focus states, and no decorative noise.

Negative Prompt

Do not invent a custom component API when shadcn/ui textarea already covers the base behavior. Avoid random gradients, oversized radii, unclear disabled states, missing labels, icon-only controls without accessible names, and variants that change layout unexpectedly.

Implementation Notes

Base: shadcn/ui textarea
Primitive: none
Tailwind: Use shadcn tokens for background, border, ring, muted text, radius, and state variants. Keep component-specific classes local and copyable.
Dependency: No extra primitive required beyond React and Tailwind.

Tokens

{
  "id": "textarea",
  "category": "components",
  "trigger": "user interaction",
  "target": "textarea",
  "feeling": [
    "polished",
    "practical",
    "precise"
  ],
  "palette": [
    "black",
    "white",
    "gray"
  ],
  "radius": "8px or less",
  "border": "1px solid rgba(237, 237, 236, 0.14)",
  "background": "neutral surface with subtle contrast",
  "foreground": "high-contrast text",
  "mutedForeground": "secondary text at 68-74% contrast",
  "focusRing": "2px neutral ring with offset",
  "shadow": "soft elevation only when interaction needs tactility",
  "motionDuration": "120ms-220ms"
}

Usage notes

Short guidance for humans and AI tools before copying the component.

What is this component for?

Textarea helps teams collect longer text without making the form feel heavy. It should feel like a reusable product primitive, not a one-off decoration.

How should I implement it?

Start from shadcn/ui textarea. No extra primitive required beyond React and Tailwind. Keep variants token-driven and keep states predictable.

What should I avoid?

Do not invent a custom component API when shadcn/ui textarea already covers the base behavior. Avoid random gradients, oversized radii, unclear disabled states, missing labels, icon-only controls without accessible names, and variants that change layout unexpectedly.

Textarea