web-design-guidelines-review

Audit UI code by comparing it against a local design system to surface concrete issues and inconsistencies. The process reviews interactions, accessibility, forms, motion, performance, and copy, outputting findings grouped by file and line with actionable remediation guidance.

A design review of frontend diffs checks for conformance with local design guidelines and tokens. It focuses on interactions, accessibility, forms, motion, performance, and copy, producing actionable findings grouped by affected files to accelerate fixes.

Yes, a design-system map located under references/core and references/frameworks is required. This style guide provides the necessary baseline to audit frontend projects for accessibility, interactions, and visual fidelity, generating clear remediation guidance.

Yes, you can use a UI audit to check frontend forms and motion. The review workflow focuses on interactions, accessibility, forms, motion, performance, and copy, ensuring conformance with local design guidelines and surfacing concrete issues with actionable remediation steps.

The best way to surface visual inconsistencies is running a findings-first UI review against local design guidelines. This produces actionable findings grouped by affected files and line numbers, providing clear remediation guidance to accelerate fixes.