figma-component-audit

Audit Figma component libraries for naming, coverage, and variant gaps.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/spontus-reach/spontus --skill figma-component-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-component-audit
Source: https://github.com/spontus-reach/spontus/tree/main/.agents/skills/figma-component-audit
Command: npx skills add https://github.com/spontus-reach/spontus --skill figma-component-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quickly identify inconsistencies, naming problems, missing components, and incomplete variants in a Figma component library so designers and developers can align on a healthier design system.

Core Features & Use Cases

  • Component library health audit: Produces an overall verdict using naming consistency, coverage, variant completeness, and documentation signals.
  • Actionable naming recommendations: Flags naming issues and provides clear before/after convention guidance for components, variants, and pages.
  • Coverage and variant gap detection: Highlights missing components and variant states per component to ensure interactive completeness.
  • Prioritised fix plan: Outputs a prioritized table that balances effort and impact, helping teams decide what to fix first.

Quick Start

Ask the skill to audit your Figma component library and return a structured report with prioritized fixes.

Frequently Asked Questions about figma-component-audit

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

FAQPage Schema
How do I audit a Figma component library for inconsistencies and missing variants?

To audit a Figma component library, the skill evaluates naming conventions, coverage gaps, and variant completeness across interactive states. It outputs a structured report with impact-prioritized findings and explicit before/after naming recommendations to guide remediation.

What is component variant completeness and why does it matter for design systems?

Component variant completeness ensures a Figma component covers all required interactive states. The skill checks for missing variant states per component and highlights coverage gaps to ensure interactive completeness and align designers with developers.

How do I fix naming convention issues in a Figma design system?

To fix naming convention issues in a Figma design system, the skill flags inconsistent component and variant names. It provides clear before and after convention guidance for components, variants, and pages to standardize your library.

Can I get a prioritized fix plan for design system coverage gaps?

Yes, you can get a prioritized fix plan for design system coverage gaps. The skill outputs a prioritized table that balances effort and impact, helping teams decide exactly which missing components and incomplete variants to fix first.

Does this component library health check require any specific Figma plugins?

No specific Figma plugins are required. The skill operates as an intermediate-level audit tool that analyzes your component library metadata to produce an overall health verdict based on naming, coverage, and documentation signals.