design-system

To audit a design system, scan component libraries and token inventories to identify naming inconsistencies, hardcoded values, and coverage gaps. This process surfaces UI drift issues and produces a structured audit report with a prioritized remediation plan.

Documenting design system components involves generating structured templates that include variants, states, props, accessibility notes, and code examples. This standardizes component definitions and creates shareable documentation for design and development teams.

Proposing new patterns requires defining the component API, variants, token usage, and accessibility considerations. This generates extendable component proposals with token mappings and open questions for design review.

Yes, you can scan component families like buttons and inputs to identify hardcoded colors and convert them to token references. This standardizes token usage across the design system and reduces visual inconsistencies.

Yes, the design system audit identifies accessibility gaps across pattern libraries and component families. It generates accessibility notes within structured documentation templates to ensure compliance and comprehensive coverage.

You need an existing component library, token inventory, or pattern library to run a full design system audit. The audit scans these inputs to detect missing documentation, hardcoded values, and naming inconsistencies, outputting a prioritized findings report.