nextjs-app-router-patterns

Implement Next.js 14+ App Router patterns with server components and streaming.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/brunodavid1308/match-node --skill nextjs-app-router-patterns-brunodavid1308
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-app-router-patterns
Source: https://github.com/brunodavid1308/match-node/tree/main/.agents/skills/nextjs-app-router-patterns
Command: npx skills add https://github.com/brunodavid1308/match-node --skill nextjs-app-router-patterns-brunodavid1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Next.js 14+ App Router patterns solve the complexity of building scalable, fast, and maintainable React applications by leveraging server components, streaming, and parallel routes.

Core Features & Use Cases

  • Rendering Modes: Server Components, Client Components, Static, Dynamic, Streaming.
  • Patterns: Server Components with data fetching, Client Components with use client, Server Actions, Parallel Routes, Intercepting Routes, Streaming with Suspense, Route Handlers, Metadata/SEO.
  • Use Cases: Build new apps with App Router, migrate from Pages Router, optimize data fetching, implement SSR/SSG, and add progressive enhancements across routes.

Quick Start

Create a new Next.js 14+ App Router project and implement Server Components, streaming, and parallel routes as described.

Frequently Asked Questions about nextjs-app-router-patterns

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

FAQPage Schema
How do I migrate a Next.js application from the Pages Router to the App Router?

Next.js App Router migration involves adopting new file conventions, moving data fetching to Server Components, and updating routing trees to leverage streaming and Server Actions for scalable apps.

What is the best way to implement streaming and Suspense in Next.js Server Components?

Implementing streaming in Next.js Server Components requires wrapping asynchronous UI segments in Suspense boundaries. This progressively streams HTML to the client, rendering fallbacks while data fetching completes across complex route trees.

How do Next.js parallel routes and intercepting routes work for complex layouts?

Next.js parallel routes render multiple pages simultaneously within a single layout using named slots, while intercepting routes load routes within the current context to enable advanced routing patterns like modals without full page transitions.

When should I use Server Actions instead of API Route Handlers in Next.js 14+?

Use Server Actions for progressive enhancement and mutations within Server Components, while Route Handlers are better for explicit HTTP endpoints. Both handle data fetching and updates within the App Router.

Does Next.js App Router support static and dynamic rendering modes simultaneously?

Next.js App Router supports simultaneous static and dynamic rendering. You can statically generate pages at build time while dynamically fetching data on demand per route, optimizing caching strategies and SEO metadata.

How do I optimize data fetching and caching strategies in Next.js App Router?

Optimizing Next.js App Router data fetching requires utilizing Server Components for direct database access and configuring caching strategies per route segment. This minimizes client-server waterfalls and improves rendering performance.