Back to catalog / Developer tools
Vercel React Best Practices
Prioritized performance guidance for React and Next.js implementation, review, and refactoring.
Skills
Use this Vercel Engineering guide when writing, reviewing, or refactoring React or Next.js code. It groups advice by impact: async waterfalls, bundle size, server work, client fetching, rerenders, rendering, JavaScript, and advanced patterns. Start with a concrete bottleneck, then apply the matching rule—for example parallelize independent requests, defer an await until a branch needs it, import a module directly, or remove duplicate server work. The rules are review guidance, not measurements of a particular application. Check framework versions and evidence before changing code, and avoid applying micro-optimizations where they do not address a real cost.
Permissions
Prerequisites
- A React or Next.js project and the relevant source files.
Permissions
- Reads code and may propose or make requested edits; review scope and diffs and test behavior. This skill alone does not grant deployment or account access.
Limitations
Rules are general guidance; applicability depends on framework version, application architecture, and measurements.
Pinned upstream source
- Repository
- vercel-labs/agent-skills
- File path
- skills/react-best-practices/SKILL.md
- Pinned commit
063bee94c3f4df8453406c830b0a7df0f2860278- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Codex · Claude Code · Gemini CLI · GitHub Copilot · Cursor · Windsurf · Cline · OpenCode
Main topic
Take a coding Agent change from context to verification