Native components you copy into your app
Styled UI for NSH, built on nsh/base and handed to you as files you own — what shadcn/ui gives React.
npx shadcn-nsh@latest init- components
- 79 components
- themes
- 3 themes
See it running
The theme showcase, live. Switch the theme, or the phone and desktop layouts.
Why shadcn-nsh
Copy into your app
add writes the component, its theme and the looks it imports into your app, then forgets them. No runtime package to keep in sync: the files are yours to change.
Native behavior
Keyboard, focus, accessibility and platform idioms come from nsh/base. The components only decide how things look.
The look is data
Colors and surfaces are read from theme.json and finishes.json, never written in a component, so one theme swaps the whole look — even while the app runs.
Phone, desktop, terminal
Each component adapts its density and controls to a touch screen, a pointer and a keyboard, and draws in the terminal too.
The shadcn/ui shape
A registry, a CLI and one file per component, with the composition and names you know from shadcn/ui: Trigger, Content, Item.
Every page is live
Each component page runs its demo in the browser through NSH's web target, in the phone or the desktop layout and in any of the themes.
Start with one component
init sets up the theme and the @/ alias; add copies a component and what it needs.
npx shadcn-nsh@latest initnpx shadcn-nsh@latest add button