shadcn-impl-framework-integration

What problem does it solve?

Prevents recurring shadcn ui initialization failures where the wrong template flag, mismatched RSC setting, or unsynced alias/theme wiring causes broken runtime behavior or missing client boundaries across frameworks.

Core Features & Use Cases

• Per-framework init correctness: selects the right init template flag (-t next|vite|react-router|astro|start) and ensures components.json defaults match the framework’s actual rendering model.
• RSC vs client boundary safety: diagnoses and fixes issues caused by incorrect components.json.rsc values that lead to missing "use client" directives in Vite or incorrect client bundles in Next.js.
• Alias and theming wiring: ensures @/*/~/* alias resolution works at both TypeScript and bundler/runtime levels, and applies the correct ThemeProvider strategy for Next.js (next-themes), Vite/React Router/TanStack Start (custom React Context), and Astro (inline pre-hydration script).

Quick Start

Tell the AI: "I’m setting up shadcn ui in a Vite/Next.js/Astro/TanStack Start/React Router v7 project and my dark mode or imports don’t work—what exact init flag, components.json.rsc, alias config, and ThemeProvider pattern should I use?"