48 lines
1.4 KiB
Markdown
48 lines
1.4 KiB
Markdown
---
|
|
name: ck-web-design-guidelines
|
|
description: Review UI code for Web Interface Guidelines compliance. Use when asked to review UI, check accessibility, audit design, review UX, or check a site against web interface best practices.
|
|
---
|
|
|
|
# Web Design Guidelines Review
|
|
|
|
Reviews files for compliance with the Vercel Web Interface Guidelines.
|
|
|
|
## When to Use
|
|
|
|
- User asks "review my UI" or "audit my design"
|
|
- Checking accessibility compliance
|
|
- Reviewing UX patterns against best practices
|
|
- Auditing a site or component for quality issues
|
|
|
|
## Don't Use When
|
|
|
|
- Reviewing backend or non-UI code
|
|
- Task is creative design work, not compliance review
|
|
|
|
## How It Works
|
|
|
|
1. Fetch the latest guidelines from the source URL
|
|
2. Read the specified files (or prompt user for files/pattern)
|
|
3. Check against all rules in the fetched guidelines
|
|
4. Output findings in 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 a web fetch tool to retrieve the latest rules. The fetched content contains all rules and output format instructions.
|
|
|
|
## Usage
|
|
|
|
When a file or pattern is provided:
|
|
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.
|