OpenParable
Skip to content
← Back to skills

Figma Component Audit

Design
figma-component-audit

Figma Component Audit is an Agent Skill for design published in the mohitagw15856/pm-claude-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Audit a Figma component library for consistency, coverage gaps, and naming issues. Use when asked to audit components, review a design system, check component consistency, identify missing components, or assess Figma library health. Produces a structured audit report with issues prioritised by impact, naming recommendations, and a fix plan.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/mohitagw15856/pm-claude-skills/blob/HEAD/plugins/pm-figma/skills/figma-component-audit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/figma-component-audit, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Figma Component Audit Skill

Produces a structured audit of a Figma component library — identifying inconsistencies, naming problems, coverage gaps, and prioritised recommendations.

Required Inputs

  • Component list or description (paste component names or describe what exists)
  • Product type (mobile app / web app / desktop / multi-platform)
  • Design system maturity (new / growing / mature / legacy)
  • Primary concern (optional)

Output Structure

1. Audit Summary

DimensionStatusScore
Naming consistencyRed/Amber/Green/10
Component coverage/10
Variant completeness/10
Documentation/10
Overall health/10

Verdict: What is the state of this library and the single most important thing to fix?

2. Naming Issues

For each problem: Issue: [Problem type]

  • What is happening: [Specific examples]
  • Why it matters: [Impact on designers and developers]
  • Fix: [Exact naming convention to adopt]
  • Examples: Before / After

Naming convention to enforce:

  • Components: PascalCase (NavigationBar)
  • Variants: Lowercase with slashes (size/large, state/hover)
  • Pages: All caps (COMPONENTS, FOUNDATIONS)

3. Coverage Gaps

Missing ComponentPriorityWhy Needed
[Component]High/Medium/Low[Use case]

4. Variant Completeness Check

ComponentDefaultHoverActiveDisabledErrorMissing
[Button]YesYesNoYesNoActive, Error

5. Prioritised Fix Plan

#FixEffortImpactDo First?
1[Fix]Low/Med/HighHighYes

Quality Checks

  • Naming recommendations have before/after examples
  • Coverage gaps are relevant to the product type
  • Fix plan is ordered by impact-to-effort ratio
  • Variant completeness covers all interactive states

Anti-Patterns

  • Do not flag naming issues without providing a specific, consistent naming convention to adopt
  • Do not audit only visual consistency — also check for missing interactive states and accessibility compliance
  • Do not list all issues at equal priority — group by impact (Critical / Major / Minor) so the fix plan is actionable
  • Do not omit variant completeness — every interactive component must cover all required states
  • Do not leave coverage gaps without recommending specific missing components to add

Example Trigger Phrases

  • "Audit my Figma component library"
  • "Review our design system for consistency issues"
  • "What components are we missing in our Figma library?"
  • "Our component naming is a mess — help me fix it"
  • "Do a health check on our Figma components"