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/dialogWith the registry named once in your project. How to set it up
3D, in the highlight colour
Buttons
A one-time code
A toolbar and tabs
Theme
Change the look of this page.
These switches set three attributes. Everything on the site follows, and your product does the same.
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.
- Controls and surfaces94Buttons, fields, menus, dialogs, dates, lists, conversation parts, players and records.
- Layout9Containers, sections, a bento grid, a marquee and frames.
- Motion15Reveals, scroll scenes, pointer effects and page transitions, from the theme's durations.
- 3D7Scenes that take their colours from the theme and fall back to a still.
- Charts8SVG charts and sparklines in the theme's series colours, each with a text alternative.
- Helpers8Class names, motion tokens, reading direction, announcements and controllable state.
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.
/**
* @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.
- Everything on one pageControls, overlays, display, layout, motion, 3D and charts, with the theme switches.
- FoundationsReading direction, announcements for screen readers, type that follows the script.
- ChoicesChips, tiles, a segmented control, a number stepper.
- Dates and timesA calendar, date and date-range pickers, offered time slots, a time field.
- Flows and listsSteps, a wizard, a sortable list, a combobox, skeletons that hold their size.
- PanelsA bottom sheet with snap points, a dock beside the page, a frame for a map.
- ConversationA thread, messages, streaming text, a status line, a composer.
- Pictures and uploadsA gallery, a lightbox with zoom, shared-element transitions, a dropzone with progress.
- Video and soundA video player, an audio player with a waveform, a scrubber, captions.
- Records and decisionsA compare table, fact rows with their source, consent, a language switcher, prices, a countdown.
- Models in 3DA viewer for one model, glTF or Gaussian splats, with a poster, progress, keys and a still fallback.
- Comparison and provenanceA then-and-now slider, a legend of certainty classes, a label that says what a picture is.
- Carousels and media rowsA scroll-snap carousel with autoplay that can be paused, and reorderable rows of uploads.
- PrimitivesAn alert dialog, a collapsible, a hover card, a menubar, a navigation menu, a toolbar, a one-time code, a password field, and words for screen readers.
- Lists of any lengthA windowed list and grid for thousands of rows of any height, with their place remembered.
- Stage for timed scenesA sequence of timed scenes with a transport and a clock, and frames drawn on request for export.
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.