A component library your AI agent actually reads

What it does

UI SDK splits UI components into composable behaviors — keyboard navigation, focus management, selection, dismissal, popups, drag and drop, plus the ARIA wiring they require. These live in a framework-agnostic core (@ui-sdk/core), with adapters for React, Vue, Svelte, Solid, and Web Components. You define a primitive once (state, API, slots) and render it identically in all five frameworks via createParts.

The interesting bit

The pitch is explicitly agent-first: the README says “you don’t need to learn how to write this. Your agents will.” There’s even a one-command skill install so an MCP-connected agent can use the library directly. The bet is that accessibility logic is too error-prone for humans to hand-roll and too well-specified for agents to get wrong — so encode it once and let the machines compose it.

Key highlights

• Behaviors like createPopup, createSelection, and createTypeahead are the building blocks, not pre-styled components — it’s headless.
• One primitive definition, five framework renderers, including Web Components via custom elements.
• Ships as an agent skill, aligning with the WebMCP topic the repo tags.
• Accessibility (ARIA, focus recovery) is treated as core behavior, not an afterthought.

Caveats

• Beta status, with Vercel beta terms attached — APIs and behavior may change before GA.
• The primitive-definition DSL is verbose; the README leans on “your agent will handle it” rather than showing why a human would want to.

Verdict

Worth a look if you’re building agent-driven UI tooling or want truly framework-agnostic headless behaviors. If you just want a dropdown component, Radix or Headless UI will get you there with less ceremony.