comprehensive-design-audit

To audit a design system for token and accessibility gaps, you can run a multi-phase analysis that scans components, identifies missing patterns, and generates a prioritized remediation backlog with file-level references.

Finding inconsistent token architecture in a large component library requires a deep context analysis that reviews token naming conventions across components and outputs a concrete action plan for migration and standardization.

Yes, you can generate an action plan for outdated design system documentation by defining audit goals during discovery, running a deep analysis on existing guidelines, and producing a concrete backlog with migration steps.

A design system audit works for a component API with 150+ components by systematically scoping the scale, applying deep context analysis to identify API gaps, and delivering actionable recommendations with user checkpoints.

To start a design system audit using Gemini, initiate a discovery phase to define known issues and success metrics, then proceed through initial scans, clarifying questions, and deep analysis to generate actionable insights.

Your design system audit needs clarifying questions before analysis to accurately scope audit goals, address known issues, and ensure the deep context analysis effectively targets token, API, and accessibility gaps for precise remediation.