Why before hydration
Streaming SSR leaves a gap between first paint and hydration — one per late Suspense boundary. There, a useState accordion is visible but inert; a <details> one already works.
29 of the 44 components are Tier 0: they ship 0 kB of client JavaScript and pass their full interaction suite with scripting disabled. The others document their cost and pre-hydration behavior.
Who it is for
Good fit: server rendering, pages that work before hydration, and your own styling. Components ship semantic markup, a documented data-* contract and no visual styles.
Poor fit: a themed kit that looks finished out of the box, or a client-only app — a hydration-first library suits you better.
How it is organized
Five layers — hooks, core, elements, components and optional styles — each published on its own, none importing a layer above it. Components are Server Components by default; the import path shows every client boundary.
Start here
- Installation — one package and one required stylesheet.
- AI agents — build pages with the
/uiifyskill. - Components — 44 live playgrounds with props and measured budgets.
- Proof — the release gates behind every published number.