Project docsneobrutal-ui

Registry

How neobrutal-ui publishes editable components, recipes, templates, and theme files.

On this page5 sectionsBack to top

neobrutal-ui is published as a shadcn-compatible source registry. The production catalog is available at neobrutal-ui.andongmin.com/r/registry.json.

#Namespace

Add the namespace once in components.json.

{
  "registries": {
    "@neobrutal-ui": "https://neobrutal-ui.andongmin.com/r/{name}.json"
  }
}

The {name} placeholder maps @neobrutal-ui/button to https://neobrutal-ui.andongmin.com/r/button.json.

#Item types

  • Base installs the shared tokens, Tailwind mappings, aliases, and core dependencies.
  • Components install individual UI source files and their declared dependencies.
  • Recipes combine multiple components for patterns such as comboboxes and date pickers.
  • Templates install focused page and block source for common starting points.
  • Stars install standalone decorative SVG components.

#Inspect before installing

Use the shadcn CLI to inspect a registry item without writing files.

npx shadcn@latest view @neobrutal-ui/dialog

The output shows the files, npm dependencies, registry dependencies, and configuration that the item declares.

#Install from the namespace

npx shadcn@latest add @neobrutal-ui/dialog

The installed files belong to your project. There is no neobrutal-ui runtime package to keep in sync, so you can modify the source after installation.

#Direct item URLs

Every component page also exposes a direct URL command. This works without a namespace entry.

npx shadcn@latest add https://neobrutal-ui.andongmin.com/r/dialog.json

Continue with Installation for the recommended setup order.