Nextjs Architecture

Name: Nextjs Architecture
Author: 89jobrien

89jobrien/steve

61 installs
4 repo stars
Updated April 11, 2026
89jobrien/steve

nextjs-architecture is a Claude Code skill for designing Next.js app architecture, App Router patterns, Server Components, and Pages-to-App-Router migration.

About

nextjs-architecture is a Claude Code skill for designing Next.js application architecture. It covers App Router structure, Server versus Client Components, performance strategies (static generation, ISR, streaming, image optimization), and migrating from the Pages Router to the App Router with worked before/after examples. A developer uses it when structuring a Next.js app or moving it to the App Router.

App Router directory structure with route groups, layouts, and route handlers
Server-Components-first guidance with 'use client' only when needed
Pages-Router-to-App-Router migration with before/after code

Nextjs Architecture by the numbers

61 all-time installs (skills.sh)
Ranked #1,203 of 2,245 Frontend Development skills by installs in the Skillselion catalog
Data as of Jul 28, 2026 (Skillselion catalog sync)

At a glance

nextjs-architecture capabilities & compatibility

Capabilities: nextjs architecture · app router migration · server components · performance optimization
Use cases: frontend · api development
Pricing: Free

From the docs

What nextjs-architecture says it does

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

SKILL.md

When migrating from Pages Router to App Router

SKILL.md

Server Components by default

SKILL.md

npx skills add https://github.com/89jobrien/steve --skill nextjs-architecture

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/89jobrien/steve/nextjs-architecture.svg)](https://skillselion.com/skills/89jobrien/steve/nextjs-architecture)

Installs	61
repo stars	★ 4
Last updated	April 11, 2026
Repository	89jobrien/steve ↗

What it does

Design a Next.js application's architecture and migrate it from the Pages Router to the App Router.

Who is it for?

Developers structuring a Next.js application or migrating it from the Pages Router to the App Router.

Skip if: Non-Next.js projects or teams not using React Server Components.

When should I use this skill?

Designing Next.js architecture, migrating to the App Router, implementing Server Components, or optimizing Next.js performance.

What you get

A Next.js architecture using Server Components by default with an App Router migration path.

Next.js architecture design
App Router structure
Pages-to-App migration plan

By the numbers

6 architecture best practices
5 performance strategies (SSG, ISR, streaming, image optimization, code splitting)

Files

SKILL.mdMarkdownGitHub ↗

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

1. Architecture Design: Designs Next.js application structure 2. App Router: Implements App Router patterns and routing 3. Server Components: Uses Server Components effectively 4. Performance: Optimizes Next.js for production 5. Migration: Migrates from Pages Router to App Router 6. 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 <Component {...pageProps} />; }

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


**2. Convert Pages**

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

// After: app/users/[id]/page.tsx export default async function UserPage({ params }) { const user = await getUser(params.id); return <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