vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

1.15x

Quality

—

Does it follow best practices?

Impact

66%

1.15x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

A clean, well-organized rule index that is token-efficient and well-structured, but it functions as a catalog without executable guidance, and its progressive-disclosure references point to files that are missing from the bundle.

Suggestions

Include the referenced bundle files (rules/*.md and AGENTS.md) so the progressive-disclosure navigation actually resolves, or remove the file references if the rules are not bundled.

Add at least one short executable code example (correct vs. incorrect) for the highest-priority CRITICAL rules so the body provides concrete, copy-paste-ready guidance rather than only names and summaries.

Add an explicit multi-step workflow with a validation checkpoint (e.g., verify the refactor preserves behavior / run the build) for the refactoring tasks the skill guides, since these are changes where errors must be caught early.

Dimension	Reasoning	Score
Conciseness	Lean index format with no padding and no explanation of concepts Claude already knows; every line is a rule name plus a one-line summary, matching the lean-and-efficient anchor.	3 / 3
Actionability	Provides a useful catalog of named rules with summaries but no executable code or concrete commands - it describes rather than instructs - so it lands at the some-guidance-but-incomplete level rather than copy-paste-ready level 3.	2 / 3
Workflow Clarity	The priority table and "When to Apply" list give sequence intent, but there is no multi-step workflow with explicit validation checkpoints for the refactoring work it guides, capping it at level 2.	2 / 3
Progressive Disclosure	The overview-to-detail structure is well designed and references are one-level-deep and clearly signaled, but the referenced files (rules/*.md, AGENTS.md) do not exist in the bundle, so navigation is broken and it cannot reach the level-3 clear-navigation anchor.	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.

A strong, well-structured description: third-person voice, concrete actions, explicit trigger guidance, and a clear niche. It clearly answers both what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - "writing, reviewing, or refactoring React/Next.js code" plus "data fetching, bundle optimization, or performance improvements" - matching the multiple-specific-actions anchor rather than the domain-only level 2.	3 / 3
Completeness	Explicitly answers both what ("performance optimization guidelines") and when with an explicit "This skill should be used when... Triggers on..." clause, satisfying the level-3 anchor and exceeding the implied-trigger level 2.	3 / 3
Trigger Term Quality	Natural terms a user would say ("React components", "Next.js pages", "data fetching", "bundle optimization", "performance improvements") are well covered; not just jargon, so above the some-relevant-keywords level 2.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Vercel React/Next.js performance with distinct triggers, occupying a niche unlikely to conflict with unrelated skills; above the somewhat-specific level 2.	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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry-data
Commit: fca5734

Reviewed: 1 day 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.