Clerk shadcn Registry
shadcn CLI commands that scaffold Clerk auth pages and middleware into a Next.js app
Clerk's docs page for its shadcn-compatible registry, plus the registry itself at clerk.com/r. Twelve items are published: a full quickstart block, a sign-in-or-up variant, sign-in / sign-up / waitlist pages, a ClerkProvider wrapper, a theme provider, a header with auth buttons, a layout-with-header, the Clerk middleware file, and two multistep onboarding flows (AIO and custom-flows). Everything targets the Next.js App Router only — there are no React Router, Vue or Remix items.
npx shadcn@latest add https://clerk.com/r/nextjs-quickstart.jsonThis is the fastest correct path from an empty Next.js app to working auth: run the nextjs-quickstart item and it drops ClerkProvider, middleware, a header and the sign-in/sign-up routes in one shot, instead of you hand-writing matchers in middleware.ts and getting the public-route regex wrong. Pair it with the Supabase UI blocks only if Supabase is the database and Clerk is the identity provider — do not install both auth blocks or you get two competing session layers. The registry stops at Next.js App Router, so for Vite, React Router or Remix fall back to Clerk's normal SDK docs.
Why it is here. A vendor proving that auth setup — the most error-prone part of a scaffold — can be one shadcn command, which is exactly the shape an agent can execute reliably.
- one-command Next.js auth scaffold
- 12 registry items including waitlist and onboarding
- writes middleware.ts for you
- App Router only
- official Clerk-maintained
Verified 2026-08-15. HTTP 200. https://clerk.com/docs/guides/development/shadcn-cli, https://clerk.com/r/registry.json (full 12-item manifest), https://clerk.com/r/nextjs-quickstart.json (200), https://clerk.com/llms.txt
