Run an audit before any major system change, whether you are aligning a pattern, creating new tokens, or preparing to pitch a system. Audits reveal what really exists today, surfacing strengths, inconsistencies, duplication, and gaps. They create a shared foundation that guides alignment, setup, and design decisions.
Audit
How to
-
Set your scope
Decide what you are auditing, such as a single pattern, tokens, accessibility, or something broader.
-
Collect real examples
Gather design files, live product screenshots, or code snippets across platforms. If you have metrics on usage across different platforms pair these with your examples.
- Use vision tools to automatically sort and categorise screenshots by pattern type
-
Sort and group
Organise examples in a way that fits your audit focus. This could mean grouping by platform for consistency checks, by token type for naming reviews, or by categories like colour, spacing, or patterns to spot gaps and overlaps.
- Run sorted groups through AI to spot naming inconsistencies or overlaps you might have missed
-
Extract insights
Capture issues, gaps, and duplication, as well as what is already working well.
-
Define requirements
Translate findings into actions, such as naming standards, missing tokens, component clean up, or documentation updates.
Speed up audits: Scan Figma files for component usage patterns and generate initial reports. Always check findings against what you know to be true.