nextjs-architecture

Next.js Architecture

This skill provides Next.js architecture expertise including App Router, Server Components, performance optimization, and migration strategies.

When to Use This Skill

When designing Next.js application architecture
When migrating from Pages Router to App Router
When implementing Server Components
When optimizing Next.js performance
When making Next.js architecture decisions
When building full-stack Next.js applications

What This Skill Does

Architecture Design: Designs Next.js application structure
App Router: Implements App Router patterns and routing
Server Components: Uses Server Components effectively
Performance: Optimizes Next.js for production
Migration: Migrates from Pages Router to App Router
Best Practices: Applies Next.js best practices

How to Use

Design Architecture

Design the architecture for this Next.js application

Migrate this Pages Router app to App Router

Specific Patterns

Implement Server Components for this feature

Architecture Patterns

App Router Structure

app/ ├── (auth)/ │ ├── login/page.tsx │ └── register/page.tsx ├── dashboard/ │ ├── layout.tsx │ ├── page.tsx │ └── analytics/page.tsx ├── api/ │ └── users/route.ts └── layout.tsx

Server Components

Pattern:

Server Components by default
Client Components with 'use client'
Direct database access in Server Components
Streaming with Suspense

Performance

Strategies:

Static generation for known content
ISR for frequently changing content
Streaming for slow queries
Image optimization
Code splitting

Examples

Example 1: App Router Migration

Input: Migrate Pages Router to App Router

Output:

Next.js Migration: Pages Router → App Router

Migration Steps

1. Convert Layout

// Before: pages/_app.tsx
export default function App({ Component, pageProps }) {
  return &#x3C;Component {...pageProps} />;
}

// After: app/layout.tsx
export default function RootLayout({ children }) {
  return (
    &#x3C;html>
      &#x3C;body>{children}&#x3C;/body>
    &#x3C;/html>
  );
}

2. Convert Pages

// Before: pages/users/[id].tsx
export default function UserPage({ user }) {
  return &#x3C;UserProfile user={user} />;
}

// After: app/users/[id]/page.tsx
export default async function UserPage({ params }) {
  const user = await getUser(params.id);
  return &#x3C;UserProfile user={user} />;
}

## Best Practices

### Next.js Architecture

1. **Server First**: Use Server Components by default
2. **Client When Needed**: Add 'use client' only when necessary
3. **Static When Possible**: Generate static pages when feasible
4. **Stream Slow Queries**: Use Suspense for slow data
5. **Optimize Images**: Use Next.js Image component

## Related Use Cases

- Next.js architecture design
- App Router migration
- Server Components implementation
- Next.js performance optimization
- Full-stack Next.js development