| 1 | --- |
| 2 | name: web-design-guidelines |
| 3 | 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". |
| 4 | metadata: |
| 5 | author: vercel |
| 6 | version: "1.0.0" |
| 7 | argument-hint: <file-or-pattern> |
| 8 | --- |
| 9 | |
| 10 | # Web Interface Guidelines |
| 11 | |
| 12 | Review files for compliance with Web Interface Guidelines. |
| 13 | |
| 14 | ## How It Works |
| 15 | |
| 16 | 1. Fetch the latest guidelines from the source URL below |
| 17 | 2. Read the specified files (or prompt user for files/pattern) |
| 18 | 3. Check against all rules in the fetched guidelines |
| 19 | 4. Output findings in the terse `file:line` format |
| 20 | |
| 21 | ## Guidelines Source |
| 22 | |
| 23 | Fetch fresh guidelines before each review: |
| 24 | |
| 25 | ``` |
| 26 | https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md |
| 27 | ``` |
| 28 | |
| 29 | Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions. |
| 30 | |
| 31 | ## Usage |
| 32 | |
| 33 | When a user provides a file or pattern argument: |
| 34 | |
| 35 | 1. Fetch guidelines from the source URL above |
| 36 | 2. Read the specified files |
| 37 | 3. Apply all rules from the fetched guidelines |
| 38 | 4. Output findings using the format specified in the guidelines |
| 39 | |
| 40 | If no files specified, ask the user which files to review. |