nextjs-reviewer

Analyzes Next.js 16+ App Router projects for PPR, caching, and Suspense issues.

6|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/jaredpalmer/claude-plugins --skill nextjs-reviewer-jaredpalmer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-reviewer
Source: https://github.com/jaredpalmer/claude-plugins/tree/main/skills/nextjs-reviewer
Command: npx skills add https://github.com/jaredpalmer/claude-plugins --skill nextjs-reviewer-jaredpalmer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Next.js Reviewer helps teams quickly assess App Router implementations for Partial Prerendering (PPR), caching strategies, Suspense boundaries, and React Query integration to ensure Next.js 16+ best practices.

Core Features & Use Cases

  • Identify misconfigurations in cache components, Suspense boundaries, and data fetching patterns.
  • Provide actionable recommendations to optimize static shell, per-user caching, and hydration.
  • Generate a structured review report suitable for PRs and architecture discussions.

Quick Start

Run the reviewer on your Next.js project to generate a comprehensive PPR and caching report.

Frequently Asked Questions about nextjs-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Next.js App Router Partial Prerendering and caching strategies?

To review Next.js App Router PPR and caching strategies, analyze project layouts, pages, and server/client boundaries to identify misconfigurations in cache components, Suspense boundaries, and data fetching patterns.

Does Next.js PPR review require cacheComponents enabled?

Next.js PPR review requires Next.js 16+ with cacheComponents enabled and a typical App Router project structure to properly analyze static shell, per-user caching, and hydration.

What is the best way to optimize Suspense boundaries and React Query integration in Next.js?

Optimizing Suspense boundaries and React Query integration in Next.js requires assessing data fetching patterns to provide actionable recommendations for static shell generation, per-user caching, and hydration.

How do I generate a structured report for Next.js App Router architecture critiques?

Generating a structured report for Next.js App Router architecture critiques requires running an automated review on layouts and pages to output actionable PPR and caching optimization recommendations suitable for PRs.

What are common misconfigurations in Next.js App Router caching and data fetching?

Common Next.js App Router caching and data fetching misconfigurations include improper Suspense boundaries, suboptimal static shell generation, and incorrect React Query integration affecting hydration and per-user caching.