design-audit

To audit frontend code for design drift, compare a page's live implementation against its Figma reference and current design system. This generates a structured Markdown audit documenting deviations, rationale, and recommended fixes.

Yes, you can check design system token usage during a migration code review by applying the audit to frontend codebases. It enforces a schema tracking migration status and design-system usage to ensure actionable remediation.

The best way to compare live UI implementation with Figma designs is by providing the Figma file URL and page routes to initiate an automated audit. This surfaces discrepancies and produces a comprehensive Markdown report.

Yes, the design audit works for desktop and mobile frontend variations. It applies to frontend codebases across routes or component paths to surface discrepancies and document findings with evidence.

When auditing frontend quality for visual inconsistencies, the process requires a Figma file URL and accessible page routes or component paths to function. It outputs a structured Markdown audit and does not automatically apply code fixes.