nextjs

Migrate Next.js 16 app router patterns with async route parameters and codemod assistance.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/eKoh951/hytale-gg --skill nextjs-ekoh951
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs
Source: https://github.com/eKoh951/hytale-gg/tree/main/.windsurf/skills/nextjs
Command: npx skills add https://github.com/eKoh951/hytale-gg --skill nextjs-ekoh951

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Next.js 16 migrations for App Router patterns require updating async route parameters, cookies, headers, and proxy usage; developers often struggle with parallel routes and cache APIs. This Skill consolidates guidance for upgrading and ensures compatibility across projects.

Core Features & Use Cases

  • Guidance on async parameters, proxy migration, parallel routes with default files, and cache components.
  • Codemod-assisted migration and manual-step checklist for Next.js 16 upgrades.
  • Practical templates and references to ensure compatibility across projects.

Quick Start

Run the automated codemod to migrate async params and update APIs, then apply parallel route defaults and proxy migrations.

Frequently Asked Questions about nextjs

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

FAQPage Schema
How do I migrate async route parameters in Next.js 16?

Next.js 16 requires making async route parameters explicit by awaiting them before use. This process involves running a codemod to automatically update params, cookies, and headers to the new async API format.

What is the best way to handle proxy.ts migration in Next.js 16?

Handling proxy.ts migration in Next.js 16 involves applying updated APIs and following specific proxy migration guidance. This Skill provides practical templates and references to ensure project compatibility during the upgrade.

How do parallel routes work with default.tsx in Next.js 16?

Parallel routes in Next.js 16 use default.tsx files to render fallback content when a slot cannot be matched. This Skill enforces best practices for configuring parallel routes and cache components to maintain compatibility.

Do I need to manually update cookies and headers for Next.js 16 migrations?

You do not need to manually update all cookies and headers because this Skill provides a codemod-assisted migration. However, a manual-step checklist is also included to verify best practices and ensure all async patterns are correctly migrated.

Why are my Next.js 16 async params not working after the upgrade?

Next.js 16 async params fail when they are not made explicit by awaiting the returned promise. You must update your code to await async params, cookies, and headers before accessing their values to resolve the migration issues.