import { SkipLink } 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 SkipLink 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 SkipLink up before writing code: `npx -y @elabs-ai/components-cli docs SkipLink` 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
Realistic Shell
Finding 3 (task-11f-brief.md): the `Default` story above has no competing focusable furniture, so its own "the link comes first" assertion is vacuous — it would pass on a page with the link anywhere in the tab order, because there is nothing else to come before. This story composes the link inside a realistic shell — a `CommandTrigger` plus real nav `<a>`/`<button>` elements genuinely competing for first place — and a real `<main id="main-content" tabIndex={-1}>` target. It proves the tab-order claim for real: tabbing from a blurred page lands on the skip link ahead of every one of those competing controls. The second claim — that ACTIVATING the link moves real focus rather than merely scrolling — is only checked at the precondition level here (see the comment in the play function); this harness cannot exercise the activation itself.
API
SkipLink
| Prop | Type | Description |
|---|---|---|
targetId | string | The id of the landmark to jump to. Defaults to "main-content". |