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 "Page header, Approvals" (headers, Spendix system) to this project.

Use the Ingot UI MCP: call get_component_code with slug "spendix-page-header-approvals-3631994" 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

Page header, Approvals is 50 lines of React with 4 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 Spendix tokens.

Component
<PageHeaderApprovals />
Size
1154 × 46 px
Icons
Square rounded check, Check, Sliders horizontal, User check from Ingot Icons
Type
Geist, 14px, 18px, Regular and Medium
Colours
#ffffff#0f172a#dfe1e6#000000#ededed#64748b
Corner radius
8px
Code
50 lines of TypeScript, React only, inline styles, icons included

Use it

import { PageHeaderApprovals } from "./page-header-approvals";

export default function Page() {
  return <PageHeaderApprovals />;
}

Accessibility

Notes for all headers components (category level). Target: WCAG 2.2 AA.

Structure
The page title should be the page’s <h1>, section titles <h2>.
Keyboard
Actions (buttons, search, menus) reachable with Tab in visual order.
ARIA
Icon-only buttons need an aria-label.

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 the drawn title for a heading element and the action shapes for buttons.

How we test and what’s known: accessibility statement.

More headers in Spendix

Copy to Figma (Pro)Copy React code (Pro)Save
Page headerSpendix Pro
Copy to Figma (Pro)Copy React code (Pro)Save
Header cardSpendix Pro
Copy to Figma (Pro)Copy React code (Pro)Save
Copy to Figma (Pro)Copy React code (Pro)Save