web-design-guidelines
Reviews UI source code against Vercel's Web Interface Guidelines, fetched fresh at review time - accessibility attributes, focus states, forms, animation, typography, images, performance, navigation and URL state, touch, dark mode, i18n, hydration safety and common anti-patterns. Use when asked to review, audit or lint the code of a component, page or stylesheet for UI quality, "check my UI against best practices", "review this form", or "audit this markup", even if the user does not name the guidelines. Reads files and reports findings as file:line. Not for judging a screenshot or a running page (use ux-review), not for a WCAG conformance audit of a live site (use the accessibility plugin), and not for choosing a visual direction (use frontend-design).
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- web-design-guidelines
- license
- MIT
- metadata
- { "author": "vercel", "upstream": "https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines" }
- description
- Reviews UI source code against Vercel's Web Interface Guidelines, fetched fresh at review time - accessibility attributes, focus states, forms, animation, typography, images, performance, navigation and URL state, touch, dark mode, i18n, hydration safety and common anti-patterns. Use when asked to review, audit or lint the code of a component, page or stylesheet for UI quality, "check my UI against best practices", "review this form", or "audit this markup", even if the user does not name the guidelines. Reads files and reports findings as file:line. Not for judging a screenshot or a running page (use ux-review), not for a WCAG conformance audit of a live site (use the accessibility plugin), and not for choosing a visual direction (use frontend-design).
- allowed-tools
- Read Grep Glob WebFetch(domain:raw.githubusercontent.com)
- argument-hint
- <file-or-glob>
02 资源文件 1
- 许可证LICENSE.txt2.0 KB
03 SKILL.md 正文
Web Interface Guidelines
Review the files the user names against Vercel's Web Interface Guidelines. This skill bundles no rules. The rules change upstream, so a copy here would go stale. Fetch them every time.
Steps
- Fetch the current guidelines with WebFetch from
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md. The file holds every rule and the output format to use. - If the fetch fails, stop and say so. Do not review from memory, because a review that quotes rules it did not read presents recall as a check.
- Read the files the user named. When the argument is a glob, expand it with Glob. When no files were named, ask which files or folder to review.
- Check every file against every rule in the fetched guidelines.
- Report in the format the fetched file specifies (terse
file:linefindings). Open with the file paths reviewed so the reader sees what was and was not covered.
Where this skill stops
| The ask | Use |
|---|---|
| Source code of components, pages or styles | This skill |
| A screenshot, mockup, or a judgment of usability and visual craft | ux-review |
| A running page: scan, keyboard and screen-reader pass, WCAG audit, ACR | the accessibility plugin |
| A site built on the U.S. Web Design System | uswds, then this skill for the rest |
| Picking a visual direction for new UI | frontend-design |
The guidelines overlap ux-review and the accessibility skills on focus-visible,
reduced motion and transition: all. They are the only source in this plugin for forms,
URL state, i18n and hydration-safety checks.
04 同仓库更多 Skills
ux-review
Judges an existing design for usability, accessibility and visual craft, and says what to change. Use when asked to review or critique a UI, screenshot, mockup, prototype, flow or component, to "roast" or grade a design, to explain why a page looks generic or AI-made, to check contrast, keyboard or reading-order risks from a design, or to answer whether a screen works for its user. Gives a readiness verdict and a ranked list of fixes with concrete values (label text, px size, hex). Judges what is shown; it does not build new UI (use frontend-design), review framework source line by line (use web-design-guidelines), or run live-page accessibility tests (use the accessibility plugin). To render the page in a real browser and make the fixes, use the ui-ux agent.
react-native-skills
React Native and Expo best practices for building performant mobile apps, from Vercel Engineering. Use when writing or reviewing React Native or Expo components, tuning list and scroll performance, building animations with Reanimated, handling images, safe areas, navigation, fonts or native modules, or structuring a monorepo with native dependencies. Applies to React Native code only, even if the user does not say "mobile". For web React performance use react-best-practices.
react-best-practices
React and Next.js performance rules from Vercel Engineering, ranked by impact. Use when writing, reviewing or refactoring React or Next.js code for speed - data-fetching waterfalls, bundle size, server components, re-renders, hydration, rendering cost - or when a page feels slow, a bundle is large or a component re-renders too often. Applies to React and Next.js code only, even if the user does not say "performance". For visual or usability review use ux-review; for component API design use composition-patterns.
composition-patterns
React component composition patterns for flexible, maintainable component APIs, from Vercel Engineering. Use when refactoring a component that has grown many boolean props, building or reviewing a shared component library or design-system wrapper, choosing between compound components, context providers, render props or explicit variants, or moving to React 19 APIs. Applies to React code only, even if the user does not say "composition". For render-and-look design review use ux-review; for performance rules use react-best-practices.
eng
Slash entry for the engineering agent. Use when the user types /core:eng, or asks to "use eng", "run the engineering pass" or "have engineering do" a fix, feature, refactor or code review in the current repo, even if they do not name the agent. Hands the task to the core:eng agent in a fresh context and returns its report.