Apply Next.js 16 App Router caching, streaming, and routing patterns.
npx skills add https://github.com/moughamir/justwaitit-review --skill nextjs-moughamir
Please help me install this Agent Skill. Skill: nextjs Source: https://github.com/moughamir/justwaitit-review/tree/main/.agents/skills/nextjs Command: npx skills add https://github.com/moughamir/justwaitit-review --skill nextjs-moughamir
It solves performance regressions and inconsistent best practices in Next.js 16 App Router apps by providing a prioritized, rule-based checklist that helps you avoid common mistakes in caching, data fetching, routing, and client/server boundaries.
fetch cache options, use cache, revalidatePath, and revalidateTag (with cacheLife profiles) to control freshness and prevent stale UIs after mutations.notFound() handling, and the Next.js 16 proxy.ts network boundary model.Ask the AI to review your Next.js 16 App Router change by checking caching strategy, server-component data fetching, and route-level loading/streaming against the nextjs skill rules.
High-intent search queries and answers about installing and using this skill.
Fix stale UI after mutations in Next.js App Router by applying cache invalidation patterns using revalidatePath and revalidateTag with cacheLife profiles to control data freshness and ensure UI consistency post-mutation.
The best way to configure caching and streaming in Next.js 16 is using explicit fetch cache options, use cache directives, and segment config exports to optimize route-level loading and error boundaries for faster perceived performance.
Structure server components and parallel routes in Next.js by preferring server-side data fetching, implementing parallel and intercepting routes, and handling notFound states to maintain proper client and server composition boundaries.
Yes, this Next.js performance guidance fully supports the proxy.ts network boundary model in Next.js 16, ensuring correct server and client composition while optimizing routing and data fetching patterns across the application.
Slow cold starts and large bundles in Next.js App Router routes often stem from improper server and client composition boundaries, which you can resolve by applying rule-based performance checklists for data fetching and caching directives.
thongdn-itApply Next.js 16 App Router optimization guidelines for caching, server components, and routing.
CutTheChexxOptimize web performance by reducing bundles and enabling code-splitting.
frankxaiImplement React 19 and Next.js 15 patterns for Server Components, Client Components, and Server Actions.
rnavarychProvide React 19 expertise for Next.js 15 and Remix applications.