import { Meter } 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 Meter 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 Meter up before writing code: `npx -y @elabs-ai/components-cli docs Meter` 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.
Examples
Sizes
The three heights; `xs` is the inline confidence rung beside a printed percentage.
Tones
A quantity that IS a verdict takes a status tone — always with `aria-valuetext`.
With Marker
A ceiling drawn as a tick; the fill runs past it in the destructive rung.
Segmented
“4 of 5 signals held” — five discrete facts drawn as five countable cells.
API
Meter
| Prop | Type | Description |
|---|---|---|
valuerequired | number | The measured value. Clamped to `[min, max]` for the fill; reported as-is to AT. |
min | number | Range floor. Default 0. |
max | number | Range ceiling. Default 100. |
segments | number | Draw the track as this many discrete cells instead of one continuous fill; the value fills `round((value − min) / (max − min) × segments)` of them. For "n of m" facts pass `segments={m}` with `max={m}`. |
marker | number | Reference point on the same scale as `value` (a ceiling, a target), rendered as a thin vertical tick on the track. Unset renders no tick. |
markerLabel | string | What `marker` represents, already localized ("ceiling $500"). Appended to the accessible value text; a caller-supplied `aria-valuetext` always wins. |