web-design-guidelines

To audit UI code for web design compliance, run this skill against your UI files by providing specific file paths or patterns, such as src/**.html or styles/*.css. It fetches the latest Web Interface Guidelines and reports non-conformant findings in a concise file:line format.

A UI code review for accessibility and UX quality compares your frontend code against Web Interface Guidelines to identify design inconsistencies and accessibility gaps. This skill fetches the latest guidelines, reads your specified files, and outputs a terse file:line report of non-conformant elements.

Yes, you can review multiple UI files for design consistency at once. By providing file path patterns like src/**.html or styles/*.css, the skill reads all specified files and generates a consolidated report covering accessibility, UX quality, and overall design organization.

No, a web design audit using this skill requires no external dependencies or components. It independently fetches the latest Web Interface Guidelines from a remote source, reads your specified UI files, and generates a compliance report without needing additional setup.

The best way to check frontend code against Web Interface Guidelines is to run an automated skill that fetches the latest standards and compares your code. This skill surfaces accessibility, UX, and design inconsistencies, reporting findings tersely in a file:line format.

You need a UI compliance audit for web design when you want to ensure your UI code aligns with Web Interface Guidelines, reducing accessibility gaps and design inconsistencies across a project before deployment or during a code review.