Agent skill · DevOps & Cloud

nextjs-developer

Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, 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.

Jeffallangithub.com/JeffallanGitHub ↗
claude-codeMIT
Install
npx skills add Jeffallan/claude-skills --skill nextjs-developer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.1.0
Declared author: https://github.com/Jeffallan
Path: skills/nextjs-developer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 10,871 · +100 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the 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. ## 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: | Topic | Reference | Load When | |-------|-----------|-----------| | App Router | `references/app-router.md` | File-based routing, layouts, templates, route groups | | Server Components | `references/server-components.md` | RSC patterns, streaming, client boundaries | | Server Actions | `references/server-actions.md` | Form handling, mutations, revalidation | |

What's inside
Steps it walks through
  1. Core Workflow
  2. Reference Guide
  3. Constraints
  4. MUST DO (Next.js-specific)
  5. MUST NOT DO
  6. Code Examples
  7. Server Component with data fetching and caching
  8. Server Action with form handling and revalidation
  9. generateMetadata for dynamic SEO
  10. Output Templates
  11. Knowledge Reference
Ships with 5 files
  • references/app-router.md
  • references/data-fetching.md
  • references/deployment.md
  • references/server-actions.md
  • references/server-components.md
More from claude-skills
All skills →
About this skill
What does the nextjs-developer skill do?

Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, 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.

How do I install it?

Run `npx skills add Jeffallan/claude-skills --skill nextjs-developer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going