| name | web-design-guidelines |
| description | Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.
|
| triggers | ["web design guidelines","vercel design","product ui standards","design checklist","review my UI","check accessibility","audit design","review UX","设计审查"] |
| metadata | {"author":"vercel","version":"1.0.0","argument-hint":"<file-or-pattern>"} |
| od | {"mode":"design-system","surface":"web","platform":"desktop","category":"design-systems","upstream":"https://github.com/vercel-labs/web-interface-guidelines","source-commit":"4e799d45c17aec1498c269287a83b9dba22b966b","preview":{"type":"markdown"},"example_prompt":"Review my UI code against the Vercel Web Interface Guidelines — check layout, typography, color, motion, and accessibility compliance.\n"} |
Web Interface Guidelines
Review files for compliance with Web Interface Guidelines.
How It Works
- Load the pinned guidelines from
references/guidelines.md — this is the default, reproducible execution path
- Optionally, fetch the latest guidelines from the upstream URL below and diff against the pinned snapshot to see if anything has changed
- Read the specified files (or prompt user for files/pattern)
- Check against all rules in the guidelines
- Output findings in the terse
file:line format
Guidelines Source
Default (pinned): The vendored copy at references/guidelines.md is the default execution path. It is a pinned snapshot of the upstream guidelines and guarantees the skill produces reproducible results in any runtime environment.
Upstream (live): For users who want the very latest rules, the live source is available at:
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
Fetching the live version is optional — the pinned snapshot is always the baseline.
Usage
When a user provides a file or pattern argument:
- Load
references/guidelines.md as the default source
- Optionally fetch the upstream URL to check for updates
- Read the specified files
- Apply all rules from the guidelines
- Output findings using the format specified in the guidelines
If no files specified, ask the user which files to review.
