# Nextjs App Router Patterns
> Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
Source: https://skillsagentes.com/skills/wshobson/agents/nextjs-app-router-patterns
Repository: https://github.com/wshobson/agents
Author: wshobson
License: MIT
Updated: hace 2 meses
Context cost: 53 tok installed, 929 tok once triggered, 3.4k tok with every bundled file
Bundle: 2 files, 13 KB
Permissions requested: none declared
## Install
```bash
npx -y skills add wshobson/agents --skill nextjs-app-router-patterns --agent claude-code
```
## What it does
- Aplica patrones de arquitectura de Next.js 14+ App Router: Server Components, streaming, rutas paralelas e interceptadas
- Define convenciones de archivos (layout.tsx, page.tsx, loading.tsx, error.tsx, route.ts, etc.)
- Guía la elección entre rendering Server, Client, estático, dinámico y streaming
- Establece buenas prácticas de data fetching, caching y Server Actions
## Use it when
- Construir nuevas aplicaciones Next.js con App Router
- Migrar de Pages Router a App Router
- Implementar Server Components y streaming
- Configurar rutas paralelas e interceptadas u optimizar data fetching/caching
## What triggers it
- "Ayúdame a migrar mi app de Pages Router a App Router en Next.js"
- "Cómo implemento streaming con Suspense en Next.js 14"
- "Necesito configurar rutas paralelas en mi proyecto Next.js"
## Before you install
- Requiere Next.js 14+ con App Router; hay detalles adicionales en references/details.md.
## Files
- SKILL.md — 4 KB
- references/details.md — 10 KB
## SKILL.md
Reproduced verbatim from wshobson/agents under MIT. This section is the upstream document and is in English.
# Next.js App Router Patterns
Comprehensive patterns for Next.js 14+ App Router architecture, Server Components, and modern full-stack React development.
## When to Use This Skill
- Building new Next.js applications with App Router
- Migrating from Pages Router to App Router
- Implementing Server Components and streaming
- Setting up parallel and intercepting routes
- Optimizing data fetching and caching
- Building full-stack features with Server Actions
## Core Concepts
### 1. Rendering Modes
| Mode | Where | When to Use |
| --------------------- | ------------ | ----------------------------------------- |
| **Server Components** | Server only | Data fetching, heavy computation, secrets |
| **Client Components** | Browser | Interactivity, hooks, browser APIs |
| **Static** | Build time | Content that rarely changes |
| **Dynamic** | Request time | Personalized or real-time data |
| **Streaming** | Progressive | Large pages, slow data sources |
### 2. File Conventions
```
app/
├── layout.tsx # Shared UI wrapper
├── page.tsx # Route UI
├── loading.tsx # Loading UI (Suspense)
├── error.tsx # Error boundary
├── not-found.tsx # 404 UI
├── route.ts # API endpoint
├── template.tsx # Re-mounted layout
├── default.tsx # Parallel route fallback
└── opengraph-image.tsx # OG image generation
```
## Quick Start
```typescript
// app/layout.tsx
import { Inter } from 'next/font/google'
import { Providers } from './providers'
const inter = Inter({ subsets: ['latin'] })
export const metadata = {
title: { default: 'My App', template: '%s | My App' },
description: 'Built with Next.js App Router',
}
export default function RootLayout({
children,
}: {
children: React.ReactNode
}) {
return (
{children}
)
}
// app/page.tsx - Server Component by default
async function getProducts() {
const res = await fetch('https://api.example.com/products', {
next: { revalidate: 3600 }, // ISR: revalidate every hour
})
return res.json()
}
export default async function HomePage() {
const products = await getProducts()
return (
Products
)
}
```
## Detailed patterns and worked examples
Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
## Best Practices
### Do's
- **Start with Server Components** - Add 'use client' only when needed
- **Colocate data fetching** - Fetch data where it's used
- **Use Suspense boundaries** - Enable streaming for slow data
- **Leverage parallel routes** - Independent loading states
- **Use Server Actions** - For mutations with progressive enhancement
### Don'ts
- **Don't pass serializable data** - Server → Client boundary limitations
- **Don't use hooks in Server Components** - No useState, useEffect
- **Don't fetch in Client Components** - Use Server Components or React Query
- **Don't over-nest layouts** - Each layout adds to the component tree
- **Don't ignore loading states** - Always provide loading.tsx or Suspense
---
Skills Agentes — https://skillsagentes.com/skills/wshobson/agents/nextjs-app-router-patterns