web-design-guidelines

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".
user-invocable	false
metadata	{"author":"vercel","version":"1.0.0","argument-hint":"<file-or-pattern>"}
version	1.0.0
scope	public

Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

How It Works

1. Fetch the latest guidelines from the source URL below
2. Read the specified files (or prompt user for files/pattern)
3. Check against all rules in the fetched guidelines
4. 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:

1. Fetch guidelines from the source URL above
2. Read the specified files
3. Apply all rules from the fetched guidelines
4. Output findings using the format specified in the guidelines

If no files specified, ask the user which files to review.

Error Handling

Guidelines URL Unreachable

If WebFetch fails (network error, 404, timeout):

• Report the error clearly: "Could not fetch guidelines from [URL]. Status: [error]."
• Do NOT proceed with guessed or remembered rules — guidelines may have changed.
• Suggest: (1) Check network connectivity, (2) Verify URL is still valid at https://github.com/vercel-labs/web-interface-guidelines, (3) User can paste guidelines content directly.

Large Codebases (50+ files)

If user provides a glob pattern matching many files:

• Suggest reviewing by page/feature area rather than all at once (e.g., "Start with your main layout and navigation components")
• Offer to review in batches: "I'll start with the first 10 most recently modified files. Want me to continue with the rest?"
• Prioritize: layout components > page components > utility components