web-design-guidelines

To audit UI code, you apply web interface guidelines to your frontend project files. This skill fetches up-to-date rules from official sources and evaluates your code to identify accessibility and usability gaps, outputting findings in a file:line format.

Yes, you can review a design system or component library for usability gaps. The skill analyzes UI files to detect semantic structure, color contrast, and interaction pattern issues across frontend projects before release.

The best way to detect color contrast issues is by evaluating your UI code against official web interface guidelines. The skill fetches these rules and scans your files to flag accessibility violations in a precise file:line format.

Yes, the accessibility review works with existing frontend design patterns. The skill evaluates files or patterns you provide from your codebase, assessing them against fetched web guidelines to ensure your current UI meets compliance standards.

Accessibility violations are reported in a file:line format. After fetching and applying web interface guidelines to your UI code, the skill outputs specific findings that pinpoint exactly where semantic structure or interaction gaps occur.

Fetching rules from a web guidelines source ensures your UI review uses the most up-to-date accessibility standards. The skill retrieves official compliance rules dynamically to accurately evaluate your frontend files for current usability gaps.