Skip to content
cccskills
FreePublished on GitHub

nextjs-developer

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.

The English summary is being prepared. Showing the original description.

Works withVercel
See how to install

Files included (6)

  • SKILL.md3.8 KB
  • references/app-router.md6.9 KB
  • references/data-fetching.md10.3 KB
  • references/deployment.md10.5 KB
  • references/server-actions.md9.6 KB
  • references/server-components.md8.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to "review my paper," "simulate peer review," or "give my paper a peer review.

The English summary is being prepared. Showing the original description.

zebbern/claude-code-guide4.7KUpdated Oct 19, 2026

This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.

The English summary is being prepared. Showing the original description.

zebbern/claude-code-guide4.7KUpdated Oct 19, 2026

This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.

The English summary is being prepared. Showing the original description.

zebbern/claude-code-guide4.7KUpdated Oct 19, 2026

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

The English summary is being prepared. Showing the original description.

zebbern/claude-code-guide4.7KUpdated Oct 19, 2026

Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.

The English summary is being prepared. Showing the original description.

zebbern/claude-code-guide4.7KUpdated Oct 19, 2026

Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.

The English summary is being prepared. Showing the original description.

zebbern/claude-code-guide4.7KUpdated Oct 19, 2026

See all skills by zebbern

Report a problem with this skill