Agent skill · Security

figma-component-audit

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.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill figma-component-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/figma-component-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the 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) ##

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Structure
  3. 1. Audit Summary
  4. 2. Naming Issues
  5. 3. Coverage Gaps
  6. 4. Variant Completeness Check
  7. 5. Prioritised Fix Plan
  8. Quality Checks
  9. Anti-Patterns
  10. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the figma-component-audit skill do?

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.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill figma-component-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going