Back to catalog
Human reviewedDevelopment

Skill dossier

nextjs-developer

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A Next.js 14+ Skill centered on App Router, Server Components, Server Actions and metadata, with a build and env validation step before deploy.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Plans routes, layouts and rendering strategy in the App Router.
  • Keeps components server-side by default with explicit fetch caching options.
  • Writes Server Actions, generateMetadata and loading and error boundaries.
  • Validates with next build and environment checks before deploy.

Limitations & scope

  • Targets the App Router only and forbids Pages Router usage.
  • Examples reflect Next.js 14-era APIs and may need updating for newer releases.
  • The Core Web Vitals above 90 target is stated but not measured here.

Relevant for

  • React developers using the App Router
  • Teams focused on SEO
  • Developers deploying to Vercel

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
50.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/nextjs-developer/references/app-router.mdReference6.7 KB
skills/nextjs-developer/references/data-fetching.mdReference10.1 KB
skills/nextjs-developer/references/deployment.mdReference10.4 KB
skills/nextjs-developer/references/server-actions.mdReference9.4 KB
skills/nextjs-developer/references/server-components.mdReference8.1 KB
skills/nextjs-developer/SKILL.mdInstruction5.6 KB

SKILL.md frontmatter

{
  "name": "nextjs-developer",
  "description": "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.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "frontend",
    "triggers": "Next.js, Next.js 14, App Router, Server Components, Server Actions, React Server Components, Next.js deployment, Vercel, Next.js performance",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "typescript-pro"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Plan architecture

    Define app structure, routes, layouts and rendering strategy.

  2. 02
    Action

    Implement routing and data

    Create App Router files with loading and error states and server-side data fetching.

  3. 03
    Decision

    Validate before deploy

    Run next build, confirm zero type errors and check environment variables.

  4. 04
    Output

    Deliver code and rationale

    Provide app structure, components, actions, config and the rendering strategy chosen.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

167 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

106 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 106 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

56 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 56 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

5 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Check that server-only environment variables and Server Action inputs are not exposed to the client or left unvalidated.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/nextjs-developer # .claude/skills/nextjs-developer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/nextjs-developer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to build a product list page and confirm it uses a Server Component, explicit revalidation and loading and error files.

Prerequisites

  • Targets the App Router only and forbids Pages Router usage.
  • Examples reflect Next.js 14-era APIs and may need updating for newer releases.
  • The Core Web Vitals above 90 target is stated but not measured here.

Example prompts

Representative task

Using the nextjs-developer skill, build a products page with a Server Component fetching with 60-second revalidation, a createProduct Server Action, generateMetadata, and loading.tsx and error.tsx.

Inspect before use

Read the nextjs-developer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/nextjs-developer/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Concrete rules for client boundaries and explicit caching.
  • Includes build validation before deployment.

Considerations

  • Next.js APIs evolve quickly, so check against your installed version.
  • The project's AGENTS.md may require reading local Next docs first.
Research conclusion

A solid set of App Router conventions, best checked against your Next.js version.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/nextjs-developer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.