web-design-guidelines

To audit UI code for web interface guideline compliance, fetch current rules and evaluate target UI files to generate a concise compliance report identifying accessibility gaps and UX inconsistencies.

You can check web accessibility issues by running automated checks that compare your UI code against fetched design best practices, surfacing non-compliant patterns in a file:line format for review.

Yes, you can review specific files for UX compliance by providing a specific file list or file patterns, allowing the evaluation to target a defined set of UI files rather than the entire project.

The best way to ensure deterministic behavior during a UI review is to fetch fresh web interface guidelines before each evaluation, ensuring checks apply the most current rules to the target files.

Yes, web design guideline compliance checking operates without external dependencies, fetching the latest rules directly to evaluate target UI files and output results in the file:line format.

Limitations include relying on fetched web interface guidelines for each review session, meaning checks are constrained to current rules and the provided file patterns or specific file lists for evaluation.