shadcn / RNR Registry

The full AniUI catalog is published as a shadcn-compatible registry at https://aniui.dev/r. Install any component with the shadcn CLI or the React Native Reusables (RNR) CLI — everything stays hosted under AniUI, so you always get the source straight from us.

Already on RNR or a configured NativeWind/Uniwind project? One step. AniUI uses the same theme tokens (background, foreground, primary…) and the same ui/lib aliases you already have — so a component drops in and renders immediately. No extra setup.

Add the @aniui namespace (shadcn CLI)#

components.json

{
  "$schema": "https://ui.shadcn.com/schema.json",
  "registries": {
    "@aniui": "https://aniui.dev/r/{name}.json"
  }
}

Then add components by name. Registry dependencies (like utils and sibling components) resolve automatically:

terminal

# after adding @aniui to components.json
npx shadcn@latest add @aniui/button
npx shadcn@latest add @aniui/card      # auto-pulls @aniui/text + utils
npx shadcn@latest add @aniui/login     # a block — lands in components/blocks/

Install with the RNR CLI#

The React Native Reusables CLI installs any registry item by full URL (it doesn't use namespaces). Point it straight at an AniUI item — transitive dependencies are fetched from their URLs:

terminal

# React Native Reusables CLI — install by full URL
npx @react-native-reusables/cli@latest add https://aniui.dev/r/button.json
npx @react-native-reusables/cli@latest add https://aniui.dev/r/card.json

The raw-URL form also works with the shadcn CLI, no components.json registry entry required:

terminal

# any shadcn-compatible CLI can install by raw URL
npx shadcn@latest add https://aniui.dev/r/button.json

Fresh project#

On a brand-new app that isn't set up for NativeWind/Uniwind yet, the CLIs copy source but can't wire Metro/Babel/Tailwind. Run AniUI's init once to configure everything, then add from the registry:

terminal

# fresh / bare project — set up native config + tokens once
npx @aniui/cli init
# then add from the registry as above (shadcn or RNR CLI)

React Native components.json#

If you set up components.json by hand, this is the React-Native-appropriate shape (rsc: false, RN aliases):

components.json

{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "default",
  "tsx": true,
  "rsc": false,
  "tailwind": {
    "config": "tailwind.config.js",
    "css": "global.css",
    "baseColor": "neutral",
    "cssVariables": true
  },
  "aliases": {
    "components": "components",
    "ui": "components/ui",
    "lib": "lib",
    "utils": "@/lib/utils"
  },
  "registries": {
    "@aniui": "https://aniui.dev/r/{name}.json"
  }
}

Which CLI should I use?#

aniui CLI — full experience: project init, theming, blocks, and the MCP server. Best for AniUI-first projects.
shadcn CLI (@aniui) — drop-in for existing shadcn/RN projects that already use namespaced registries.
RNR CLI (by URL) — already on React Native Reusables? Pull any AniUI component by URL alongside your existing components.

Previous← CLI NextMCP →