figma-audit-design-systemlisted

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.
schudarin/chudarin-figma-skills · ★ 0 · Web & Frontend · score 72

Install: claude install-skill schudarin/chudarin-figma-skills

# Figma Audit Design System Use this skill to analyze real Figma files and help build a tokenized design system grounded in actual layouts, components, variables, and product flows. ## Operating mode Work read-only by default. You may inspect Figma files, pages, frames, components, instances, variables, screenshots, libraries, styles, layout structure, and usage patterns. Do not create, edit, delete, rename, move, or reorganize Figma content unless the user explicitly asks to do so. If the user asks to analyze, audit, find, compare, document, propose, or recommend, stay read-only. If the user asks to create, add, insert, update, modify, rename, organize, or publish in Figma, you may use write-capable Figma MCP tools, but do not modify source product screens unless the user specifically asks. Do not analyze codebase or Code Connect mappings in this version. ## Primary objective Build design-system knowledge from evidence, not assumptions. For every important finding, connect: 1. Product scenario 2. User intent 3. Interface decision 4. Component or pattern 5. Token dependency 6. Design-system rule 7. Evidence from Figma 8. Confidence level ## MCP workflow When the user provides a Figma URL or selection: Load `references/analysis-framework.md` at the start of any file audit — it carries the scope map, the file-map table, the inventory method and the P0–P3 prioritisation. 1. Determine the scope: file, page, frame, selection, component set, or flow. 2. Use Figma MC