Receber por email
← Voltar para o catálogo

figma-component-audit

Audita uma biblioteca de componentes Figma para consistência, lacunas de cobertura e problemas de nomenclatura, produzindo um relatório estruturado com problemas priorizados por impacto, recomendações de nomenclatura e um plano de correção.

991estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add mohitagw15856/pm-claude-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/figma-component-audit-mohitagw15856/svg)](https://www.skillteca.com.br/skills/figma-component-audit-mohitagw15856)
#ai

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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

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"
Compartilhar X LinkedIn