| name | web-design-guidelines |
| description | Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". |
| when_to_use | When auditing web UI for best practices, checking accessibility, or reviewing design against Web Interface Guidelines. |
| allowed-tools | Read, Grep, Glob, WebFetch |
| version | 1.0.0 |
| metadata | {"author":"vercel","version":"1.0.0","argument-hint":"<file-or-pattern>"} |
Web Interface Guidelines
Review files for compliance with Web Interface Guidelines.
How It Works
- Fetch the latest guidelines from the source URL below
- Read the specified files (or prompt user for files/pattern)
- Check against all rules in the fetched guidelines
- Output findings in the terse
file:line format
Guidelines Source
Fetch fresh guidelines before each review:
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
Usage
When a user provides a file or pattern argument:
- Fetch guidelines from the source URL above
- Read the specified files
- Apply all rules from the fetched guidelines
- Output findings using the format specified in the guidelines
If no files specified, ask the user which files to review.
Related Skills
| Skill | When to Use |
|---|
| frontend-design | Before coding - Learn design principles (color, typography, UX psychology) |
| web-design-guidelines (this) | After coding - Audit for accessibility, performance, and best practices |
Design Workflow
1. DESIGN → Read frontend-design principles
2. CODE → Implement the design
3. AUDIT → Run web-design-guidelines review ← YOU ARE HERE
4. FIX → Address findings from audit
