import { ConfirmDialog } 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 ConfirmDialog 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 ConfirmDialog up before writing code: `npx -y @elabs-ai/components-cli docs ConfirmDialog` 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
Escape Cancels
Escape cancels — the keyboard route to the safe outcome.
Loading
The request is in flight. The action swaps in a spinner and reports `aria-busy`, but it is never pre-disabled — and repeat activations are swallowed, so a double-click cannot fire the deletion twice.
Neutral Tone
A neutral, non-destructive confirmation — same contract, calmer action.
API
ConfirmDialog
| Prop | Type | Description |
|---|---|---|
openrequired | boolean | Controlled open state — the app owns it. |
onOpenChangerequired | (open: boolean) => void | Fires on cancel, Escape, and any other Radix dismissal. |
titlerequired | ReactNode | What is about to happen, as a question or a statement. |
descriptionrequired | ReactNode | The consequence, spelled out. **Required**: `AlertDialogContent` is inaccessible to screen-reader users without a description (Radix warns), and a confirmation whose only text is its title cannot state what is at stake. |
confirmLabel | ReactNode | The confirm action's label. States the CONSEQUENCE ("Delete skill"), never "OK" — a label that names the outcome is the last chance to catch a mistake. Defaults to a generic "Confirm", which you should almost always replace. |
cancelLabel | ReactNode | The safe action's label. Defaults to "Cancel". |
onConfirmrequired | () => void | Runs when the confirm action is activated. |
onCancel | () => void | Runs when the safe action is activated (in addition to `onOpenChange`). |
tone | "default" | "destructive" | Visual tone of the CONFIRM action only. The dialog chrome never changes. |
loading | boolean | The confirm request is in flight: the action swaps its label for a spinner and reports `aria-busy`. It deliberately stays ENABLED (`.claude/rules/interaction-guidelines.md`, Forms — a submit is never pre-disabled); repeat activations are ignored while it is set. |
children | ReactNode | Extra body content between the description and the actions. |
className | string |