All packs
Pack
UI Library Pack
Your own component registry, installable with the shadcn CLI, documented, and consistent enough that agents build with it correctly.
Builders who keep re-copying the same components across projects, agencies standardizing a house style, or anyone who wants to ship a public library.
The stack
| Slot | Pick | Alternative | Why |
|---|---|---|---|
| Registry model | shadcn registry (registry.json, CLI build) | The distribution standard | |
| Primitives | Radix UI | Base UI | Accessible behavior for free |
| Styling | Tailwind v4, CVA, tailwind-merge | Variants without a theme runtime | |
| Theming | tweakcn for token exploration | Visual token editing, exports CSS variables | |
| Docs site | Next.js with MDX | Fumadocs | Live examples next to code |
| Visual testing | Storybook 9 | Ladle | Isolated states, a11y addon |
| Icons | Phosphor or Nucleo | Pick one, never mix | |
| Animation | Motion | ||
| Lint | Ultracite | ||
| Study these | Cult UI, Kokonut UI, Skiper UI, Smooth UI | How the good ones structure variants |
The kickoff prompt
The first lines of the prompt members paste into their agent. The full prompt, the model board, and the setup checklist are inside the portal.
You are setting up a new project. Follow this stack exactly. Do not substitute tools unless one is unavailable, and if you substitute, say so at the end. ## Project A component library called [NAME] with a house style that is [THREE ADJECTIVES]. It ships as a shadcn registry so consumers run `npx shadcn add [REGISTRY URL]/button`. ## Stack - pnpm workspace, TypeScript strict
Get the full pack
Members get the complete prompt, the model board with verified dates, the setup checklist, and every other pack in the club.
