HavenSkills

Vercel React Best Practices skill

By Vercel Labs

Vercel’s React Best Practices skill gives a coding agent a prioritized set of performance checks for React and Next.js. Start with one slow route and a reproducible symptom, such as two independent requests that run in sequence.

Install this skill

npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices

Run the command from your project directory. If your client is already running, reload it and confirm the skill is available before trying the example below.

Source repo

Ask your agent to install the skill
Install vercel-react-best-practices from vercel-labs/agent-skills in this project. Show me the destination folder and report any dependencies the source lists.

Install for your agent

Run the command for your client from your project directory.

Claude Code
npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices -a claude-code
Codex
npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices -a codex
Cursor
npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices -a cursor
GitHub Copilot
npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices -a github-copilot

How to use vercel-react-best-practices

Record the route, inputs and a baseline trace. Ask the agent to match the slowdown to a named rule, then inspect the data dependencies before changing code. If two reads are independent after the same authorization check, propose starting them together. Re-run the route with the same inputs and compare the traces.

Example prompt and what to check

Review this Next.js route for request waterfalls. Point to the two call sites, explain which data and authorization checks each fetch depends on, and propose one change. Show how to verify that the fetches overlap and the route renders the same response. Leave the code untouched until I approve the change.

Acceptance check The report identifies concrete file locations, explains whether the requests can safely overlap and preserves loading, error and authorization behavior. A before-and-after trace under the same conditions should show overlap before you count the change as a performance improvement.

What the upstream guide covers

The upstream SKILL.md indexes Vercel’s rules for asynchronous requests, bundle cost, server rendering, client data fetching, rerenders and other React work. It points to separate rule files in the same folder. Source checked on November 18, 2026 at commit 1a2c79d. The Source repo link opens that revision.

HavenSkills workflow check

No workflow check recorded yet. Use the sample task above to make your own check in your client.

Review methodology and recorded checks

Requirements, permissions and limits

The agent needs access to the relevant project files. Measuring a request change requires a runnable app and a trace or timings. Follow the project’s React and Next.js versions and code conventions. Keep server-only code, credentials and private data out of client bundles.

Author
Vercel Labs
Skill source
SKILL.md

Frequently asked questions

Which React performance rule should I start with?

Choose the rule that matches a measured bottleneck. For a slow initial response, trace fetch dependencies first. For slow client startup, inspect bundle contents and loaded JavaScript. Reproduce the symptom before changing the route.