Publisher: Vercel · Editorial profile by AI Tools Ratings · Review method
Not runtime tested; source-document review only. No security certification.
What task is this skill designed for?
Review a slow React route for unnecessary sequential requests and expensive client imports, then propose one measurable change.
What input and output should you expect?
Input: The route and component files, framework version, an observed bottleneck and a reproducible measurement setup.
Output: Expected, not independently tested: code-context findings and proposed refactors linked to the bundled rules. No benchmark improvement is claimed by this directory.
What does it need to run?
An agent that can load the repository’s skill format, access to the React or Next.js project and the rule references. Build tools and profiling are needed to validate an implementation change.
The author repository publishes Agent Skills-format instructions. Client-specific installation and tool dependencies must be checked; no Codex, Claude Code or Cursor runtime compatibility is independently verified here.
How should you approach installation?
- Read the pinned source and the relevant rule files, plus the repository’s installation guidance.
- Use the documented skill installer or manual mechanism for your agent, then verify the installed name and scope.
- Start with a code-only review of one route and authorize refactoring separately.
Installation guide: discovery, dependencies and runtime checks
What files, accounts or data can it access?
Reads source and may edit components or data-fetching logic if authorized. Dependency or server changes should stay within the review scope and avoid exposing private application data in reports.
What does the skill cost?
The repository declares MIT licensing; agent usage and hosting or profiling services are separate costs.
What are its limits and alternatives?
A pattern can be correct for one framework version and inappropriate for another. Static advice cannot establish a runtime bottleneck. The source’s frontmatter name differs from its repository folder name, so verify the installed directory and discovery name.
Use a browser or server profiler first when the bottleneck is unknown. Choose this skill to interpret a specific React performance issue and evaluate code changes against documented patterns.
What could you ask in a small trial?
Try this with a small sample:
Review this route for request waterfalls and unnecessary client-side dependencies. Cite the relevant rule, propose one change, and define a before-and-after measurement without claiming an unmeasured speedup.
How would you verify the result?
- Reproduce the baseline using the same build mode, data and environment.
- Confirm the proposed refactor preserves loading, error and user-visible behavior.
- Measure the relevant metric after the change and retain raw observations.
Use a baseline and record acceptance evidence before treating a successful task as a reliable workflow.
Which source and license were checked?
Read the reviewed SKILL.md at its pinned commit · Complete reviewed folder
Repository and current publisher guidance
Checked:
MIT — declared in the repository README at the reviewed commit; no separate license file was found in the inspected root or skill folder. Confirm third-party material terms before redistribution. License evidence
Version details and review scope
Source: vercel-labs/agent-skills/skills/react-best-practices
Reviewed commit: 063bee94c3f4df8453406c830b0a7df0f2860278
SKILL.md SHA-256: 71ed7794962fa6e803ee83030517b5b93a9f70fbfeb431ec4535c5480a8d8355
Source-document review. Source text and stated dependencies were inspected for this profile. Referenced code was not comprehensively audited, no runtime test was performed, and source files are not mirrored here.