penpot-audit-tokens

To audit Penpot designs for hardcoded colors and off-grid spacing, use an automated governance audit tool that scans your files and generates a severity report with suggested semantic-token swaps for unresolved or unused tokens.

Design system governance in Penpot ensures consistency by managing tokens. An audit mechanism scans designs to identify duplicated values and orphan tokens, producing a severity report with suggested fixes.

Yes, you need the Penpot MCP to run a design token audit. The process also requires access to your design system tokens and schemas to identify unresolved references and suggest semantic swaps.

To fix orphan and unresolved tokens in Penpot, run an automated audit that detects these governance issues. The audit generates a severity report with suggested semantic-token swaps to resolve duplicates.

The best way to generate a severity report for Penpot design system issues is to automate the audit process. This identifies hardcoded colors and spacing issues, providing suggested token swaps directly in the output report.