figmalint-design-system-auditing

Audit Figma components for design-system compliance, accessibility, and token usage.

3|Updated May 16, 2026
One-click install
npx skills add https://github.com/Aradotso/design-skills --skill figmalint-design-system-auditing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figmalint-design-system-auditing
Source: https://github.com/Aradotso/design-skills/tree/main/skills/figmalint-design-system-auditing
Command: npx skills add https://github.com/Aradotso/design-skills --skill figmalint-design-system-auditing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Figma components often drift from design-system rules, leading to accessibility gaps, inconsistent token usage, and developer handoff problems that slow shipping.

Core Features & Use Cases

  • Design system compliance auditing: checks component consistency, layer naming, and developer handoff readiness.
  • Accessibility auditing (WCAG-oriented): evaluates contrast, touch target sizes, focus indicators, and font sizing.
  • Token detection and auto-fix support: finds hard-coded values, detects design-token adoption gaps, and guides binding fixes.
  • Documentation and exports: generates structured component documentation and exports analysis for developers or AI-assisted generation.

Quick Start

Ask the skill to audit your Figma component for design system compliance and accessibility issues, including token hard-coding and missing interactive states.

Frequently Asked Questions about figmalint-design-system-auditing

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

FAQPage Schema
How do I audit Figma components for design system compliance and accessibility?

Auditing Figma components involves analyzing tokens versus hard-coded values, checking layer naming, evaluating interactive state coverage, and running WCAG-oriented accessibility checks for contrast and touch targets.

How do I find hard-coded values in Figma components and check design token adoption?

Finding hard-coded values requires detecting design-token adoption gaps by analyzing component layers, identifying raw values instead of bound tokens, and generating guidance for binding fixes.

Can I check Figma component accessibility for WCAG contrast and touch target sizes?

Yes, accessibility auditing evaluates Figma components for WCAG-oriented criteria including color contrast ratios, touch target sizes, focus indicators, and font sizing to identify compliance gaps.

What is the best way to document Figma components for developer handoff?

Documenting Figma components for developer handoff involves generating structured component documentation that exports analysis reports covering token usage, state coverage, and readiness gaps.

Does Figma component auditing check missing interactive states and layer naming?

Yes, component auditing checks for missing interactive states and evaluates layer naming conventions to identify design-system noncompliance and developer handoff gaps across component sets.

Can I export Figma component audit reports for developers and AI-assisted generation?

Yes, component audit reports can be exported as structured documentation across supported formats, providing analysis outputs suitable for developer handoff or AI-assisted code generation.