nextjs-framework

What problem does it solve?

Many teams struggle with correct App Router structure, rendering choices, server/client component boundaries, caching and revalidation, middleware, and deployment configuration in Next.js which leads to bugs, poor performance, and fragile builds. This Skill consolidates best practices to reduce architectural mistakes, speed development, and improve runtime behavior across routes and API handlers.

Core Features & Use Cases

• Project Structure & Routing: Guidance on App Router conventions, route groups, dynamic/parallel routes, and where to place shared components and utilities.
• Rendering & Data Fetching: Advice on choosing between static, ISR, SSR, CSR, and streaming; parallel fetch patterns; Server Actions; and revalidation/tagging strategies.
• Platform & Deployment: Recommendations for middleware, next.config tuning, image/font optimization, runtime selection (nodejs vs edge), and deployment outputs (Vercel, standalone, Docker).
• Use Case: Migrate a Pages Router app to the App Router, convert heavy client code to server components, and set per-route caching and revalidation to reduce TTFB and bundle size.

Quick Start

Ask the nextjs-framework skill to review the app directory and recommend per-route rendering, caching, and component boundaries to improve performance and correctness.