Changelog

You can now turn any public GitHub repository into a registry.

Add a registry.json file at the root of the repository, define the items you want to distribute, and users can install them directly from GitHub with the shadcn-svelte CLI.

pnpm dlx shadcn-svelte@latest add <username>/<repo>/<item>

For example, to install the project-conventions item from the acme/toolkit repository:

pnpm dlx shadcn-svelte@latest add acme/toolkit/project-conventions

GitHub registries are source registries. You do not need to run shadcn-svelte registry build, publish generated item JSON files, or set up a registry server. The CLI reads the root registry.json, resolves include entries, finds the requested item, and installs the files declared by that item.

Distribute anything

Registry items are not limited to components. A GitHub registry can distribute components, hooks, utilities, design tokens, feature kits, project conventions, agent instructions, testing setup, CI workflows, release workflows, templates, codemods, migration kits, and other project files.

For example, a repository can expose a project-conventions item that installs shared docs, editor settings, and agent instructions:

{
  "$schema": "https://shadcn-svelte.com/schema/registry.json",
  "name": "acme-toolkit",
  "homepage": "https://github.com/acme/toolkit",
  "items": [
    {
      "name": "project-conventions",
      "type": "registry:item",
      "files": [
        {
          "path": "AGENTS.md",
          "type": "registry:file",
          "target": "~/AGENTS.md"
        },
        {
          "path": ".editorconfig",
          "type": "registry:file",
          "target": "~/.editorconfig"
        },
        {
          "path": "docs/conventions.md",
          "type": "registry:file",
          "target": "~/docs/conventions.md"
        }
      ]
    }
  ]
}

Commands

GitHub registry addresses work with the registry commands supported by shadcn-svelte.

Validate a GitHub registry:

pnpm dlx shadcn-svelte@latest registry validate acme/toolkit

Install an item:

pnpm dlx shadcn-svelte@latest add acme/toolkit/project-conventions

See the GitHub Registries docs for the full guide.

Introducing Rhea, a new shadcn-svelte style. A more compact Luma. Smaller spacing. Denser surfaces. Built for focused product interfaces.

Try Rhea in shadcn-svelte/create

Rhea started from a simple request we've heard a lot: Luma, but more compact. We looked at how people were using the new styles and what they were asking for, and the pattern was clear. A lot of teams wanted the softness and shape of Luma with tighter spacing, smaller controls, and more information density.

Rhea keeps the same rounded foundation, but makes it more compact for product interfaces where space matters. Buttons, inputs, menus, cards, and lists all sit a little tighter so the UI can carry more without feeling crowded.

Why a new style?

We considered making this a spacing tweak for Luma, but --spacing is a multiplier. Changing it would change what familiar utilities mean across your app. p-2, w-4, and m-16 would no longer mean the same size.

That tradeoff felt wrong. Compactness should not force you to relearn Tailwind's spacing scale or wonder whether a utility means something different in one style than another.

So Rhea is a new style instead. It lets us adjust component sizes, gaps, and density directly while keeping the underlying utility scale predictable.

Available now in shadcn-svelte/create.