web-design-guidelines

To audit web UI files for accessibility and design best practices, provide a file path or pattern like `src/**/*.tsx` to the Skill. It fetches the latest Vercel Web Interface Guidelines and checks your code against those rules, outputting issues in a terse file:line format for quick fixes.

A UX audit against web interface guidelines is a rule-based review of your UI source code to catch accessibility and design compliance issues. You need one during development and code review cycles to ensure your interface matches current standards before deployment.

Yes, you can review React and CSS files together for web interface compliance by providing a matching pattern such as `src/**/*.tsx and src/**/*.css`. The Skill analyzes all targeted files against the fetched guideline rules and reports any violations found.

The best way to check HTML and React components for accessibility issues is running an automated rule-based audit that fetches current web interface guidelines. This catches UI and UX problems early, outputting precise file and line references for fast developer fixes.

Yes, the UI code audit output includes specific line numbers. It formats all accessibility, UX, and design guideline violations in a terse file:line syntax, allowing developers to locate and fix the exact source of each compliance issue quickly.

Automated guideline checks for web UI accessibility require a specific file or pattern input to function and cannot evaluate runtime visual rendering or dynamic user interactions. They are limited to static source code analysis against the fetched Vercel Web Interface Guidelines rule set.