shadcn/ui

What is it?

shadcn/ui is a CLI-delivered set of React + TypeScript component recipes built on Radix UI primitives and styled with Tailwind CSS. You add components via `npx shadcn add <component>` and the source lands in your repo — fully editable, no runtime dependency, no vendor lock-in.

What does it do?

shadcn/ui covers the full component surface of a modern web app: dialogs, dropdowns, forms, tables, tabs, tooltips, toasts, date pickers, combos, command palettes, and dozens more. Every piece is accessible by default (ARIA, keyboard nav, focus management), themeable via CSS variables, and compatible with Next.js App Router and React Server Components.

Where is it used?

shadcn/ui is the default component starter for thousands of Next.js and Remix apps shipped in 2025–2026, from indie SaaS to enterprise dashboards at Vercel, Linear, and Cal.com. Its 'copy source into your repo' model made it the preferred approach for teams who rejected the npm-install component-library trap.

When & why it emerged

shadcn/ui was released by @shadcn in 2023 to solve the component-library fatigue cycle — MUI, Chakra, Mantine all force black-box opinions and bloated bundles for features you never use. Copying source into your repo meant teams could ship production UI in a weekend while retaining full control when the design evolves.

Why we use it at Internative

shadcn/ui is the foundation of every UI we ship in 2026, including the site you're on. Components live in `src/components/ui/` where we tune them to our design tokens. When a client wants a 'completely custom design system', we start from shadcn primitives and evolve outward — saving weeks of foundational work while guaranteeing accessibility from day one.