Vercel Agent Skills
Review code, investigate metrics, and deploy
Choose focused skills for React performance, interfaces, technical writing, production metrics, or deployment, with findings tied to files and checks.
- GitHub stars
- 33,222
- Checked
- Categories
- EngineeringProduct & Project
Review one real route and verify one change
Start with React performance and a page that has a reproducible problem. Understand request dependencies and loading behavior, make the best-supported small change, and repeat the same checks without inventing measurements.
Pick a task and get started
Each task includes its own installation command. Run it in a terminal at the project root, then open Claude Code in that same project. Have the assistant confirm the selected SKILL.md and companion files before providing brief.md and the target files.
Investigate dependencies and initial loading, then verify a small change.
Install the selected skill
Start with React performance or copy another task’s command. The installer is pinned to 1.7.4; skill content comes from the current repository at project scope by default.
Read the author’s setup guidenpx [email protected] add vercel-labs/agent-skills --skill vercel-react-best-practices -a claude-codeFirst run: locate, change, then compare
Write the target route, reproduction steps, symptoms, React/framework versions, and existing check commands in brief.md. Preserve a useful baseline. Install vercel-react-best-practices from task one and confirm that the assistant reads its actual file. Request findings with file locations, one supported small change, project checks, and a rerun with the same data.
React skill and rule indexGive your AI this first task
These are editorial prompts with replaceable paths and filenames. Static source review is not presented as a benchmark or deployment performed by us.
Use vercel-react-best-practices for the React/Next.js route in brief.md and its necessary dependencies. Check installed React/framework versions and existing validation commands. Identify the order of authorization, requests, and component loading. Prioritize independent requests that wait unnecessarily and heavy components loaded before they are needed. Give each finding a file location, applicable rule, user impact, and verification method. Fetch private data only after its authorization checks. Explain cache lifetime and user isolation; React cache is not a persistent cross-request cache. If a concrete problem is established, implement the best-supported minimal change while preserving interfaces and behavior; otherwise report that no supported change was found. Run relevant checks and repeat the original flow with the same input. If measurement tools are unavailable, report structural changes and checks without claiming a speedup percentage. Return the change summary, results, and remaining issues.
Check what you receive
- Findings with file locations and relevant rules.
- A scoped patch when justified, or a reason that no change is needed.
- Comparable checks and unmeasured outcomes.
More about this skill
This Vercel-maintained collection currently has nine skill entries. Some organize engineering guidance for code reviews, some retrieve current interface or writing rules, and others use Vercel CLI data to investigate a deployed project or guide a deployment. Choose the entry that matches the work.
The React performance skill currently lists 70 rules across eight categories: waterfalls, bundle size, server and client data fetching, rerenders, rendering, JavaScript, and advanced patterns. Priorities help focus attention; recommendations still depend on framework versions, authorization, and actual data dependencies.
The five tasks below cover different deliverables. The entry map also explains composition, native apps, view transitions, and token-based CLI setup. Start locally for code review; use vercel-optimize when production evidence is needed to decide which routes deserve attention.
Sources and verification
Sources checked
Reviewed at 1a2c79d across all nine entry files, selected rules, the reporting workflow, external guidelines, and deployment documentation. No installation or Vercel operation was performed.