Review files for compliance with Web Interface Guidelines.
How It Works
- Fetch the latest guidelines from the source URL below (if retrieval fails, follow the Retrieval Fallback section)
- Read the specified files (or prompt user for files/pattern)
- Check against all rules in the fetched guidelines
- Output findings in the terse
file:lineformat
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.
If the environment has no WebFetch tool, fall back to curl against the same URL and review with the same rules:
# 直连优先
curl -sL "https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md"
# 直连失败/过慢时走代理（代理地址按本机环境配置，替换为实际代理地址）
curl -sL -x "http://<proxy-host>:<proxy-port>" "https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md"
Direct connection and proxyPrioritize speed(You can test the latency of each once before choosing; the proxy port is not fixed, configure it according to the actual local setup).
Retrieval Fallback
If the guidelines cannot be retrieved — no network, both direct and proxied requests fail, or the upstream URL returns an error (e.g. 404 after a path change):
- Check whether a local copy of the guidelines exists (provided by the user, or saved from an earlier successful fetch). Use it only if it is the ruleset from this same source URL, and state clearly in the output that the rules come from a local copy that may be stale.
- If no such local copy is available, STOP: tell the user the guidelines source could not be retrieved and that the review cannot be completed. Never continue from memorized or assumed rules — findings not checked against a verified copy of the guidelines are invalid.
Usage
When a user provides a file or pattern argument:
- Fetch guidelines from the source URL above (on failure, follow the Retrieval Fallback section 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.