# Registry

Learn how to use the shadercn registry with the shadcn CLI.

> For the complete documentation index, see [llms.txt](/llms.txt). Markdown variants are available by appending `.md` to any URL or sending an `Accept: text/markdown` header. An agent skill is available at [/.well-known/agent-skills/site-skill.md](/.well-known/agent-skills/site-skill.md).



The **shadercn** registry ships GPU-powered shader components in the [shadcn registry format](https://ui.shadcn.com/docs/registry). Register the namespace once in `components.json`, then pull items by name with the CLI.

## Setup [#setup]

Add a **registries** entry for this site. See the [shadcn registry documentation](https://ui.shadcn.com/docs/registry) for all `components.json` fields and behaviors.

```json
{
  "registries": {
    "@shadercn": "https://shadercn.run/r/{name}.json"
  }
}
```

You can replace `@shadercn` with another namespace; it only needs to match what you pass to `shadcn add`.

## Usage [#usage]

Registry files install shader components into `components/ui/`.

Components declare their dependencies, so installing a component does not require additional setup.

### With namespace [#with-namespace]

Install a component:

```bash
npx shadcn@latest add @shadercn/orb-01
```

### Without namespace [#without-namespace]

Use the full URL (as on each docs page):

```bash
npx shadcn@latest add https://shadercn.run/r/orb-01.json
```