Web Interface Review
Check UI source against Vercel's current interface guidelines and return file-level findings.
npx skills add vercel-labs/agent-skills --skill web-design-guidelines What it does
A polished screen can still contain accessibility, interaction, or implementation problems. This skill directs the agent to fetch current interface guidelines and review specified source files against them.
What changes after install
- Fetches the current rule source instead of relying only on a remembered checklist.
- Scopes the review to files or patterns supplied by the user.
- Returns concise findings linked to locations in the reviewed code.
Install
Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.
npx skills add vercel-labs/agent-skills --skill web-design-guidelines Before using Web Interface Review
- The agent needs network access to fetch the current Web Interface Guidelines, plus read access to the UI files or patterns you want reviewed.
Read the reviewed setup instructions for the selected workflow.
When to use it
- Reviewing an existing interface before a release.
- Checking forms, navigation, focus behavior, and other UI implementation details.
When not to use it
- Treating a source review as a complete accessibility audit.
- Expecting an original visual design to be generated from this review workflow.
Give the review a useful boundary
For a signup form, provide the form component, its validation logic, and any shared input or button components. Ask for findings that explain the observable problem and point to the responsible code. This is more actionable than asking an agent to “make the entire design better” without identifying the interface or its purpose.
The skill first retrieves the current Web Interface Guidelines from Vercel’s separate guideline repository. It then reads the selected files and produces a concise, location-based review. Because the rules are fetched at review time, internet access and a functioning fetch tool are part of the documented workflow.
What the review can and cannot establish
The linked guidelines cover topics such as accessibility, focus, forms, animation, typography, images, and interaction behavior. Source inspection can reveal a missing label or a problematic pattern, but it cannot by itself prove that the page works for every keyboard or screen-reader user. Follow up on the actual rendered interface, particularly on small screens and with reduced motion enabled.
If the guideline URL cannot be retrieved, preserve that limitation in the report. A review against an old local copy can still be useful, but it should not be described as using the latest rules.
Keep findings connected to user outcomes
For each proposed change, ask what a person would experience differently and whether the issue is reproducible. Address defects in important flows before visual preferences. Choose a design-generation skill when creating a new interface; choose this skill to examine existing UI code. SkillDex reviewed the instruction file and its source links, without executing a live accessibility assessment.
Related workflows
FAQ
- Does this skill work without network access?
- Its documented workflow fetches current guidelines. Without that access, the reviewer should disclose the limitation rather than pretend to use the latest rules.
- Does a clean report prove the site is accessible?
- No. Keyboard use, assistive technology, actual content, and rendered behavior still need appropriate checks.