Multi-stack shadcn registry
Shadcn Components for Tailwind v3
240+ React sections and components for shadcn projects, built to work seamlessly with Tailwind v3. One CLI command. No upgrade required.
pnpm dlx shadcn@latest add https://ruixen.com/r/tw3/gradient-hero-showcase.jsonExample installs the Gradient Hero Showcase. Same /r/tw3/ prefix works for every component.
Why a Tailwind v3 build still matters
v3 is still production
Tailwind v4 rewrote the CSS engine in December 2024. Most large codebases stay on v3 for pinned dependencies, design-system stability, and managed migration risk.
Identical components
One source codebase. A build-time transform produces v3 and v4 variants automatically — v4-only patterns are rewritten to v3 equivalents. The JSX and behavior are the same.
Drop-in via shadcn CLI
Use the same shadcn CLI you already use. Point it at the /r/tw3/ registry endpoint and the v3 variant lands in your project.
A sample of what ships in Tailwind v3
Every component in the catalog is available in v3. Browse the full docs for the rest of the 240+ sections and primitives.
Frequently asked questions
Does Ruixen UI really work with Tailwind CSS v3?+
Yes. Every component in the catalog is generated into both a Tailwind v3 and a Tailwind v4 variant at build time. The v3 variant is published at /r/tw3/<component>.json and uses HSL-based shadcn theme tokens, which v3 understands natively. No manual porting required.
Why ship a Tailwind v3 build at all in 2026?+
Tailwind v4 rewrote the CSS engine and shipped December 2024. Many production codebases stay on v3 because they have pinned dependencies, paid migration risk, or design systems already tuned to v3's behavior. Most shadcn-style libraries now assume v4. Ruixen is the registry that meets v3 users where they are.
Are v3 users getting the same components as v4 users?+
Yes — identical components. The source code lives once in /registry. A build-time transform produces the v3 variant by rewriting v4-only patterns (var(--color-TOKEN) becomes hsl(var(--TOKEN)), inset-shadow utilities are dropped). The visual output is the same.
What's the migration path when I eventually move to v4?+
Swap your install URL from https://ruixen.com/r/tw3/<name>.json to https://ruixen.com/r/<name>.json and re-run the shadcn CLI. The component source you already have can stay — v3 and v4 share the same JSX. The transform only rewrites Tailwind class strings.
Do I need extra config beyond shadcn's standard Tailwind v3 setup?+
No. If your project already builds with Tailwind v3 and has the standard shadcn theme variables in globals.css, the v3 components drop in unchanged. The shadcn CLI handles dependencies, file placement, and registry resolution.
Is Tailwind v3 support free?+
Yes. The full 240+ component catalog is MIT-licensed and free across all four stack variants (Tailwind v3 or v4, Radix or Base UI). Ruixen Pro is a separate one-time $59 purchase for premium components and landing-page templates.
Need polished landing-page templates?
Ruixen Pro ships 50+ premium components and full landing-page templates that work in Tailwind v3 and v4. One payment, lifetime updates.