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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with executable examples, explicit constraints, and an excellent progressive-disclosure reference table. It loses points only on minor conciseness padding (a keyword-dump section) and small actionability gaps where helper functions and config are assumed rather than shown.

Suggestions

Remove or replace the 'Knowledge Reference' keyword list with actionable detail — it restates Next.js terminology Claude already knows without adding guidance.

Define the assumed helpers in the code examples (e.g., show a `fetchProduct` implementation or note it as a placeholder) and include a minimal `next.config.js` snippet since it is listed as an output template.

Add an error-recovery feedback loop to the Deploy step (e.g., 'if `next build` fails, fix type errors and re-run before deploying') to reach full workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with complete code examples and a lean reference table, but the 'Knowledge Reference' keyword dump and the 'Senior Next.js developer with expertise...' intro line restate concepts Claude already knows and could be trimmed. Not 5 due to these padded sections; not 3 because the bulk earns its place.	4 / 5
Actionability	Three complete, copy-pasteable TSX examples plus concrete MUST DO/MUST NOT DO constraints provide mostly executable guidance, but `db.product.create`, `fetchProduct`, and `next.config.js` are referenced without being defined. Not 5 because of these unspecified helper/config gaps.	4 / 5
Workflow Clarity	Five-step Core Workflow with an explicit validation checkpoint under Deploy ('run next build locally, confirm zero type errors... run Lighthouse/PageSpeed to confirm Core Web Vitals > 90'). Not 5 because validation is final-only with no error-recovery feedback loop; not 3 because a concrete checkpoint is present so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	Clear overview with a well-signaled reference table pointing to five one-level-deep files (all verified present: app-router.md, server-components.md, server-actions.md, data-fetching.md, deployment.md), each with a 'Load When' navigation cue. Content is appropriately split with easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: third-person voice, explicit 'Use when' trigger, a rich list of concrete capabilities, and a comprehensive trigger-term list with synonyms. It clearly communicates both what the skill does and when to invoke it with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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' — giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both what ('Invoke to configure route handlers...') and when ('Use when building Next.js 14+ applications...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms ('RSC', 'React Server Components', 'Server Components'), file names ('loading.tsx'), and deployment terms ('Vercel', 'Next.js deployment') that users would actually say.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Next.js 14+ App Router with specific triggers — minimizing overlap with generic React or frontend skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Path: skills/nextjs-developer/SKILL.md
Commit: 882ef55

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.