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 Abotix 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 "Tabs" (navigation, Abotix system) to this project.

Use the Ingot UI MCP: call get_component_code with slug "abotix-tabs-823950" 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

Tabs is 30 lines of React with no icons, set in Inter. 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 Abotix tokens.

Component
<Tabs />
Size
373 × 32 px
Icons
None
Type
Inter, 12px, 14px, Medium
Colours
#8a8a8a#f2f2f2#ffffff#ededed#2563eb#6692f1
Corner radius
8px, 9px
Code
30 lines of TypeScript, React only, inline styles, icons included

Use it

import { Tabs } from "./tabs";

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

Accessibility

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

Keyboard
Tab through links in order; Enter follows. Tabs: arrow keys between tabs.
ARIA
<nav aria-label>, links as <a>, aria-current="page" on the active item. Tab bars use role="tablist".
Focus
A visible focus ring on every item.

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.
  • Turn the drawn items into links or your router’s Link; use Loopo Sidebar navigation or Tabs as the pattern.

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

More navigation in Abotix

Copy to Figma (Pro)Copy React code (Pro)Save
Copy to Figma (Pro)Copy React code (Pro)Save
Tabs wrapAbotix Pro
Copy to Figma (Pro)Copy React code (Pro)Save
Toolbar leftAbotix Pro
Copy to Figma (Pro)Copy React code (Pro)Save
Toolbar rightAbotix Pro