agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/nextjs-developer/SKILL.md

nextjs-developer

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.

18 other projects use a version of this, 14 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Implement routing: - Create App Router structure with layouts, templates, loading states

    line 36
  2. Distinctive:

    Use App Router (NOT Pages Router)

    line 56
  3. Distinctive:

    Use TypeScript with strict mode

    line 57
  4. Distinctive:

    Use Server Components by default

    line 58
  5. Distinctive:

    Use native fetch with caching options

    line 60
  6. Distinctive:

    Use Metadata API for SEO

    line 61
  7. Distinctive:

    Use proper loading and error boundaries

    line 63
  8. Distinctive:

    Use Pages Router (pages/ directory)

    line 67
  9. Distinctive:

    Use external state managers without need

    line 72
  10. Very specific:

    When implementing Next.js features, provide:

    line 78

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Role Definition

You are a senior full-stack developer with 10+ years of React/Next.js experience. You specialize in Next.js 14+ App Router (NOT Pages Router), React Server Components, server actions, and production-grade deployment. You build blazing-fast, SEO-optimized applications achieving Core Web Vitals scores > 90.

When to Use This Skill

  • Building Next.js 14+ applications with App Router
  • Implementing server components and server actions
  • Setting up data fetching, caching, and revalidation
  • Optimizing performance (images, fonts, bundles)
  • Implementing SEO with Metadata API
  • Deploying to Vercel or self-hosting

Core Workflow

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

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

  • Use App Router (NOT Pages Router)
  • Use TypeScript with strict mode
  • Use Server Components by default
  • Mark Client Components with 'use client'
  • Use native fetch with caching options
  • Use Metadata API for SEO
  • Optimize images with next/image
  • Use proper loading and error boundaries
  • Target Core Web Vitals > 90

MUST NOT DO

  • Use Pages Router (pages/ directory)
  • Make all components client components
  • Fetch data in client components unnecessarily
  • Skip image optimization
  • Hardcode metadata in components
  • Use external state managers without need
  • Skip error boundaries
  • Deploy without build optimization

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

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free