nextjs-16

Implement Next.js 16 App Router patterns with typed params and server actions.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/JeffKM/pitch-ac --skill nextjs-16-jeffkm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-16
Source: https://github.com/JeffKM/pitch-ac/tree/main/.claude/skills/nextjs-16
Command: npx skills add https://github.com/JeffKM/pitch-ac --skill nextjs-16-jeffkm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers adopt Next.js 16 App Router patterns and best practices, enabling faster, safer implementation of pages, layouts, routes, and server actions.

Core Features & Use Cases

  • Param resolution with Promise-based params support for dynamic routing and safe data access.
  • PageProps/LayoutProps helpers for type-safe route components.
  • Server Actions and useActionState for form mutations with progressive enhancement.
  • Cache Components (PPR) patterns to mix static, cached, and runtime content.
  • Proxy / Middleware patterns for routing, security, and localization.
  • Real-world examples covering static/dynamic routes, layouts, and error handling.

Quick Start

Start by scaffolding a Next.js 16 App Router project and implement a sample page with params, PageProps, and a server action to demonstrate routing, data fetching, and server/client boundaries.

Frequently Asked Questions about nextjs-16

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

FAQPage Schema
How do I handle dynamic route params with Promise-based params in Next.js 16 App Router?

You can implement Next.js 16 Server Actions using the useActionState hook to manage form mutations. This pattern enables progressive enhancement, allowing forms to function without JavaScript while providing type-safe server-side data processing and client-side state updates.

What are Cache Components in Next.js 16 and how do they mix static and dynamic content?

Next.js 16 provides PageProps and LayoutProps helpers to enforce strict typing for route components. By combining these helpers with TypeScript and Promise-based params, you achieve end-to-end type safety across your server and client boundaries.

How do I structure server and client boundaries when using Server Actions in Next.js 16?

Structuring server and client boundaries in Next.js 16 involves defining Server Actions at the server boundary and invoking them via useActionState on the client. This maintains robust typing and progressive enhancement while keeping sensitive logic server-side.

Can I use middleware and proxy patterns for localization and security in Next.js 16?

Next.js 16 supports proxy and middleware patterns for routing, security, and localization. You can intercept requests at the edge to enforce access controls, rewrite paths based on locale, and apply consistent routing rules before reaching the App Router.