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 Spendix 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 "Footer card, Approve with ⌘ Enter" (cards and panels, Spendix system) to this project. Use the Ingot UI MCP: call get_component_code with slug "spendix-footer-card-approve-with-enter-3632314" 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
Footer card, Approve with ⌘ Enter is 34 lines of React with 1 Ingot icon, 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 Spendix tokens.
- Component
<FooterCardApproveWithEnter />- Size
- 440 × 57 px
- Icons
- Check from Ingot Icons
- Type
- Geist, 12px, 14px, Regular and Medium
- Colours
- #ffffff#fafafa#e2e8f0#64748b#dfe1e6#0f172a
- Corner radius
- 8px
- Code
- 34 lines of TypeScript, React only, inline styles, icons included
Use it
import { FooterCardApproveWithEnter } from "./footer-card-approve-with-enter";
export default function Page() {
return <FooterCardApproveWithEnter />;
}Accessibility
Notes for all cards and panels components (category level). Target: WCAG 2.2 AA.
- Structure
- The card title should be a heading at the right level for your page.
- Keyboard
- Every action in the card is a button or link, reachable with Tab.
- ARIA
- Icon-only actions need an aria-label; decorative icons stay aria-hidden.
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.
- Swap drawn buttons and links for real ones; if the whole card is clickable, use one link and keep other actions outside it.
How we test and what’s known: accessibility statement.
