Docs
Get started with Joinery
Joinery is a shadcn registry of 86 components and 39 screens for SaaS products. Add the theme once, then add what you need, one file at a time. The code is yours.
Introduction
Every item is a React file built on Tailwind CSS 4 and Radix, with typed props and realistic defaults, so you or your agent change data and wording without touching the markup. Components are the parts (an approval card, a filter menu). Screens are complete in-app pages built from them (billing, members, an agent run).
Free covers 48 components and 10 screens, in Figma and code. Pro unlocks the whole library, the full Figma file and every update, for a one-time price. See pricing.
Installation
Next.js, Vite or any React project with Tailwind CSS 4 and shadcn.
- 1
Set up shadcn on Radix
Joinery is built on Radix. A new project picks it with the flag below; a project already on Radix is ready as is.
npx shadcn@latest init --base radix - 2
Add the Joinery theme
Colours, radius and shadows for light and dark. shadcn names stay as aliases, so your existing components keep working.
npx shadcn@latest add https://joineryui.com/r/theme.json - 3
Create a free account and copy your token
Items install with the registry token of your account. Sign up, then copy the token from your account. Keep it secret, like an API key.
- 4
Save it in your environment
.env.local
JOINERY_TOKEN=jy_live_... - 5
Register the Joinery namespace
components.json
{ "registries": { "@joinery": { "url": "https://joineryui.com/r/{name}.json", "headers": { "Authorization": "Bearer ${JOINERY_TOKEN}" } } } } - 6
Add a component or a screen
Every page shows its command once you are signed in. Dependencies, including other Joinery items, come with it.
npx shadcn@latest add @joinery/kpi-chartEach item lands in its own folder, components/joinery/<name>, and imports in one line:
app/page.tsx
import { KpiChart } from "@/components/joinery/kpi-chart";
Pro access
Pro uses the same token: buying Pro unlocks every Pro item on it, in the CLI, in CI and for your agent.
- 1
Get Pro on your account
Buy Pro while signed in. Your token stays the same, nothing to change in components.json.
- 2
Install any Pro item
npx shadcn@latest add @joinery/agent-run-detail
Theming
One flat set of tokens with shadcn names as aliases. Change a value and every component and screen follows, in light and dark.
The theme adds the tokens to your global CSS under :root and .dark. Change the accent, a radius or a surface there; nothing in the components is hard-coded.
Surfaces and text
Neutral, alpha on ink
Status
Tone on a soft fill
Type
Inter, one family
Radius and elevation
Tokens in use
Same names in Figma
Agents and MCP
Joinery is written to be installed and edited by coding agents: data lives in props, rules live in the docs.
Each page has Open in Claude, Cursor and v0, and a Copy prompt with the install command and the Joinery rules. To let your agent search and install on its own, add the shadcn MCP server with the Joinery namespace above:
.mcp.json
{
"mcpServers": {
"shadcn": { "command": "npx", "args": ["shadcn@latest", "mcp"] }
}
}Then ask in plain words, for example: “Add the Joinery approvals inbox to /approvals and wire it to our API.” An llms.txt index of every item and its props ships at launch.
Figma
The design file and the code share the same variables and names.
Free items are in the community file. Pro includes the full file: every component with its variants, every screen in light and dark, and the foundations as variables, so a token change in Figma maps one to one to the code.
License and updates
You can use Joinery in unlimited personal and commercial projects, including client work and products you sell. You cannot resell or redistribute the library itself as a kit. Pro is paid once and includes every future component and screen.