Nextjs Developer
Use when building Next.js 14+ applications with App Router, server components, or server actions.
Before & after
Same prompt, same agent — the only difference is the skill.
Next.js 14+ uses App Router and Server Components by default, which changes how you fetch data. You can fetch directly in server components without needing separate API routes. You'd want to use the fetch API in your component and it will automatically cache the result. You could also use third-party data-fetching libraries if that fits your needs better. You might need to set up error boundaries and loading states so your users see something while data is loading. You could also use dynamic rendering if you need real-time data. It might help to know if you need real-time data, static data, or a mix of both. Have you already set up your project structure, and do you know what data source you're fetching from?
DATA FETCHING IN NEXT.JS 14+ SERVER COMPONENTS
PATTERN 1: STATIC DATA (default, fastest)
// app/posts/page.tsx (Server Component)
export default async function PostsPage() {
const posts = await fetch("https://api.example.com/posts")
.then(r => r.json());
return (
<div>
{posts.map(post => <PostCard key={post.id} post={post} />)}
</div>
);
}
Behavior: Builds at deploy time, cached forever
TTL: 3600s (1 hour default, overrideable)
Best for: Blog posts, docs, marketing pages
PATTERN 2: DYNAMIC DATA (real-time)
export const revalidate = 0;
export default async function DashboardPage() {
const data = await fetch("https://api.example.com/dashboard", {
cache: "no-store"
}).then(r => r.json());
return <Dashboard data={data} />;
}
Best for: Dashboards, user-specific data, live feeds
PATTERN 3: ISR (Incremental Static Regeneration)
export const revalidate = 60;
Behavior: Serves cached page, regenerates in background every 60s
Best for: Product listings, top news (semi-fresh data)
PATTERN 4: ERROR BOUNDARY + LOADING STATE
// app/posts/loading.tsx (auto-shown while fetching)
export default function Loading() {
return <SkeletonList count={5} />;
}
// app/posts/error.tsx (auto-shown on fetch failure)
"use client";
export default function Error({ error }) {
return <div>Error loading posts: {error.message}</div>;
}
METADATA FOR SEO
export const metadata = {
title: "Posts",
description: "Our latest posts",
openGraph: { image: "og-image-url" }
};
DEPLOYMENT TO VERCEL
1. Connect GitHub repo
2. Vercel auto-detects Next.js
3. Sets environment variables
4. Deploys on every push to main
COMMON MISTAKE: Fetching in useEffect on client components
// Wrong (defeats Server Component caching)
"use client";
useEffect(() => fetch("/api/posts"), []);
// Right (fetch in server component)
export default async function Posts() {
const posts = await fetch(...);
}
TIMING: ISR (60s) fast path average 20ms, dynamic (0s) path 400-800ms.About this skill
name: nextjs-developer description: Use when Use when building Next.js 14+ applications with App Router, server components, or server actions.
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.
What you get
- Public GitHub repo
- the skills/nextjs-developer folder with SKILL.md and references.
Customize your output
- Fork the repo and extend the skill's reference files for your own stack conventions.
Example output
Activates on a matching request (e.g. building or reviewing Nextjs Developer code) and can chain with other skills in the pack.
Best for
Full-stack developers and engineering teams using Claude Code.
SKILL.md preview
---
name: nextjs-developer
description: Use this skill when building Next.js 14+ applications with the App Router, server components, or server actions, including route handlers, middleware, streaming SSR, and Vercel deployment.
version: 1.0.0
category: Development / Frontend
author: AgentVolt
license: proprietary
tags:
- development
- frontend
---
# Nextjs Developer
Implements Next.js 14+ App Router applications — server components, server actions, route handlers, middleware, streaming SSR, SEO metadata, and Vercel deployment.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Angular Architect
Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance.
Vue Expert (JS)
Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript.
Flutter Expert
Use when building cross-platform applications with Flutter 3+ and Dart.
React Expert
Use when building React 18+ applications in .jsx or .tsx files, Next.js App Router projects, or create-react-app setups.