brand-ui — FilterChip

import { FilterChip } from "@elabs-ai/components-ui";

Install

npm install @elabs-ai/components-tokens @elabs-ai/components-ui

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt 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 FilterChip 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 FilterChip up before writing code: `npx -y @elabs-ai/components-cli docs FilterChip` 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

5 live examples

With Count

A count with a caller-supplied label — "excluded 1,204", locale-formatted.

Bare Count

A bare count with no `countLabel` — just the formatted number.

Multiple Chips

Long Label With Count

A label long enough to overflow a 280px container (#284). The label truncates with an ellipsis; the count stays fully visible — CSS `text-overflow: ellipsis` can only reach the label's own span, never the count's sibling element.

API

`FilterChip`

Prop	Type	Description
`label`required	`string`	Label-in-value text — `"Status: Failed"`, never `"Status = failed"` and never a bare `"Failed"`. The caller composes the string so the chip reads as a sentence fragment out of context (and in a screen reader).
`trailing`	`string`	Short, non-shrinking secondary text — a count, a unit (`"excluded 1,204"`). A second text slot rather than folding it into `label` (#284): `label` is the shrinkable, safe-to-truncate part; `trailing` is short and fixed-width and must never lose characters to the ellipsis. Same shape as `TurnStatus`'s and `TerminalWorking`'s `trailing` slot — a fixed-width companion beside a truncating label. Composed into the accessible name after `label` (`"Remove filter: <label> · <trailing>"`), so the byte- identical name from before this slot existed is unchanged. Trade-off: `trailing` is `shrink-0`, so an extremely narrow container now truncates `label` down to nothing before it touches `trailing`. That is the right default — the count is short and fixed, the label is the long, prose-shaped part — but it is a choice, not a free win.
`onRemove`required	`() => void`	Remove this filter. The WHOLE chip is the remove control — see below.

Also accepts: Omit<ButtonHTMLAttributes<HTMLButtonElement>, "children">