web-design-guidelines

To audit UI code for accessibility gaps, provide your UI source files or patterns to review. The skill fetches the latest Web Interface Guidelines from a source URL, reads the target files, and checks them against all rules to output findings in a concise file:line format.

Yes, you can automate design reviews during PRs by applying this skill to your codebase and UI components. It reads target file patterns, checks them against fetched web guidelines, and reports accessibility and UX findings in a terse file:line style for quick PR feedback.

A UI accessibility lint check against web guidelines is an automated process that reads target UI files, fetches the latest interface rules from a source URL, and identifies accessibility and design quality gaps by reporting findings in a file:line format.

Yes, the design review tool works across projects by reading target files or patterns from any codebase. It fetches the latest guidelines from the specified source URL and audits UI components and design assets for accessibility conformance without requiring specific dependencies.

Accessibility audit findings are reported in a terse file:line format. After fetching guidelines and reading target UI files or patterns, the skill checks against all rules and outputs concise findings pinpointing exact locations of accessibility and UX gaps.

To check UI components against Web Interface Guidelines, provide the source files or patterns to review. The skill fetches the latest rules from the source URL, reads the target files, and identifies accessibility and UX gaps by reporting findings in a file:line format.