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

82%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

64%

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

This is a solid, actionable Next.js skill with excellent code examples and clear constraints. Its main weaknesses are the missing bundle files that the reference table points to, some verbosity in the introductory framing and knowledge reference section, and a workflow that lacks intermediate validation checkpoints between the architecture and deployment phases.

Suggestions

Add intermediate validation steps to the core workflow (e.g., 'after implementing routing, run next build to verify route resolution' or 'after data layer setup, test server component rendering')

Create the referenced bundle files (references/app-router.md, references/server-components.md, etc.) or remove the reference table if they won't be provided

Remove the introductory role description line and the Knowledge Reference keyword list at the bottom — these consume tokens without adding actionable guidance

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary framing ('Senior Next.js developer with expertise in...') and the Knowledge Reference section at the bottom is a keyword dump that adds little value. The constraints section is well-structured but some items explain things Claude already knows (e.g., what next/image does).	2 / 3
Actionability	Provides fully executable, copy-paste-ready code examples for server components with data fetching, server actions with form handling, and generateMetadata. The constraints are specific and concrete (e.g., 'use native fetch with explicit cache/next.revalidate options'). The code examples are complete TypeScript/TSX with file paths.	3 / 3
Workflow Clarity	The core workflow lists steps at a high level but validation only appears at the final deploy step. There are no intermediate validation checkpoints (e.g., after implementing routing or data layer). The deploy validation step is good but the overall workflow lacks feedback loops for error recovery during development phases.	2 / 3
Progressive Disclosure	The reference table with 'Load When' guidance is well-structured and clearly signaled. However, no bundle files are provided, meaning all five referenced files (references/app-router.md, etc.) are missing. The skill inlines substantial code examples that could arguably live in reference files, while the actual reference files don't exist to support the progressive disclosure pattern.	2 / 3
	Total	9 / 12 Passed

Description

100%

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

This is an excellent skill description that clearly defines its scope around Next.js 14+ App Router development. It lists specific concrete actions, provides explicit 'Use when' guidance, and includes a comprehensive list of trigger terms covering natural variations users would employ. The description is well-structured, uses third person voice appropriately, and would be easily distinguishable from other skills in a large skill library.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, deploy to Vercel.	3 / 3
Completeness	Clearly answers both 'what' (configure route handlers, implement middleware, set up API routes, streaming SSR, etc.) and 'when' with an explicit 'Use when' clause at the start and a 'Triggers on' list at the end.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including common variations: 'Next.js', 'Next.js 14', 'App Router', 'RSC', 'use server', 'Server Components', 'Server Actions', 'React Server Components', 'generateMetadata', 'loading.tsx', 'Vercel'. These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Next.js 14+ with App Router specifically. The trigger terms are specific enough (App Router, RSC, Server Actions, generateMetadata, loading.tsx) to distinguish from generic React skills or other framework skills.	3 / 3
	Total	12 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Commit: e8be415

Reviewed: 4 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.