import { FlowNode } from "@elabs-ai/components-flow";npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-flowPaste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.
Add the brand-ui FlowNode component (from @elabs-ai/components-flow) 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 FlowNode up before writing code: `npx -y @elabs-ai/components-cli docs FlowNode` prints its real props, variants, what it pairs with and what to avoid. 3. If @elabs-ai/components-flow is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-flow` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-flow`). 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
- Raw colors on the node — use flow-node tokens.
Works with
Used inside
Examples
Tones
Every status tone. A non-neutral tone paints the border AND draws its glyph with an `sr-only` name, so the tone never rests on colour alone.
Emphasis
The `featured` emphasis — flow's "look here" node, drawn with a star. On a neutral node it also takes the primary border; a status tone keeps its own border and the star alone says "featured". `emphasis: "default"` is the ordinary node.
Minimal
Node without optional subtitle or kind — minimal data shape.
Selected
Selected node shows a ring highlight.
Connected
Two connected nodes to show handles in context.
Focus Indicator
Regression lock for #312 — `FlowNode` was keyboard-focusable and painted NO focus indicator at all. React Flow puts `tabIndex`/`:focus-visible` on its own wrapper (`.react-flow__node`), one level above the `<div>` this component renders, so the lock reaches the real tab stop by keyboard alone (no synthetic `.focus()`) and reads RESOLVED computed styles on the component's own div — not just a class string — because a previous defect on this exact surface measured 0 changed pixels out of 540,000 while the class list looked correct. Two nodes: a plain one (proves focus alone paints an indicator) and a pre-selected one (proves the NEW focus outline is a distinct, additional layer over the EXISTING `selected` ring — the two never collapse into one ring, and `selected` on its own never gains the outline).
Theming
The tokens each state resolves to. Change the token and every theme follows.
| State | Token |
|---|---|
| selected | ring-2 ring-ring |