import { IterationBuilderDialog } from "@elabs-ai/components-editor/markdown";npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-editorPaste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.
Add the brand-ui IterationBuilderDialog component (from @elabs-ai/components-editor) 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 IterationBuilderDialog up before writing code: `npx -y @elabs-ai/components-cli docs IterationBuilderDialog` prints its real props, variants, what it pairs with and what to avoid. 3. If @elabs-ai/components-editor is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-editor` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-editor`). 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
Iterate Builder
Iterate: one value list → one rendered cell per value (stacked).
Pivot With Calc
Pivot with a ```calc cell: objects inside a cell RESOLVE in the live preview (not raw text). With a calc `evaluate` wired, each cell's fence renders a real CalcBlock — the same path the saved block renders through, in matrix and stacked alike.
With Nested Card
A nested `:::card` (with content AFTER it) inside the iteration template. The live preview renders a REAL Card per item — not truncated plain text — and keeps the trailing line, because the builder serializes the directive with a fence longer than the nested one (`outerDirectiveFence`). This is the #223 "other components inside iterations don't render" fix, shown in the dialog the author actually uses.
Bento Builder
Bento layout: the values render as varied-size BentoGrid tiles in the live preview.