UI/UX & Design · Blog Post
Vercel Agent Skills: React rules, UI audits, and the skills CLI
Vercel's official skill pack turns its React performance playbook and its web interface guidelines into instructions a coding agent loads on demand. It also comes from the same team that ships npx skills, the installer most skills on this site use.
By Mehadi Hasan 8 min read
What it is
vercel-labs/agent-skills is Vercel's public collection of skills for AI coding agents. The README describes skills as "packaged instructions and scripts that extend agent capabilities", and every skill follows the open Agent Skills format: a folder with a SKILL.md file, plus optional scripts/ and references/. That is the same shape Anthropic's skills repo defines, so these work in Claude Code and in any other agent that reads skill folders.
The pack covers three areas. Most of it is front-end code quality: React and Next.js performance, component composition, React Native, and view transitions. Then there are two review skills, one for UI and one for docs. The rest is Vercel-specific: deploying, using the CLI with tokens, and auditing a live project's cost and speed. As of November 17, 2026 the repo has 34,314 stars and 2,985 forks on GitHub, and it is MIT-licensed.
What's in the repo
There are nine skill folders. The names below are the ones in each SKILL.md frontmatter, which is what you pass to the installer. Several differ from their folder names (the React best-practices folder is react-best-practices, but the skill is vercel-react-best-practices).
vercel-react-best-practices
React
70 performance rules for React and Next.js in 8 categories, ranked from CRITICAL (waterfalls, bundle size) down to LOW (advanced patterns). One Markdown file per rule, each with an incorrect and a correct code example.
vercel-composition-patterns
React
8 rules in 4 categories on component API design: compound components instead of boolean props, lifting state, explicit variants, and the React 19 change that drops forwardRef.
vercel-react-native-skills
React
36 rules in 8 categories for React Native and Expo, led by list performance (FlashList, memoized items, stable callbacks), then animation, navigation, and UI patterns.
vercel-react-view-transitions
React
A guide to React's View Transition API: the <ViewTransition> component, addTransitionType, CSS recipes, and the transitionTypes prop on next/link. Five reference files cover patterns, Next.js, and troubleshooting.
web-design-guidelines
Design
A UI audit. It fetches Vercel's Web Interface Guidelines at run time, checks the files you name against them, and reports findings as file:line. Covers accessibility, focus states, forms, animation, typography, dark mode, and i18n.
writing-guidelines
Docs
The same audit pattern for prose. It fetches Vercel's writing handbook and checks docs for voice, structure, headings, code samples, and typography (80+ rules per the README).
deploy-to-vercel
Vercel
Deploys a project. It checks for a git remote, a linked project, and an authenticated CLI, then prefers git-push deploys. It always deploys as a preview unless you explicitly ask for production.
vercel-cli-with-tokens
Vercel
Drives the Vercel CLI with an access token instead of an interactive login. Useful for CI or for agents that cannot open a browser.
vercel-optimize
Vercel
A cost and performance audit of a deployed Vercel project. It pulls metrics, usage, and config through the Vercel CLI first, then reads only the routes and files those numbers point to.
One thing to know if you read the README first: some of its counts are behind the code. It says the React skill has "40+ rules across 8 categories". The skill's own SKILL.md says 70, and the rules/ folder holds 70 rule files. The React Native section of the README also lists an older, smaller count than the 36 rule files now in the folder. Trust the skill folders over the README.
How it works
The skills fall into two designs, and the difference matters.
The rulebooks (React best practices, composition, React Native) are local reference material. SKILL.md holds a priority table and a one-line index of every rule. Each rule lives in its own file with an impact level, a short reason, and an incorrect-versus-correct code pair. The agent reads the index when a React task comes up, then opens only the rule files it needs. A compiled AGENTS.md with every rule expanded is there for tools that want one file. The React categories, in priority order:
vercel-react-best-practices categories
1 Eliminating Waterfalls CRITICAL async- 2 Bundle Size Optimization CRITICAL bundle- 3 Server-Side Performance HIGH server- 4 Client-Side Data Fetching MEDIUM-HIGH client- 5 Re-render Optimization MEDIUM rerender- 6 Rendering Performance MEDIUM rendering- 7 JavaScript Performance LOW-MEDIUM js- 8 Advanced Patterns LOW advanced-
The rules are concrete. async-parallel says to use Promise.all() for independent awaits. bundle-barrel-imports says to import directly instead of through barrel files. server-auth-actions says to authenticate server actions the same way you would an API route. The ordering is the useful part: it tells the agent to fix request waterfalls before it starts adding useMemo.
The auditors (web-design-guidelines and writing-guidelines) are short and hold almost no rules themselves. Each one tells the agent to fetch a live rule file from another Vercel repo (vercel-labs/web-interface-guidelines or vercel-labs/writing-guidelines), read the files you named, and report problems as file:line. So the rules can change without a skill update, but the agent needs web access to run them, and the rule set you get today may not match the one you got last month.
The Vercel skills are different again. vercel-optimize is the heaviest thing in the repo: Node scripts, scanners, and reference playbooks. Its stated rule is "metrics first": it collects production signals with the Vercel CLI before it reads any source file. It needs Vercel CLI v53 or later, a linked project, and Node.js 20+. It supports Next.js, SvelteKit, and Nuxt, with limited Astro support, and it stops and asks before going further on other frameworks.
Installation
The repo installs through Vercel's skills CLI. Run it from your project. It asks which skills you want and which agents to install them for:
Install (interactive)
npx skills add vercel-labs/agent-skills
You don't need all nine. List them first, then install only the ones that fit your stack. The CLI README uses this example for one skill and one agent:
List, then pick one skill
npx skills add vercel-labs/agent-skills --list npx skills add vercel-labs/agent-skills --skill web-design-guidelines -a claude-code
Skills go into the current project by default. Add -g to install them for every project. The CLI needs Node.js 22.20 or later.
The skills CLI and find-skills
npx skills (the skills package, version 1.9.0, MIT) is worth knowing on its own. It installs skills from GitHub, GitLab, any git URL, or a local path. Its README says it supports OpenCode, Claude Code, Codex, Cursor, "and 75 more" agents. It also has find, list, check, update, and remove commands, and it writes a skills-lock.json with a content hash for each skill. By default it symlinks one copy of each skill into every agent's folder, so an update reaches all of them. It collects anonymous usage data; set DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 to turn that off.
The CLI repo also ships one skill, find-skills. It tells the agent to search for an existing skill when you ask "how do I do X" or "is there a skill for X", then check install counts, the source's reputation, and GitHub stars before it suggests anything. On the skills.sh all-time leaderboard, as of November 17, 2026, find-skills is #1 with 4.4M installs. From this repo, vercel-react-best-practices shows 908.1K installs and web-design-guidelines 873.7K.
Install find-skills
npx skills add https://github.com/vercel-labs/skills --skill find-skills
Using it day to day
There's no command to learn. Once installed, the agent picks a skill when your request matches its description. The README's own examples are plain requests: "Review this React component for performance issues", "Help me optimize this Next.js page", "Deploy my app".
For the UI audit, name the files. The skill takes a file or glob argument and asks you which files to review if you don't give any:
Example prompts
Review my UI in app/(marketing)/**/*.tsx Check this checkout form for accessibility problems Review this React component for performance issues Create a preview deployment and give me the link
Two habits help. First, install only the skills that match your stack. The React Native rules do nothing in a Next.js repo, and every installed skill adds its description to the agent's context. Second, read deploy-to-vercel before you let an agent run it. It is careful (preview by default, it asks which team to use), but it runs real CLI commands against your account.
Pricing
Free. The skills and the CLI are both MIT-licensed, and the React, design, and writing skills need nothing beyond your agent. The Vercel skills need a Vercel account. vercel-optimize also lists Observability Plus as a requirement for route-level recommendations. Without it, the skill stops and offers a scanner-only mode that can catch code issues but can't rank routes by real traffic or cost.
My take
If you build in React or Next.js, vercel-react-best-practices is the one to install. It's a clear example of a rulebook written for an agent instead of a person: an impact level on every rule, a code pair per rule, and a file layout that lets the agent read one rule instead of the whole guide. The impact ranking is the part a generic "write fast React" instruction can't give you.
web-design-guidelines suits anyone shipping UI, React or not, because it reviews files rather than framework APIs. Its trade-off is the live fetch. You always get the current rules, but the review depends on network access, and the content can change between runs. If you need repeatable audits, pin a copy of the guidelines yourself.
The Vercel-specific skills are only for Vercel users, and vercel-optimize pays off most for teams with real traffic and Observability Plus. If you don't write React and don't deploy on Vercel, skip this repo and install find-skills instead. It's a small, sensible default that helps an agent find the right pack for the job.
Frequently asked questions
Which skills does vercel-labs/agent-skills include?
Nine: vercel-react-best-practices, vercel-composition-patterns, vercel-react-native-skills, vercel-react-view-transitions, web-design-guidelines, writing-guidelines, deploy-to-vercel, vercel-cli-with-tokens, and vercel-optimize. Run npx skills add vercel-labs/agent-skills --list to see them before installing.
Do I need to deploy on Vercel to use these skills?
No. The React, composition, React Native, view transitions, web design, and writing skills are framework or code guidance and work in any project. Only deploy-to-vercel, vercel-cli-with-tokens, and vercel-optimize need a Vercel account, and vercel-optimize needs Observability Plus for route-level recommendations.
Why does web-design-guidelines need internet access?
The skill holds no rules itself. Each time it runs, it fetches the latest Web Interface Guidelines from the vercel-labs/web-interface-guidelines repo, checks your files against them, and reports findings as file:line. You always get the current rules, but results can change between runs.
What is find-skills and do I need it?
find-skills ships with Vercel's skills CLI (vercel-labs/skills). It tells your agent to search for an existing skill when you ask how to do something, and to check install counts, source, and GitHub stars before recommending one. It is optional, and it was #1 on the skills.sh all-time leaderboard as of November 17, 2026.