SkillsAdd

mohitagw15856/pm-claude-skills

figma-component-audit

Audit a Figma component library for consistency, coverage gaps, and naming issues.

First seen Apr 10, 2026

Installation

$ npx skills add mohitagw15856/pm-claude-skills --skill figma-component-audit
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from mohitagw15856/pm-claude-skills · top by installs.

npx skills add mohitagw15856/pm-claude-skills
teaching-lesson-plan 150 team-offsite-planner 98 sop-writer 72 patient-communication 67 user-research-synthesis 66 financial-due-diligence 65 competitive-analysis 65 prd-template 64 meeting-notes 62 project-status-report 62

Browse all from mohitagw15856/pm-claude-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.3K
License LICENSE
Default branch main
Open issues 7
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,126 B
  • docs SUMMARY.md 371 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 49 installs

SKILL.md

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

Dimension Status Score
Naming consistency Red/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 Component Priority Why Needed
[Component] High/Medium/Low [Use case]

4. Variant Completeness Check

Component Default Hover Active Disabled Error Missing
[Button] Yes Yes No Yes No Active, Error

5. Prioritised Fix Plan

# Fix Effort Impact Do First?
1 [Fix] Low/Med/High High Yes

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"