nextjs

Migrate Next.js projects to App Router with structured guidance and templates.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/GofiveCorp/pegasussio --skill nextjs-gofivecorp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs
Source: https://github.com/GofiveCorp/pegasussio/tree/main/.agent/skills/nextjs
Command: npx skills add https://github.com/GofiveCorp/pegasussio --skill nextjs-gofivecorp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps developers migrate to Next.js 16 App Router by providing structured guidance, templates, and best practices.

Core Features & Use Cases

  • Async route params handling, Server Components/Actions, and Cache Components ("use cache") fundamentals.
  • Proxy.ts migration, Route Handlers, and Parallel Routes with default.tsx for reliable soft navigation.
  • Real-world upgrade scenarios: Turbopack adjustments, i18n caching, and metadata optimization.

Quick Start

Quick start: Use the codemod to migrate code to Next.js 16, then apply the provided templates and references to implement App Router patterns, Server Components, and caching strategies across your project.

Frequently Asked Questions about nextjs

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

FAQPage Schema
How do I migrate to Next.js 16 App Router with async params and cache components?

Use the provided codemod to automatically migrate code to Next.js 16, then apply structured templates and references to implement App Router patterns, async route params, and cache components across your project.

What is the best way to handle parallel routes and default.tsx for soft navigation in Next.js?

The best way to handle parallel routes is by using default.tsx files alongside structured guidance to ensure reliable soft navigation, preventing layout shift and routing errors during App Router transitions.

How does proxy.ts migration work when upgrading to the Next.js App Router?

Proxy.ts migration involves restructuring your middleware logic into the App Router architecture using provided templates and best practices to maintain reliable request handling and routing behavior.

Can I use Turbopack adjustments and i18n caching with Next.js Server Components?

Yes, this skill provides specific guidance for real-world upgrade scenarios including Turbopack adjustments, i18n caching, and metadata optimization within Server Components and Actions.

What are the limitations of migrating to Next.js App Router with Server Actions?

Migrating to App Router with Server Actions requires careful handling of async params and cache components; incorrect implementation can break soft navigation, so following best practices and templates is essential.