audit-design-system

Detect design-system drift in Figma nodes and report token binding issues.

Updated Mar 25, 2026

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

Ready to run

npx skills add https://github.com/PytaichukBohdan/figma_board_connection --skill audit-design-system-pytaichukbohdan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-design-system
Source: https://github.com/PytaichukBohdan/figma_board_connection/tree/main/.claude/skills/audit-design-system
Command: npx skills add https://github.com/PytaichukBohdan/figma_board_connection --skill audit-design-system-pytaichukbohdan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and reports design-system drift in a Figma node or screen, including missing shared components, local overrides, and unbound tokens.

Core Features & Use Cases

Drift detection: identifies where a node deviates from approved primitives, tokens, and component usage.
Evidence-based findings: anchors each issue to concrete Figma structure such as instances, raw values, or token bindings.
Replacement guidance: suggests credible design-system replacements when possible via a search across the audited library.
Use Case: Review a screen to ensure all interactive controls are instantiated from design-system primitives rather than custom frames.

Quick Start

Review a Figma node to identify and report design-system drift and token binding issues.

Frequently Asked Questions about audit-design-system

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

FAQPage Schema

How do I detect design-system drift in a Figma node?▼

You audit Figma nodes for design-system drift by rigorously evaluating structural evidence like instances, token bindings, and raw values to identify missing primitives, local overrides, and unbound tokens. This process anchors each issue to concrete Figma structure.

What are unbound tokens and missing primitives in a Figma design system?▼

Unbound tokens and missing primitives in a Figma design system occur when nodes deviate from approved components and use raw values instead of shared token bindings. They represent local overrides that drift away from the established design-system structure.

Can I get replacement suggestions for local overrides found in a Figma screen?▼

Yes, you can get replacement suggestions for local overrides found in a Figma screen. When a credible match exists, the audit proposes a replacement via a search across the audited design-system library to ensure components are instantiated from approved primitives.

How do I review a Figma screen for token binding issues and custom frames?▼

To review a Figma screen for token binding issues and custom frames, you evaluate the structural evidence of the screen to detect missing shared components and local overrides. This ensures interactive controls are instantiated from design-system primitives rather than custom frames.

Does the Figma design-system audit report raw values and instance overrides?▼

Yes, the Figma design-system audit reports raw values and instance overrides. It rigorously evaluates structural evidence to anchor each finding of design-system drift, such as missing primitives and unbound tokens, to concrete Figma structure.

What is the best way to ensure Figma components are instantiated from approved primitives?▼

The best way to ensure Figma components are instantiated from approved primitives is to audit nodes and screens for design-system drift. This identifies missing shared components and local overrides, proposing credible replacements via a search across the design-system library.