import { NavigationMenu } from "@elabs-ai/components-ui";npm install @elabs-ai/components-tokens @elabs-ai/components-uiPaste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.
Add the brand-ui NavigationMenu 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 NavigationMenu up before writing code: `npx -y @elabs-ai/components-cli docs NavigationMenu` 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
Keyboard focus
Locks WCAG 1.4.11 (#308): `NavigationMenuTrigger` painted `hover:` and `focus:` identically, with the fill alone (no ring/outline layer) as the only signal — not a visible indicator. Keyboard (Tab) focus must now paint a real compound ring (`focus-ring`: a `boxShadow` layer, or a non-zero, non-`none` `outline`), and the resting trigger must carry neither layer. NOTE: this does not additionally assert "a mouse click shows no ring" — confirmed BOTH before and after this fix (and independent of story order), a real click on this trigger still lands the browser in `:focus-visible` in this environment. `NavigationMenuTrigger` sits in Radix's roving- tabindex collection, which manages its focus imperatively rather than via the browser's native click-to-focus default action — the same class of "script-triggered focus" `CompoundFocusIndicator` (`button.stories.tsx`) already notes as unreliable against `:focus-visible`. Converting `focus:` to `focus-visible:` is still the correct, spec-aligned fix (mouse-click suppression is now possible, keyed on the browser's own determination); whether Radix's roving-focus internals let the browser actually make that determination for a plain click is a separate, deeper defect — flagged as a residual follow-up, not fixed here.