audit-design-system

Name: audit-design-system
Availability: InStock
Author: artosetrov

Audit Figma nodes for missing shared components, local overrides, and unbound tokens.

Updated Mar 5, 2026

Search Tags:#components #audit #figma #tokens #drift #design-system #design-review

Ready to run

npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill audit-design-system-artosetrov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-design-system
Source: https://github.com/artosetrov/iron-fist-arena-backend/tree/main/.claude/skills/audit-design-system
Command: npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill audit-design-system-artosetrov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit a Figma screen or component for design-system integration drift, including missing shared components, local overrides, and unbound tokens.

Core Features & Use Cases

Review a Figma node for evidence that the design is not properly integrated with the design system.
Provide guidance on how to resolve drift by aligning to shared primitives and tokens.
When credible, suggest replacement components sourced from the audited design system.

Quick Start

Use the audit-design-system on this Figma link to audit design-system integration drift and, when credible, suggest replacement components that can route to $fix-design-system-finding or $apply-design-system.

Frequently Asked Questions about audit-design-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit a Figma screen for design-system drift?▼

To audit Figma screens for design-system drift, you analyze nodes for missing shared components, local overrides, and unbound tokens. This review surfaces areas where the design is not properly integrated with the shared library.

What is design-system drift in Figma components?▼

Design-system drift in Figma occurs when screens use missing shared components, apply local overrides, or contain unbound tokens. Identifying this drift helps maintain conformity by realigning elements to shared primitives and tokens.

How do I fix unbound tokens and local overrides in Figma?▼

To fix unbound tokens and local overrides in Figma, the audit suggests replacement components sourced from your design system. This provides guidance on resolving drift by aligning elements back to shared primitives.

Can I audit an entire Figma board for missing shared components?▼

Yes, you can apply the audit to individual screens, components, or entire Figma boards. It evaluates instances, tokens, and variants for conformity to surface missing shared components across the selected node data.

Does the Figma design review require access to token bindings?▼

Yes, evaluating design-system integration requires access to Figma node data and token bindings. This access is necessary to properly evaluate instances, tokens, and variants for conformity and detect drift scenarios.