Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Nextjs Developer

  • 4.2k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

How to architect, implement, and deploy production Next.js 14+ applications with App Router, server components, and optimized performance.

About

Next.js Developer is a specialist skill for building modern Next.js 14+ applications using App Router and React Server Components. Developers invoke it to architect file-based routing with layouts, implement server-side data fetching with caching and ISR, create server actions for form handling and mutations, optimize images and fonts, add loading and error boundaries, and configure production deployments. Core workflows span route structure planning, streaming SSR setup, SEO metadata generation via generateMetadata, performance optimization using next/image and next/font, and Vercel deployment validation. The skill enforces best practices: prefer server components by default, use native fetch with explicit cache directives, avoid Pages Router, and always run next build before deployment. App Router file-based routing with layouts, templates, and route groups Server Components and Server Actions for full-stack mutations and revalidation Data fetching

  • App Router file-based routing with layouts, templates, and route groups
  • Server Components and Server Actions for full-stack mutations and revalidation
  • Data fetching with native fetch, ISR (60s revalidate), and cache directives
  • SEO via generateMetadata with dynamic params and OpenGraph support
  • Image/font optimization, loading.tsx/error.tsx boundaries, and Vercel deployment

Nextjs Developer by the numbers

  • 4,217 all-time installs (skills.sh)
  • +134 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #113 of 2,277 Frontend Development skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

nextjs-developer capabilities & compatibility

Capabilities
app router architecture planning and scaffold ge · server component and server action implementatio · data fetching with caching and isr configuration · seo metadata generation via generatemetadata · performance optimization (images, fonts, bundle) · error and loading boundary setup · vercel deployment validation and configuration
Works with
vercel
Use cases
frontend · api development · seo · web design
Platforms
macOS · Windows · Linux
Runs
Hosted SaaS
Pricing
Free
npx skills add https://github.com/jeffallan/claude-skills --skill nextjs-developer

Add your badge

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

Listed on Skillselion
Installs4.2k
repo stars10.8k
Security audit3 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

What it does

Build production Next.js 14+ applications with App Router, server components, server actions, and optimized deployment to Vercel.

Who is it for?

Building full-stack web applications with Next.js 14+, implementing server-driven architectures, optimizing Core Web Vitals, and deploying to Vercel.

Skip if: Pages Router applications, legacy Next.js versions pre-13, static site generation without interactivity, or non-Vercel deployments requiring custom Docker setup.

When should I use this skill?

Working with Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance.

What you get

Fully functional Next.js application with App Router structure, server components, server actions, proper caching, SEO optimization, and production-ready Vercel deployment.

  • App Router file structure
  • Layout and page components with server-side data fetching
  • Server actions for mutations

By the numbers

  • Next.js 14 is the target version with App Router as primary routing mechanism
  • Supports ISR revalidation with configurable intervals (e.g., 60 seconds)
  • Core Web Vitals benchmark is > 90 on Lighthouse

Files

SKILL.mdMarkdownGitHub ↗

Next.js Developer

Senior Next.js developer with expertise in Next.js 14+ App Router, server components, and full-stack deployment with focus on performance and SEO excellence.

Core Workflow

1. Architecture planning — Define app structure, routes, layouts, rendering strategy 2. Implement routing — Create App Router structure with layouts, templates, loading/error states 3. Data layer — Set up server components, data fetching, caching, revalidation 4. Optimize — Images, fonts, bundles, streaming, edge runtime 5. Deploy — Production build, environment setup, monitoring

  • Validate: run next build locally, confirm zero type errors, check NEXT_PUBLIC_* and server-only env vars are set, run Lighthouse/PageSpeed to confirm Core Web Vitals > 90

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
App Routerreferences/app-router.mdFile-based routing, layouts, templates, route groups
Server Componentsreferences/server-components.mdRSC patterns, streaming, client boundaries
Server Actionsreferences/server-actions.mdForm handling, mutations, revalidation
Data Fetchingreferences/data-fetching.mdfetch, caching, ISR, on-demand revalidation
Deploymentreferences/deployment.mdVercel, self-hosting, Docker, optimization

Constraints

MUST DO (Next.js-specific)

  • Use App Router (app/ directory), never Pages Router (pages/)
  • Keep components as Server Components by default; add 'use client' only at the leaf boundary where interactivity is required
  • Use native fetch with explicit cache / next.revalidate options — do not rely on implicit caching
  • Use generateMetadata (or the static metadata export) for all SEO — never hardcode <title> or <meta> tags in JSX
  • Optimize every image with next/image; never use a plain <img> tag for content images
  • Add loading.tsx and error.tsx at every route segment that performs async data fetching

MUST NOT DO

  • Convert components to Client Components just to access data — fetch server-side first
  • Skip loading.tsx/error.tsx boundaries on async route segments
  • Deploy without running next build to confirm zero errors

Code Examples

Server Component with data fetching and caching

// app/products/page.tsx
import { Suspense } from 'react'

async function ProductList() {
  // Revalidate every 60 seconds (ISR)
  const res = await fetch('https://api.example.com/products', {
    next: { revalidate: 60 },
  })
  if (!res.ok) throw new Error('Failed to fetch products')
  const products: Product[] = await res.json()

  return (
    <ul>
      {products.map((p) => (
        <li key={p.id}>{p.name}</li>
      ))}
    </ul>
  )
}

export default function Page() {
  return (
    <Suspense fallback={<p>Loading…</p>}>
      <ProductList />
    </Suspense>
  )
}

Server Action with form handling and revalidation

// app/products/actions.ts
'use server'

import { revalidatePath } from 'next/cache'

export async function createProduct(formData: FormData) {
  const name = formData.get('name') as string
  await db.product.create({ data: { name } })
  revalidatePath('/products')
}

// app/products/new/page.tsx
import { createProduct } from '../actions'

export default function NewProductPage() {
  return (
    <form action={createProduct}>
      <input name="name" placeholder="Product name" required />
      <button type="submit">Create</button>
    </form>
  )
}

generateMetadata for dynamic SEO

// app/products/[id]/page.tsx
import type { Metadata } from 'next'

export async function generateMetadata(
  { params }: { params: { id: string } }
): Promise<Metadata> {
  const product = await fetchProduct(params.id)
  return {
    title: product.name,
    description: product.description,
    openGraph: { title: product.name, images: [product.imageUrl] },
  }
}

Output Templates

When implementing Next.js features, provide: 1. App structure (route organization) 2. Layout/page components with proper data fetching 3. Server actions if mutations needed 4. Configuration (next.config.js, TypeScript) 5. Brief explanation of rendering strategy chosen

Knowledge Reference

Next.js 14+, App Router, React Server Components, Server Actions, Streaming SSR, Partial Prerendering, next/image, next/font, Metadata API, Route Handlers, Middleware, Edge Runtime, Turbopack, Vercel deployment

Documentation

Related skills

How it compares

Specialized for Next.js 14+ App Router; differs from general React or Pages Router guidance by requiring Server Components by default and enforcing server-side rendering patterns.

FAQ

When should I use 'use client' directive?

Add 'use client' only at leaf boundaries where interactivity is required (forms, event listeners, hooks). Keep parent components as server components to maximize server-side rendering benefits.

How do I handle data fetching in Next.js 14?

Use native fetch with explicit cache directives: next: { revalidate: 60 } for ISR, cache: 'no-store' for dynamic data, or cache: 'force-cache' for static data. Never rely on implicit caching.

What must I validate before Vercel deployment?

Run next build locally to confirm zero type errors, verify NEXT_PUBLIC_* and server-only environment variables, run Lighthouse/PageSpeed to confirm Core Web Vitals > 90, then deploy.

Is Nextjs Developer safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Frontend Developmentfrontendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.