Live preview from the React code. Hover the marks, rows and tabs.
Build it with your agent
Copy the setup prompt once per project, then the prompt for this component. Works with Claude Code, Cursor, VS Code and Codex through the Ingot MCP.
1Set up Ingot UI
Set up Ingot UI in this project. 1. Connect the Ingot UI MCP server by running: claude mcp add --scope user --transport http ingot-ui https://mcp.ingotui.com/mcp --header "Authorization: Bearer YOUR_API_KEY" Replace YOUR_API_KEY with my key from https://ingotui.com/account (ask me for it if you don't have it). 2. Call the Ingot UI tool init_project for the Montra system and write every file it returns (token CSS, CLAUDE.md, AGENTS.md, .cursor/rules/ingot.mdc). 3. From now on build UI from Ingot components and the --fu-* tokens, never raw hex colours, and run audit_ui before you finish.
2Build this component
Add the Ingot UI "New scenario modal" (modals, Montra system) to this project. Use the Ingot UI MCP: call get_component_code with slug "montra-new-scenario-modal-3833219" and write the file to the path it returns. Then place it where I need it, keep my existing layout, use the --fu-* tokens for anything new, and run audit_ui when you're done.
Specs
New scenario modal is 168 lines of React with 10 Ingot icons, set in Geist. It needs no packages beyond React, so it works in Next.js, Vite or Remix as pasted, and its colours can be swapped for your Montra tokens.
- Component
<NewScenarioModal />- Size
- 494 × 529 px
- Icons
- Chart increase, Check, Chevron down, Cloud, Megaphone, Plus, Stack2, Trade up, User plus, Close (X) from Ingot Icons
- Type
- Geist, 10px, 10.5px, 11px, 12px, 13px, 15.5px, 18.5px, Regular and Medium
- Colours
- #ffffff#222222#e8e8e8#4996fe#6c6c6c#666d80
- Corner radius
- 2.5px, 3.5px, 4.5px, 5.5px, 7.5px
- Code
- 168 lines of TypeScript, React only, inline styles, icons included
Use it
import { NewScenarioModal } from "./new-scenario-modal";
export default function Page() {
return <NewScenarioModal />;
}Accessibility
Notes for all modals components (category level). Target: WCAG 2.2 AA.
- Keyboard
- Escape closes; Tab stays inside while open; focus returns to the button that opened it.
- ARIA
- role="dialog" and aria-modal="true", labelled by the title (aria-labelledby).
- Focus
- Move focus to the first field or the dialog itself on open.
Before you ship it
- The generated code draws the design only: <div>s, text and aria-hidden icons, with no buttons, inputs, roles or ARIA. That is why it matches Figma closely, and why you add behaviour when you wire it up.
- Wrap it in a dialog primitive (the free Loopo Dialog uses Base UI and does all of the above).
- Make the close icon a <button aria-label="Close">, and footer actions real buttons.
How we test and what’s known: accessibility statement.
