UI SDK (vercel-labs/ui)
The ui-sdk skill from vercel-labs/ui guides coding agents to build accessible, agent-ready interfaces using @ui-sdk/core primitives across React, Vue, Svelte, Solid, and Web Components—enforcing per-component entry imports, accessible labeling, @layer ui-sdk styling, createAgent/WebMCP controls, and real-browser verification.
Explore the workflow and limits ↓What to use it for
Use the ui-sdk skill from vercel-labs/ui whenever a project uses @ui-sdk/* to assemble forms, settings pages, command palettes, or custom headless primitives with keyboard navigation, focus recovery, ARIA, SSR, RTL, and agent-callable actions.
At commit 98ba9fd, @ui-sdk/core powers adapters for React, Vue, Svelte, Solid, and Web Components, plus an optional @ui-sdk/core/web.css baseline stylesheet and createAgent / WebMCP bindings.
Good fit: frontend and full-stack teams building design systems or agent-operable UIs across five frameworks without styling lock-in. Choose another tool if you are looking for LLM streaming hooks (vercel/ai AI SDK) or a pre-styled Tailwind template library.
Installation & versioned docs lookup
Install @ui-sdk/core plus your framework adapter (@ui-sdk/react, @ui-sdk/vue, @ui-sdk/svelte, @ui-sdk/solid, or @ui-sdk/web), then add the skill:
npm install @ui-sdk/react @ui-sdk/core
npx skills add vercel-labs/ui --skill ui-sdk
The skill instructs agents to read node_modules/@ui-sdk/<framework>/docs/llms.txt first and load only the component Markdown pages needed—rather than reading compiled dist/*.js bundles. For Nuxt 4+ apps, add @ui-sdk/vue to modules in nuxt.config.ts. For no-bundler pages or Artifacts, load https://ui-sdk.dev/web.js and web.css and consult https://ui-sdk.dev/web.md.
Composition, styling & agent-ready guardrails
packages/core/skills/ui-sdk/SKILL.md enforces strict API and accessibility rules:
- Per-component imports & composition: import from component entries such as
@ui-sdk/react/select, never from package roots or@ui-sdk/core/internal/*. Swap elements withrender, never anasprop. - Styling & contrast: place
@layer ui-sdk;at the top of global CSS before@import "tailwindcss", targetdata-slotanddata-open/data-pressedattributes rather than inline styles, and verify 4.5:1 text and 3:1 control contrast in a real browser. - Agent-ready controls (
agent-ready.md): give every interactive control a unique accessible name (FieldLabel,SelectLabel,DialogTitle, oraria-label), putkeepMountedon multi-trigger dialogs, avoid sharing one Menu across rows, and verify with typecheck plus agent/keyboard tests before wrapping up.