Installed from ui.kaotypr.com
Raihin doesn't ship its own component library. Every component is installed from the ui.kaotypr.com registry — the same shadcn-compatible primitives used across products that share the design system core. Token names and component APIs are identical; what changes is the values Raihin binds to those tokens.
How it works
The kaotypr UI registry is a shadcn-compatible source of refined primitives, custom components, and blocks. Each component reads tokens by name (bg-card, text-primary-foreground, rounded-button, --density-control-h), never hardcoded values.
Raihin imports the same component source but binds the tokens to its own values in app/globals.css. The result: same API, same variants, same accessibility — different visual character. Every example below is a live render of a component installed from ui.kaotypr.com, styled by Raihin's tokens.
Install
Use the standard shadcn CLI pointed at the kaotypr registry. Each component is a JSON endpoint at https://ui.kaotypr.com/r/{name}.json.
pnpm dlx shadcn@latest add https://ui.kaotypr.com/r/button.json
pnpm dlx shadcn@latest add https://ui.kaotypr.com/r/card.json
# …or any other component / blockLive preview
Every component below is the kaotypr registry source running on Raihin's tokens. Resize, toggle dark mode, or switch density mode — the components respond because their tokens do.
default · secondary · outline · ghost · destructive · link
default · secondary · outline · destructive · success · warning · info · ghost
destructive · success · warning · info — the four locked status hues
input · label · checkbox · switch
surface · header · content · footer
image · fallback initials
trigger · content
keyboard shortcut display
Where to look next
- ui.kaotypr.com — the full registry with documentation for every variant, prop, and example.
- Patterns— common compositions of these primitives (form fields with errors, status alerts, multi-field layouts).
- Tokens— the values these components consume. Edit a token in
app/globals.cssand every install of the matching component reskins automatically. - Foundations— the rules every component on this page already follows (semantic pairs, the solid status pattern, the focus-ring convention).