What problem does it solve? Production bugs in Next.js App Router apps are hard to isolate because failures can originate in server rendering, client hydration, runtime environments, or one of four caching layers. This Skill provides structured diagnostic tables and fixes to pinpoint and resolve these issues quickly. ## Core Features & Use Cases - SSR vs CSR Isolation: Decision tables and techniques (disabling JavaScript, hard refresh) to determine whether a bug lives on the server or the client. - Hydration Error Debugging: Identifies common causes like Date.now() in render bodies, invalid HTML nesting, and window checks, with fixes such as useEffect and suppressHydrationWarning. - Runtime and Cache Troubleshooting: Covers Edge vs Node runtime mismatches (e.g., 'fs' module errors in Middleware) and the four Next.js cache layers (Request Memoization, Data Cache, Full Route Cache, Router Cache) with revalidation fixes. - Use Case: Your page shows stale data after a database update. Follow the cache debug flow to determine whether the culprit is the client Router Cache, Data Cache, or Full Route Cache, then apply revalidatePath or force-dynamic accordingly. ## Quick Start Ask the assistant to diagnose why your Next.js page shows a hydration error or stale data in production using the nextjs-production-debugger guidelines.