# Textarea

Follows: **Surface Treatment**, **Typography Application**, and **Interaction States** from [`../philosophy.md`](../interface.md), plus the package-first rules in [`component-guide.md`](selection.md).

`Textarea` is the multiline companion to `Input`. Use it for authored or pasted text that must remain editable in place, such as Markdown source, instructions, or evaluator criteria.

## Rules

- At rest, use the same subtle boundary contrast as panels and dropdowns; the legacy `--border-default` name does not mean a stronger input outline. Select the reference from the textarea fill and its immediate surroundings.

- Pair it with a persistent label. Placeholder text is only a format hint.
- It begins at a purposeful minimum height and grows by user resize, not by autoresize animation.
- Use the monospace family for code, Markdown, structured text, and prompts; create a rich editor only when syntax-aware editing is explicitly required.
- Follow the same border, focus ring, disabled state, and color rules as `Input`.

## Floating title

Use `fieldLabel` for the persistent title. In an empty, inactive textarea it sits at the top left on the first text line, regardless of field height or user resizing. On focus it floats into a notch in the top border, exposing the placeholder hint. A populated textarea keeps its title floated. Use the same named motion tokens, notch background, and disabled/focus semantics as Input. Placeholder hints begin on the first line; do not vertically center multiline labels.

Use `textStyle="prose"` for descriptions and `textStyle="source"` for Markdown instructions. The source style remains the default for compatibility. Keep the title in the shared sans-serif field-label typography.
