skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
fusengine/claude-plugins75 installs

nextjs-16

Use when building Next.js 16 apps — Turbopack, App Router, Cache Components, proxy.ts, v15 migration. Not for stack scaffolding (nextjs-stack) or React SPA (react-expert).

How do I install this agent skill?

npx skills add https://github.com/fusengine/claude-plugins --skill nextjs-16
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides documentation for a fictional version of Next.js (version 16) and enforces a specific, non-standard workflow for the AI agent. It also encourages the use of an unverified third-party tool (next-devtools-mcp). While not explicitly malicious, the deceptive versioning and meta-instructions could lead the agent to generate incorrect code or install unnecessary software.

  • Socketpass

    No alerts

  • Snykfail

    Risk: CRITICAL · 2 issues

What does this agent skill do?

<objective> Covers Next.js 16 core framework mechanics (current stable: 16.4): Turbopack (default bundler; Webpack remains available via the `--webpack` opt-out flag), the App Router (nested layouts, parallel/intercepting routes, file conventions like page.tsx/layout.tsx/loading.tsx/error.tsx/not-found.tsx), Cache Components (`use cache`, `cacheTag()`, `cacheLife()`, `revalidateTag()`), `proxy.ts` (full Node.js runtime, replaces Edge middleware), and React 19 integration (View Transitions, new hooks).

Documents the critical v15→v16 breaking changes: proxy.ts replacing middleware.ts, Turbopack as the default for next dev/next build, cacheComponents replacing the removed experimental.ppr flag, required React 19, and async params/searchParams. This skill covers core framework APIs only — for assembling a full production stack (Prisma, Better Auth, shadcn/ui, Zustand together) use nextjs-stack instead; for a pure React SPA without next.config.* use the react-expert skills instead. </objective>

Next.js 16 Expert

Production-ready React framework with Server Components, streaming, and Turbopack.

Agent Workflow (MANDATORY)

Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:

  1. fuse-ai-pilot:explore-codebase - Analyze existing routes, components, and patterns
  2. fuse-ai-pilot:research-expert - Verify latest Next.js 16 docs via Context7/Exa
  3. mcp__context7__query-docs - Check breaking changes v15→v16

After implementation, run fuse-ai-pilot:sniper for validation.


Overview

When to Use

  • Building new React applications with server-first architecture
  • Need Server Components for optimal performance and SEO
  • Implementing streaming and progressive rendering
  • Migrating from Next.js 14/15 to version 16
  • Using proxy.ts for route protection (replaces middleware)
  • Leveraging Turbopack for faster development builds

Why Next.js 16

FeatureBenefit
Turbopack default2-5x faster builds, 10x faster HMR; Webpack only via --webpack opt-out
Cache ComponentsExplicit caching with use cache directive
proxy.tsFull Node.js runtime, replaces Edge middleware
React CompilerAutomatic memoization, no manual useMemo/useCallback
React 19View Transitions, useEffectEvent, Activity component
App RouterNested layouts, parallel routes, intercepting routes

Breaking Changes from v15

Critical Migration Points

  1. proxy.ts replaces middleware.ts - Full Node.js runtime, not Edge
  2. Turbopack by default - next dev/next build use Turbopack; a custom webpack config fails the build unless you migrate it or opt out with --webpack
  3. cacheComponents + use cache - Replaces experimental.ppr / experimental_ppr (removed); PPR is the default behavior under cacheComponents
  4. React 19 required - New hooks and View Transitions API
  5. Async params/searchParams - Must await dynamic route params

Cache Components: the recommended model (16.4+)

Since 16.4 Cache Components is recommended for every Next.js app, create-next-app enables it by default, and it becomes the default in Next.js 17. Data fetching is dynamic by default; opt in to caching per component/function with 'use cache'. Use the two-flag setup (cacheComponents: true + partialPrefetching: true, set partialPrefetching explicitly) for new code and when touching caching/data fetching; see cache-components.md. Existing apps: npx next@canary upgrade --agent=latest (see upgrade.md).

New in 16.1 – 16.4 (see upgrade.md)

  • 16.1 - Turbopack filesystem cache on by default for next dev; next dev --inspect
  • 16.2 - transitionTypes prop on <Link>, next start --inspect, Adapters API stable
  • 16.3 - catchError + retry() error recovery (stable), next/root-params, import.meta.glob, Turbopack build cache on by default, opt-in Instant Navigations (partialPrefetching with cacheComponents)
  • 16.4 - Cache Components recommended for all apps (on by default in create-next-app, default in Next.js 17); ensureStatic route segment config; navigation() / prefetch() from next/cache; next upgrade --agent + experimental.agentUpgrade; React 19.3 (stable View Transitions, Fragment Refs, browser()); lazy server HMR, smaller Turbopack disk cache and production bundles

SOLID Architecture

Module-Based Structure

Pages are thin entry points importing from feature modules:

  • app/page.tsx → imports from modules/public/home/
  • app/dashboard/page.tsx → imports from modules/auth/dashboard/
  • modules/cores/ → Shared services, utilities, configurations

File Conventions

  • page.tsx - Route UI component
  • layout.tsx - Shared UI wrapper
  • loading.tsx - Suspense loading state
  • error.tsx - Error boundary
  • not-found.tsx - 404 handling

Core Concepts

Server Components (Default)

All components are Server Components by default. Use 'use client' directive only when needed for interactivity, hooks, or browser APIs.

Caching Strategy

  • Default - With cacheComponents on (recommended, 16.4+) data fetching is dynamic; wrap uncached runtime access in <Suspense> and cache explicitly
  • use cache - Mark async functions for caching
  • cacheTag() - Tag cached data for targeted revalidation
  • cacheLife() - Control cache duration (stale, revalidate, expire)
  • revalidateTag() - Invalidate cached data on-demand

Data Fetching

Server Components fetch data directly. Use fetch() with native caching or database queries. No need for getServerSideProps or getStaticProps.


Reference Guide

NeedReference
Initial setupinstallation.md, project-structure.md
Migration v15→v16upgrade.md, middleware-migration.md
Routingapp-router.md, routing-advanced.md
Cachingcaching.md, cache-components.md
Server Componentsserver-components.md, directives.md
React 19 featuresreact-19.md, react-compiler.md
Route protectionproxy.md, security.md
SEO/Metadatametadata.md, metadata-files.md
Forms/Actionsforms.md, data-fetching.md
Deploymentdeployment.md, environment.md

Best Practices

  1. Server Components first - Only add 'use client' when necessary
  2. Colocate data fetching - Fetch data where it's used
  3. Streaming with Suspense - Wrap slow components in Suspense
  4. proxy.ts over middleware - Full Node.js runtime for auth
  5. Cache explicitly - Use use cache for expensive operations
  6. Parallel routes - Load independent UI sections simultaneously

Performance

Build Optimization

  • Turbopack - Incremental compilation, instant HMR
  • React Compiler - Automatic memoization
  • Tree shaking - Unused code elimination
  • Code splitting - Automatic route-based splitting

Runtime Optimization

  • Streaming - Progressive HTML rendering
  • Partial hydration - Only hydrate interactive components
  • Image optimization - Automatic WebP/AVIF conversion
  • Font optimization - Zero layout shift with next/font

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/fusengine/claude-plugins/nextjs-16">View nextjs-16 on skillZs</a>