import { Toolbar } from "@elabs-ai/components-ui";npm install @elabs-ai/components-tokens @elabs-ai/components-uiPrompt for your coding agent
Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.
Add the brand-ui Toolbar 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 Toolbar up before writing code: `npx -y @elabs-ai/components-cli docs Toolbar` 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 it for the ordinary control row above a list or table — that is ViewToolbar, where every control is its own tab stop.
- Omitting aria-label — a toolbar is one tab stop, so an unnamed one announces nothing about what it acts on.
- Putting a text input or a link inside it — the roving tabindex swallows the arrow keys those controls need.
- Reaching for it to attach actions to a canvas node — that is NodeToolbar in @elabs-ai/components-ai.
Works with
Examples
Keyboard Navigation
The behaviour the role promises, exercised: Tab reaches the toolbar ONCE, and the arrow keys walk it. A row that claims `role="toolbar"` without this tells a screen-reader user to press keys that do nothing.
Vertical
A rail beside the content it acts on. Arrow keys follow the orientation.
Horizontal
Explicitly horizontal — the default, spelled out.