Silica UI
A design system for Tailwind CSS v4, in two core layers plus a family of optional composite packages:
@wizeworks/silicaui— the "daisyUI" layer. A Tailwind v4 plugin that ships 76 semantic, themeable component classes (btn,btn-primary,card,dialog, …) driven by an extensible OKLCH color-token engine. CSS-first: notailwind.config, just@plugin "@wizeworks/silicaui"in your CSS. Framework-agnostic.@wizeworks/silicaui-react— the "shadcn" layer. 90 thin React components that apply Silica classes and delegate interaction behavior to Base UI.@wizeworks/silicaui-html— the framework-neutral node-tree source + HTML projection powering the visual builder and any structured host.- Composite packages — heavier engines (charts, tables, rich text, drag-and-drop, resizable panels) kept out of the core so it stays dependency-light; install them only when you need them.
Status
Early, but growing fast: 76 CSS component families, 90 React components, a
full theme-customization API (extensible N-color engine, optional class
prefixing), and five composite packages wrapping best-in-class engines. See
examples/playground.
pnpm install
pnpm dev # open the playground
Packages
@wizeworks/silicaui-builder (the visual builder) lives in this monorepo but is not yet
published — it's mid-refactor onto the React component set above.
Contributing
This is a pnpm workspace. Every change that should ship gets a changeset:
pnpm changeset # describe what changed and which packages it affects
Landing that changeset on main is the whole release. CI builds the workspace
once, verifies it, and — only if everything is green — versions the packages,
publishes them to npm, tags them, cuts a GitHub Release, and rolls
silicaui.com. There is no "Version Packages" PR to merge
and nothing to click. All twelve packages are fixed, so they always move
together. See .github/workflows/ci.yml.
Links
- silicaui.com — website & docs
- GitHub repo
- Issues