figma-variable-audit
FeaturedAudit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- murphytrueman
- Repository
- murphytrueman/design-system-ops
- Created
- 6 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
figma-audit-design-system
Analyze, audit, inventory, and document an existing Figma design system through the Figma MCP server — components, variables, tokens, patterns, design debt, usage rules, causal relationships — and create design-system documentation pages in Figma on request. Use when the user asks to audit, inventory, map, document, or find debt in a Figma file, page, frame, component set, or selection. Read-only by default; modify Figma only when the user explicitly asks. Not for designing or building screens — that is figma-design-screens; not for repairing broken variable bindings — that is figma-fix-variable-bindings.
naming-audit
Audit naming consistency and clarity across component, token and pattern names, with rename suggestions. Triggers: naming review, are my names consistent, fix our naming. For token tier structure use token-audit; for Figma variable names use figma-variable-audit.