Every StyleKit style is published as a shadcn registry theme. You can install any style's color theme — light and dark — into an existing shadcn project with a single command, no copy-paste required.
In any shadcn project, run:
npx shadcn add https://stylekit.top/r/glassmorphism.jsonReplace glassmorphism with the slug of any style. The shadcn CLI fetches the URL, reads the theme item, and injects its CSS variables into your globals.css. After it finishes, your project's components pick up the StyleKit palette for both light and dark mode.
-
A project that has already been initialized with shadcn (it has a
components.jsonand aglobals.css). -
The project must contain a
tsconfig.json. The shadcn CLI inspectstsconfig.jsonto resolve paths; without it the command fails with:Couldn't find tsconfig.jsonIf you hit this, add a
tsconfig.jsonto the project root (even a minimal one) and run the command again.
Each style is served as a shadcn registry:theme item. A theme item ships no source files — it only carries CSS variables, which the CLI writes directly into your stylesheet. Two sets are applied:
cssVars.light— written to your:rootblockcssVars.dark— written to your.darkblock
The variables cover the standard shadcn theme tokens, derived from the style's own design tokens:
| Group | Variables |
|---|---|
| Surfaces | background, foreground, card, card-foreground, popover, popover-foreground |
| Brand | primary, primary-foreground, secondary, secondary-foreground, accent, accent-foreground |
| Support | muted, muted-foreground, destructive, destructive-foreground |
| Form / focus | border, input, ring |
| Shape | radius |
Values are stored as bare HSL channels (for example 0 0% 100%). When you install into a Tailwind v4 project, the shadcn CLI wraps each value as hsl(...) and generates the matching @theme inline block automatically, so the variables are usable as Tailwind utilities without extra configuration. Tailwind v3 projects work too — the CLI adapts the output to the detected setup.
A slug is the kebab-case identifier in a style's URL, for example glassmorphism, neo-brutalist, or bento-grid (https://stylekit.top/styles/neo-brutalist).
You can list every available style — all 146 — from the registry index:
curl https://stylekit.top/registry.jsonOr browse them visually in the styles gallery.
| Endpoint | Returns |
|---|---|
GET /registry.json |
The registry index: every style as a lightweight { name, type, title, description } entry. |
GET /r/<slug>.json |
One style as a full shadcn registry:theme item, including cssVars for light and dark. |
Both responses follow the official shadcn schemas (registry.json and registry-item.json).
{
"$schema": "https://ui.shadcn.com/schema/registry.json",
"name": "stylekit",
"homepage": "https://stylekit.top",
"items": [
{
"name": "glassmorphism",
"type": "registry:theme",
"title": "Glassmorphism",
"description": "..."
}
]
}{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "glassmorphism",
"type": "registry:theme",
"title": "Glassmorphism",
"description": "...",
"cssVars": {
"light": {
"background": "0 0% 100%",
"foreground": "0 0% 3.9%",
"primary": "...",
"radius": "0.5rem"
},
"dark": {
"background": "0 0% 3.9%",
"foreground": "0 0% 98%",
"primary": "..."
}
},
"files": []
}| Symptom | Cause | Fix |
|---|---|---|
Couldn't find tsconfig.json |
The target project has no tsconfig.json. |
Add a tsconfig.json to the project root and re-run. |
Unknown style: <slug> (404) |
The slug does not exist. | Check the slug against /registry.json or the styles gallery. |
| Variables not applied | The project was never initialized with shadcn. | Run npx shadcn init first, then add the theme. |
- shadcn registry docs
STYLE_AUTHORING.md— how StyleKit styles (and their tokens) are defined.