shadcn/ui

shadcn/ui scores 7 of 8 and shares fifth place with Chakra UI and Shopify Polaris. The ratings come from its own docs and repository, and it has no tie to Simbolik. It is not a package you install and call; it is source code you copy, which shapes both its strengths and its one lost point.

The first 4 signs make the score out of 8: 2 points for a Yes, 1 for a Partly, none for a No. Typed props are rated beside them and left out of the score.

• Design tokens: Partly, 1 point. The theme is CSS variables such as --background and --primary. Color values are also served as JSON under /r/colors/, but no page documents them as a design token feed, and there is no file in the W3C format or package of design tokens. Proof: shadcn/ui, theming (opens in a new tab), checked November 8, 2026.
• Agent access: Yes, 2 points. npx shadcn@latest mcp starts the official server, which browses, searches and installs components from registries, and registry owners get it for their own components at no cost. Proof: shadcn/ui, MCP server (opens in a new tab), checked November 8, 2026.
• Docs: Yes, 2 points. An llms.txt, and every page as Markdown when you add .md. There is no llms-full.txt. Proof: shadcn/ui’s llms.txt (opens in a new tab), checked November 8, 2026.
• Guidance: Yes, 2 points. npx skills add shadcn/ui installs a skill that reads your components.json, runs shadcn info --json and has rules for the CLI and for customizing. Proof: shadcn/ui, skills (opens in a new tab), checked November 8, 2026.
• Typed props: Yes, not scored. Components are TypeScript files copied into your project, and each docs page has an API reference of props such as variant and size. Proof: Button, as Markdown (opens in a new tab), checked November 8, 2026.

Teams that want to own their component code and let agents install, read and change it. Because the source lands in your repository, an agent works on files it can open, and your changes are never overwritten by a package update.

• The JSON colors. Do not build on the files under /r/colors/ until shadcn documents them; the research found no page that does.
• Moving addresses. The docs now split components into base, Radix and Aria versions, and some page addresses have already moved. Agents that saved old links will hit redirects.
• Ownership cuts both ways. Copied code is yours to maintain; fixes upstream do not reach it by themselves.

The lost point is the cheapest kind to win back, and it sits on your side once the code is copied. Export the CSS variables your project uses to a JSON file in the W3C format, with a type and one line of purpose per design token, and keep it next to components.json. A build tool such as Style Dictionary can then write the CSS from that file, so the data is the source and the variables follow. Design tokens as data walks through the file, and the best AI-ready design systems, ranked show what the 2 points are worth.