What problem does it solve? Writing and reviewing Next.js code often leads to subtle bugs: invalid async client components, non-serializable props crossing server/client boundaries, hydration mismatches, missing Suspense boundaries, and misconfigured images or fonts. This Skill provides structured guidance to detect and fix these issues while enforcing project-specific rules like multi-tenant auth boundaries. ## Core Features & Use Cases - RSC Boundary Validation: Detects invalid patterns such as async client components, non-serializable props (Date, Map, class instances), and incorrect Server Action usage. - Data Fetching Patterns: Guides selection between Server Components, Server Actions, and Route Handlers, and prevents data waterfalls with Promise.all, Suspense, and preload patterns. - Optimization & Debugging: Covers image/font optimization, metadata and OG image generation, hydration error fixes, bundling issues, self-hosting with Docker, and MCP-based dev server debugging. - Use Case: When building a Next.js 15+ dashboard page, use this Skill to correctly await async params, wrap useSearchParams in Suspense, configure remote image patterns, and avoid try-catch around redirect() in Server Actions. ## Quick Start Review my Next.js page component for RSC boundary violations, async API usage, and data fetching best practices.