shadcn-agents-rsc-boundary-validator

Hydration crashes like 'useState is not a function' occur when shadcn ui components violate React Server Components boundaries by missing or misplacing 'use client' directives. Auditing your codebase validates directive placement and verifies provider wrapper boundaries to resolve these runtime errors.

Auditing a Next.js codebase for 'use client' directives requires scanning components.json, classifying shadcn imports per a client/RSC-safe matrix, and verifying directive formatting. This process identifies over-clientification and ensures correct server-to-client boundary separation before merging.

A React Server Components boundary violation happens when server-to-client prop crossing introduces non-serialisable instances or inline functions. It also occurs when 'use client' is absent where required or placed incorrectly, causing runtime failures during App Router hydration.

Passing non-serialisable props or inline functions across the server-to-client boundary violates RSC rules and causes runtime crashes. Boundary validation flags these server-to-client prop crossings to ensure only serialisable data passes into shadcn ui client components.

The components.json rsc flag must match your Next.js project framework configuration to maintain correct RSC boundaries. Boundary validation checks this alignment and verifies each shadcn primitive is in the correct server/client module shape to prevent build failures.

Fixing direct ThemeProvider imports into app/layout.tsx requires checking provider wrapper boundaries to ensure proper 'use client' isolation. RSC boundary validation identifies these Provider-import mistakes and generates a PASS/WARN/FAIL checklist to guide corrections before merging.