Kumo

Reach for Kumo over shadcn/ui when you are building an infrastructure or admin console rather than a marketing site — it already ships the pieces shadcn makes you assemble: charts (ECharts timeseries, sankey, geo maps), a Flow node/connector diagram, sidebar, command palette, sensitive-input, meter and resource-list blocks, all on the same Base UI primitives so the two genuinely compose. Read the repo's AGENTS.md before writing a line: styling is lint-enforced to semantic tokens only, raw Tailwind colors like `bg-blue-500` and any `dark:` variant will fail CI, and dark mode comes from `light-dark()` on CSS custom properties. Watch the peer deps — echarts 6, @phosphor-icons/react, zod 4 and React 18/19 are all peers you must install yourself, it is ESM-only on Node 24+, and kumo-ui.com returns 403 to fetchers, so enumerate components from the repo tree or `npx @cloudflare/kumo ls` instead of scraping the docs.

Why it is here. A real production design system from a major infrastructure company, MIT-licensed and shipped with a machine-readable knowledge base and an agent skill — that combination is close to unique.