| name | web-design-guidelines |
| description | Code-generation skill for reviewing UI implementation against external web interface guidelines when guideline compliance is the explicit task. |
| metadata | {"family":"design","owner":"design + engineering","last_reviewed":"2026-04-30T00:00:00.000Z","version":"1.0.0","author":"vercel","argument-hint":"<file-or-pattern>"} |
Web Interface Guidelines
This is a code-generation skill. Use it only for UI review that should lead to repo implementation changes.
Strict Trigger
Use this skill only when at least one is true:
- the user explicitly asks for a guidelines-based UI review
- the task specifically references Vercel or external interface guidelines
- the review output, not implementation, is the immediate goal
Do not load this as the default frontend skill. Use frontend-design for normal UI implementation work.
Review Workflow
- fetch the latest external guidelines if the environment supports it
- inspect the specified files or the files relevant to the task
- compare implementation against the guidelines
- return findings that are actionable in this repo
Fallback Rule
If fresh guideline fetch is unavailable, state that limitation and review against:
- the most recent locally available guidance
- current repo design conventions
- accessibility and performance rules already enforced in the repo
Output Contract
Return findings only:
file:line for each issue
- short rule-oriented explanation
- no broad essay unless the user asks for one
Repo Reminder
A guidelines review should still respect repo-specific rules:
- thin routes
- feature-owned UI
- shared primitives in
src/components/ui
- no retired UI locations