Web Design Guidelines Audit / Web 设计规范审计

Audit the requested files against the latest official guideline source. Keep evidence and recommendations tied to the inspected code.

根据最新官方规则审计指定文件，所有结论都必须对应到已检查的代码证据。

Load the guideline source / 加载规则源

Retrieve the current guideline document from:

https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md

Treat that document as an external MIT-licensed source. Record the retrieval date or commit when available. If the source cannot be reached, report the limitation and stop instead of substituting remembered rules.

从上述 Vercel Labs 官方地址读取当前规则，并记录读取日期或 Commit。无法获取时说明限制并停止，不用记忆中的规则替代。

Audit workflow / 审计流程

1. Confirm the requested file or glob scope.
2. Read the current guideline source.
3. Inspect every in-scope file before issuing findings.
4. Apply only rules relevant to the detected framework and UI surface.
5. Return each actionable finding with severity, file, line, evidence, violated rule, and a concise remediation direction.
6. State No findings when the inspected scope contains no supported issue.
7. 确认文件或 Glob 范围。
8. 读取当前官方规则。
9. 在输出结论前检查所有范围内文件。
10. 仅应用与当前框架和界面相关的规则。
11. 每条问题输出严重级别、文件、行号、证据、对应规则和精简修复方向。
12. 范围内无有证据支持的问题时输出 No findings。

Review surfaces / 检查范围

Use the official document to determine the exact current rules. Typical surfaces include:

• semantics, accessible names, keyboard behavior, focus, and announcements;
• forms, validation, errors, loading, empty, and disabled states;
• reduced motion, transition safety, and interaction feedback;
• typography, truncation, wrapping, and numeric presentation;
• responsive layout, touch targets, overflow, and zoom/reflow;
• images, icons, lazy loading, dimensions, and alternative text;
• navigation, URLs, deep links, state persistence, and browser behavior;
• performance-sensitive rendering and DOM patterns;
• theming, color-scheme metadata, localization, and internationalization.

具体规则以当次读取的官方文档为准，通常覆盖语义与可访问性、表单与状态、动效、排版、多端布局、图像、导航、性能、主题和国际化。

Evidence rules / 证据规则

• Do not report an issue without a matching code location.
• Do not treat an automated heuristic as proof when manual verification is required.
• Do not invent browser, assistive-technology, or runtime behavior that was not tested.
• Separate guideline violations from project-specific design preferences.
• Keep brand-system and product-specific rules outside this general web baseline.
• 没有对应代码位置时不输出问题。
• 需要人工验证的项目不能仅凭自动化启发式判定。
• 未测试的浏览器、辅助技术或运行时行为不得虚构。
• 通用 Web 基线与项目特定的品牌规范分开记录。

Output format / 输出格式

Use one line per finding:

[severity] path/to/file:line — evidence — violated rule — remediation direction

Finish with:

• audited scope;
• guideline source and retrieval date;
• finding counts by severity;
• checks that still require browser, keyboard, screen-reader, zoom, or performance verification;
• confirmation that the audit did not modify project files.

最后附上审计范围、规则源与读取日期、严重级别统计、待手动验证项和未修改项目文件的确认。