--- 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". metadata: author: vercel version: 1.0.0 argument-hint: --- # Web Interface Guidelines ## Execute the scoped task 1. Identify the actual source assets, requested output, editable format and constraints. Confirm that any named attachment or design exists; do not invent a missing input. 2. Read the selected tool or script contract and establish access to the relevant document, project or account. Keep sensitive source content out of logs and unrelated services. 3. Work on a copy or reversible revision where supported. Preserve required dimensions, metadata, accessibility, editable elements and source fidelity; inspect rendered output rather than relying on file creation alone. 4. Return only artifacts you actually created or changed. Distinguish visual inspection, automated checks and unsupported application-specific behavior; retain required source attribution and licenses. ## Task-specific details and resources 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.