Comparison · v0.2.1
VLLNT UI vs shadcn/ui
TLDR
shadcn/ui is the industry standard. VLLNT UI is a younger sibling that takes the same registry idea further: more components, an agent-first surface (/llms.txt, /mcp, richer JSON descriptors), and a hybrid install model that dedupes shared primitives via @vllnt/ui.
If you want maximum community signal and the largest pool of third-party tutorials and templates, shadcn/ui wins. If you want the broadest curated component set and a registry that AI agents can read directly, VLLNT UI wins.
VLLNT UI now includes a starter kit gallery for finished app shells built from the registry.
Side-by-side
| Attribute | VLLNT UI | shadcn/ui |
|---|---|---|
| Component count | 225 components | ~50 components |
| Install model | shadcn CLI against /r/<name>.json | shadcn CLI against ui.shadcn.com/r |
| You own the source after install | Yes | Yes |
| Sibling-component resolution | Hybrid: leaf source + @vllnt/ui peer dep for siblings | All source inlined per component |
| /llms.txt agent index | Yes — llmstxt.org compliant | No |
| MCP server | Yes — ui.vllnt.ai/mcp (search/get/list tools) | No |
| Per-component a11y schema in JSON | Yes — keyboard map, ARIA roles, focus model | No |
| Per-component examples in JSON | Yes — code-as-data, agent-readable | No |
| Per-component props schema in JSON | Yes — TSDoc-shaped | No |
| version + stability per component | Yes (stable / beta / experimental / deprecated) | No |
| Theming | CSS variables + design tokens (DESIGN.md) | CSS variables |
| Accessibility primitives | Radix UI | Radix UI |
| Variant system | CVA | CVA |
| Community size | Smaller, growing | Massive — millions of installs |
| Namespace recognition | @vllnt/ui (newer) | shadcn (industry standard) |
| Tutorials + content | Limited (young project) | Extensive — countless videos, blogs, courses |
| Templates / starter kits | Curated app templates for Next.js, dashboards, SaaS, AI chat, and docs | Many official + community templates |
| License | MIT | MIT |
When to pick which
Pick shadcn/uiwhen you want the most-validated choice, need a large pool of tutorials, or are building something that benefits from being “just shadcn”.
Pick VLLNT UI when you need components beyond the shadcn core (timelines, maps, AI compounds, runtime overlays, canvas primitives), when AI agents are part of your authoring flow, or when you want the registry data structured enough to query programmatically.
The honest answer: many projects use both. shadcn/ui as the baseline, VLLNT UI for the families shadcn doesn’t cover. Same install model: they coexist cleanly.