import { Select } from "@elabs-ai/components-ui";npm install @elabs-ai/components-tokens @elabs-ai/components-uiPaste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.
Add the brand-ui Select component (from @elabs-ai/components-ui) to this project. 1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`. 2. Look Select up before writing code: `npx -y @elabs-ai/components-cli docs Select` prints its real props, variants, what it pairs with and what to avoid. 3. If @elabs-ai/components-ui is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui`). If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`. 4. Use it here: [the screen or file, and what it should show] 5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop. 6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.
Avoid
- Using Select for free-form or searchable values — use Combobox when the user may type/search.
- Select without a Label — no accessible name.
Works with
Examples
Clipped Value Gets Title
A long, composed value clipped by `line-clamp-1`, recovered on mouse hover by the automatic native `title` — the zero-extra-code path. The trigger measures its own content, so the `title` appears here and NOT on a short value (see `Default`, which has none). `aria-label` is on the trigger because the value is not a name: the `title` is a hover affordance, never the field's label.
Long Composed Label
The keyboard-reachable recovery: a `Tooltip` composition, which Radix opens on focus as well as hover. `autoTitle={false}` is REQUIRED here — otherwise the native `title` and the Radix tooltip both appear on hover, one on top of the other.
API
SelectContent
SelectItem
SelectLabel
SelectSeparator
SelectTrigger
| Prop | Type | Description |
|---|---|---|
size | "sm" | "default" | |
autoTitle | boolean | Auto-set a native `title` from the trigger's rendered text — but ONLY while that text is actually clipped (default `true`). Set `false` when the trigger is a `TooltipTrigger`: the native tooltip and the Radix one would otherwise both appear on hover. A caller-supplied `title` also disables it (an explicit `title` is never overridden). |
Theming
The tokens each state resolves to. Change the token and every theme follows.
| State | Token |
|---|---|
| focus | focus-ring — the compound indicator: a ring-2 in --ring plus a 1px --ring-contour outline (#67) + ring-offset-1 ring-offset-background |
| disabled | opacity-50 |