Skip to the content
Prelaunch

Components you own, themed from one place.

Rivier UI is a component library for AI-native development. Copy the source into your project, restyle all of it with three attributes, and give your assistant a library it can read.

npx shadcn@latest add @rivier-ui/button @rivier-ui/dialog

With the registry named once in your project. How to set it up

3D, in the highlight colour

Buttons

NewBetaLive

A one-time code

A toolbar and tabs

Billed every month.

Theme

Change the look of this page.

These switches set three attributes. Everything on the site follows, and your product does the same.

Mode
Roundness
Highlight

How theming works

Why

Built for products that an assistant helps write.

  • Copied in, not installed.

    A command puts the source in your project. You can read it and change it, and nothing breaks on an upgrade you did not ask for.

  • One theme, three switches.

    Light or dark, square to round, any highlight colour. Three attributes reach every component, charts and 3D included.

  • Written to be read by an assistant.

    Every file says what it is, when to use it and when not to, with an example that works. llms.txt and the registry are generated from that.

  • Past the flat page.

    Bento layouts, motion and page transitions, 3D scenes and charts are in the same library, on the same theme.

  • Checked in a real browser.

    Each keyboard pattern is pressed key by key at desktop and phone widths, left-to-right and right-to-left, with an accessibility scan.

  • In any language.

    No words are fixed in a component, layout follows the reading direction, and type follows the script.

What is in it

141 items, one look.

Controls and surfaces, layout, motion, 3D and charts. Each one with its example, its source and a demonstration you can try.

For assistants

A library an assistant can read.

Every file opens with what the component is, when to reach for it, what to use instead, and an example that works. One file, llms.txt, holds all of them.

registry/ui/dialog.tsx
/**
 * @name dialog
 * @category ui
 * @description A modal window over a dimmed page, with parts for a header, title, description and footer.
 * @when A short task or a decision that must be finished or dismissed before going on. For a panel from an edge (menus, filters, details) use sheet; for something small attached to a control use popover. Always give it a DialogTitle (add className="sr-only" to hide it). Opened by a DialogTrigger, focus returns to that trigger on close. Opened by state with no trigger (a shortcut, a menu item), Radix has nothing to return to: remember the opener (`opener.current = document.activeElement` before opening) and refocus it in `onCloseAutoFocus={(event) => { event.preventDefault(); opener.current?.focus(); }}` on DialogContent.
 * @example
 * <Dialog>
 *   <DialogTrigger asChild><Button variant="outline">Rename</Button></DialogTrigger>
 *   <DialogContent>
 *     <DialogHeader>
 *       <DialogTitle>Rename project</DialogTitle>
 *       <DialogDescription>The address of the project does not change.</DialogDescription>
 *     </DialogHeader>
 *     <input aria-label="Name" defaultValue="Atlas" className="h-control rounded-control border border-input px-3 text-base" />
 *     <DialogFooter>
 *       <DialogClose asChild><Button variant="outline">Cancel</Button></DialogClose>
 *       <Button>Save</Button>
 *     </DialogFooter>
 *   </DialogContent>
 * </Dialog>
 */

Showcase

See every component working.

These pages are the ones the browser checks drive. Add ?dir=rtl to any of them to read it right-to-left.

Start with one component.

Name the registry at ui.rivier.ai once, add a button, and change it as you like. It is your code from then on.