Skip to content
Back to search

figma-console-mcp-skills

MarketplaceWorks with Claude CodeGitHub

The most powerful Figma Console MCP capabilities, repackaged as Markdown skills for the native Figma MCP server — design tokens, variables, component analysis, WCAG lint, a11y audits, version history, FigJam & Slides.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/southleft--figma-console-mcp-skills/badge.svg)](/listings/southleft--figma-console-mcp-skills)

HTML

<a href="/listings/southleft--figma-console-mcp-skills"><img src="/api/listings/southleft--figma-console-mcp-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

A "skill" is just a folder with a `SKILL.md` file — an open, portable format supported by **Claude Desktop, Claude Code, claude.ai (web), Cursor, OpenAI Codex, and Google Gemini CLI**. Pick the path that matches how you work.

> **Two one-time prerequisites (both free, no token):** > 1. **Connect Figma.** In your AI tool, add the **Figma** connector and sign in — this is a one-time > OAuth login (see ["Do I need a Figma token?"](#do-i-need-a-figma-token-mostly-no) below). > 2. **Have the official `figma-use` skill available.** It ships with the Figma integration and carries > the Figma Plugin API rules these skills build on. These skills extend it.

> **⚡ Fastest path — `npx` (any agent: Claude Code, Codex, Cursor, Gemini CLI, …):** one command, > no manual file copying — > ```bash > npx skills add southleft/figma-console-mcp-skills # install all skills > npx skills add southleft/figma-console-mcp-skills --list # preview without installing > npx skills add southleft/figma-console-mcp-skills --skill figma-export-tokens # just one > ``` > Powered by the [`skills`](https://github.com/vercel-labs/skills) CLI — it detects your agent and > drops each skill into the right place. > > **Claude Code plugin** — alternatively, install the whole collection as a plugin: > ``` > /plugin marketplace add southleft/figma-console-mcp-skills > /plugin install figma-console-mcp-skills@figma-console-mcp-skills > ``` > The per-host options below still work if you prefer copying folders manually.

Option A — Claude Desktop or claude.ai web (no terminal — best for designers)

1. Download this repo: green **Code → Download ZIP**, then unzip it. 2. Zip a single skill folder — open the `skills/` folder, then in Finder/Explorer **right-click the `figma-export-tokens` folder → Compress** (no terminal needed). Its `SKILL.md` must sit at the root of the zip. 3. In Claude, open **Settings → Capabilities → Skills** (Claude Desktop) or **Settings → Skills** (claude.ai), choose **Create / upload a skill**, upload that zip, and toggle it on. Repeat for each skill you want. ([Official guide](https://support.claude.com/en/articles/12512180-use-skills-in-claude) · requires a plan with Skills / code-execution enabled.) 4. In a chat with Figma connected, just ask ("export my Figma variables to CSS") or type `/figma-export-tokens`.

Every skill is **self-contained** — its `SKILL.md` and `scripts/` carry everything, so single-folder zips work with no broken links. *This path can't run the 4 REST skills* (version history, changelog, blame, comments) — they need a terminal (Option B).

Option B — Claude Code (incl. the Code tab inside Claude Desktop), Cursor, etc. (terminal)

git clone https://github.com/southleft/figma-console-mcp-skills.git
cd figma-console-mcp-skills
# Skills are self-contained — copy all of them (or pick individual folders) into your skills folder:
cp -R skills/* ~/.claude/skills/

This is the most capable setup: the `use_figma` skills **and** the shell the 4 REST skills need. Then ask naturally or type `/figma-export-tokens`. (The repo's top-level `references/` holds canonical docs for maintainers — the skills don't depend on it.)

Codex / Gemini CLI / other agents

Same folders — drop them in that tool's skills directory (e.g. `.codex/skills/`, `.gemini/skills/`; check the tool's docs). The `SKILL.md` format is portable across all of them.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 44 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "figma-console-mcp-skills",
  3. "owner": {
  4. "name": "Southleft",
  5. "email": "tpitre@gmail.com"
  6. },
  7. "metadata": {
  8. "description": "Figma Console MCP capabilities as skills for the native Figma MCP server.",
  9. "version": "1.0.0"
  10. },
  11. "plugins": [
  12. {
  13. "name": "figma-console-mcp-skills",
  14. "description": "The full collection: design tokens (export/import/setup), variable and library management, component-set analysis and docs, WCAG and design-system linting, accessibility audits, version history, changelog, blame, comments, annotations, FigJam, and Slides.",
  15. "source": "./",
  16. "strict": false,
  17. "skills": [
  18. "./skills/figjam-create-content",
  19. "./skills/figma-analyze-component-set",
  20. "./skills/figma-annotations",
  21. "./skills/figma-arrange-component-set",
  22. "./skills/figma-audit-accessibility",
  23. "./skills/figma-blame-node",
  24. "./skills/figma-check-design-parity",
  25. "./skills/figma-comments",
  26. "./skills/figma-component-properties",
  27. "./skills/figma-deep-component",
  28. "./skills/figma-design-system-inventory",
  29. "./skills/figma-export-tokens",
  30. "./skills/figma-extract-design-system",
  31. "./skills/figma-generate-changelog",
  32. "./skills/figma-generate-component-doc",
  33. "./skills/figma-import-tokens",
  34. "./skills/figma-library-variables",
  35. "./skills/figma-lint-design",
  36. "./skills/figma-manage-variables",
  37. "./skills/figma-scan-code-accessibility",
  38. "./skills/figma-setup-design-tokens",
  39. "./skills/figma-slides",
  40. "./skills/figma-version-history"
  41. ]
  42. }
  43. ]
  44. }
README.md · README · 233 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Figma Console MCP Skills
  2. **The most powerful [Figma Console MCP](https://github.com/southleft/figma-console-mcp) capabilities,
  3. repackaged as Markdown skills for the _native_ Figma MCP server.**
  4. The official Figma MCP server is powerful and general-purpose: it reads designs
  5. (`get_design_context`, `get_metadata`, `get_variable_defs`, `get_screenshot`, `search_design_system`)
  6. and writes to Figma through `use_figma`, which runs Figma Plugin API JavaScript. That flexibility
  7. means it *can* do a great deal — the harder part is doing each design-systems job well and
  8. repeatably.
  9. This repo packages that know-how. Each directory is a **skill** — a Markdown playbook plus
  10. ready-to-paste scripts, distilled from the
  11. [Figma Console MCP](https://github.com/southleft/figma-console-mcp) — so your agent reliably handles
  12. design-systems work without reinventing the Plugin API each session: token export/import (DTCG, CSS,
  13. Tailwind…), variable management, component-set analysis, WCAG linting, accessibility audits, version
  14. diffing/changelogs, annotations, comments, FigJam, and Slides. Most run through `use_figma`; a few
  15. reach data the Plugin API can't (version history, comments) via the Figma REST API, or analyze code
  16. (axe-core).
  17. > **You do not need to install the Figma Console MCP to use these skills.** You only need the native
  18. > Figma MCP server and (for the four REST skills) a Figma personal access token.
  19. ---
  20. ## How it works
  21. A "skill" is a folder containing a `SKILL.md` with YAML frontmatter (`name`, `description`). When your
  22. request matches a skill's `description`, the agent loads it and follows the playbook. You can also
  23. invoke one explicitly with `/skill-name`.
  24. - **`scripts/*.js`** — ready-to-paste snippets for the native `use_figma` tool (plain JS, top-level
  25. `await`, `return` for output, inlined inputs). The full Plugin API reference is the official
  26. **`figma-use`** skill.
  27. - **`scripts/*.mjs` / `*.sh`** — runnable Node/bash for the REST and code-side skills.
  28. - **A skill's own `references/`** — extra detail bundled *inside* that skill's folder, so it travels
  29. with a single-folder upload. **Every skill is self-contained** — you don't need anything else from
  30. the repo. (The top-level [`references/`](references) is optional background/contributor docs that no
  31. skill depends on.)
  32. **Prerequisite:** Always load the official **`figma-use`** skill alongside any Plugin-API skill here —
  33. it's the source of truth for the Figma Plugin API surface. These skills add design-systems workflows
  34. on top of it.
  35. ---
  36. ## Install
  37. A "skill" is just a folder with a `SKILL.md` file — an open, portable format supported by **Claude
  38. Desktop, Claude Code, claude.ai (web), Cursor, OpenAI Codex, and Google Gemini CLI**. Pick the path
  39. that matches how you work.
  40. > **Two one-time prerequisites (both free, no token):**
  41. > 1. **Connect Figma.** In your AI tool, add the **Figma** connector and sign in — this is a one-time
  42. > OAuth login (see ["Do I need a Figma token?"](#do-i-need-a-figma-token-mostly-no) below).
  43. > 2. **Have the official `figma-use` skill available.** It ships with the Figma integration and carries
  44. > the Figma Plugin API rules these skills build on. These skills extend it.
  45. > **⚡ Fastest path — `npx` (any agent: Claude Code, Codex, Cursor, Gemini CLI, …):** one command,
  46. > no manual file copying —
  47. > ```bash
  48. > npx skills add southleft/figma-console-mcp-skills # install all skills
  49. > npx skills add southleft/figma-console-mcp-skills --list # preview without installing
  50. > npx skills add southleft/figma-console-mcp-skills --skill figma-export-tokens # just one
  51. > ```
  52. > Powered by the [`skills`](https://github.com/vercel-labs/skills) CLI — it detects your agent and
  53. > drops each skill into the right place.
  54. >
  55. > **Claude Code plugin** — alternatively, install the whole collection as a plugin:
  56. > ```
  57. > /plugin marketplace add southleft/figma-console-mcp-skills
  58. > /plugin install figma-console-mcp-skills@figma-console-mcp-skills
  59. > ```
  60. > The per-host options below still work if you prefer copying folders manually.
  61. ### Option A — Claude Desktop or claude.ai web (no terminal — best for designers)
  62. 1. Download this repo: green **Code → Download ZIP**, then unzip it.
  63. 2. Zip a single skill folder — open the `skills/` folder, then in Finder/Explorer **right-click the
  64. `figma-export-tokens` folder → Compress** (no terminal needed). Its `SKILL.md` must sit at the root of the zip.
  65. 3. In Claude, open **Settings → Capabilities → Skills** (Claude Desktop) or **Settings → Skills**
  66. (claude.ai), choose **Create / upload a skill**, upload that zip, and toggle it on. Repeat for each
  67. skill you want. ([Official guide](https://support.claude.com/en/articles/12512180-use-skills-in-claude)
  68. · requires a plan with Skills / code-execution enabled.)
  69. 4. In a chat with Figma connected, just ask ("export my Figma variables to CSS") or type
  70. `/figma-export-tokens`.
  71. Every skill is **self-contained** — its `SKILL.md` and `scripts/` carry everything, so single-folder
  72. zips work with no broken links. *This path can't run the 4 REST skills* (version history, changelog,
  73. blame, comments) — they need a terminal (Option B).
  74. ### Option B — Claude Code (incl. the Code tab inside Claude Desktop), Cursor, etc. (terminal)
  75. ```bash
  76. git clone https://github.com/southleft/figma-console-mcp-skills.git
  77. cd figma-console-mcp-skills
  78. # Skills are self-contained — copy all of them (or pick individual folders) into your skills folder:
  79. cp -R skills/* ~/.claude/skills/
  80. ```
  81. This is the most capable setup: the `use_figma` skills **and** the shell the 4 REST skills need. Then
  82. ask naturally or type `/figma-export-tokens`. (The repo's top-level `references/` holds canonical docs
  83. for maintainers — the skills don't depend on it.)
  84. ### Codex / Gemini CLI / other agents
  85. Same folders — drop them in that tool's skills directory (e.g. `.codex/skills/`, `.gemini/skills/`;
  86. check the tool's docs). The `SKILL.md` format is portable across all of them.
  87. ---
  88. ## Do I need a Figma token? (Mostly no)
  89. **No — for the native Figma MCP and 18 of the 22 skills.** Connecting Figma uses **OAuth**: you sign
  90. in to your Figma account once when you add the connector, and there's no token to manage. Everything
  91. that runs through `use_figma` — tokens, variables, components, lint, accessibility, annotations,
  92. FigJam, Slides, component docs — is authorized automatically. (Figma's MCP doesn't even accept personal
  93. access tokens — OAuth only.)
  94. **Yes — only for the 4 REST skills:** `figma-version-history`, `figma-generate-changelog`,
  95. `figma-blame-node`, `figma-comments`. They're the exception because **version history and comments
  96. aren't part of the native Figma MCP's tools and can't be reached through `use_figma`** (the Figma
  97. Plugin API has no access to them). So these skills call Figma's **REST API** directly — and a skill
  98. can't borrow the MCP's OAuth session — so they need your own **Figma personal access token**, and a
  99. host that can run commands (Option B; they won't run in plain web/desktop chat).
  100. Set it once in your terminal — `export FIGMA_TOKEN="figd_…"` — then run those skills. **The token lives
  101. in your shell environment, never inside a skill or its zip** (skills must not contain secrets); the
  102. scripts read `$FIGMA_TOKEN` at runtime. Full steps (creating the token, scopes) are in
  103. [references/rest-api-setup.md](references/rest-api-setup.md).
  104. ---
  105. ## The 22 skills
  106. ### 🎨 Tokens & Variables — _export, import & manage variables in code-ready formats_
  107. | Skill | What it does |
  108. |---|---|
  109. | [`figma-export-tokens`](figma-export-tokens) | Export Figma variables → DTCG / CSS vars / Tailwind v4–v3 / SCSS / TS / JSON. Resolves aliases + multi-mode. Works on **any plan** (Plugin API, not the Enterprise-only Variables REST API). |
  110. | [`figma-import-tokens`](figma-import-tokens) | Push tokens (DTCG/etc.) **into** Figma as variables, non-destructively (matches by id/key/name). |
  111. | [`figma-setup-design-tokens`](figma-setup-design-tokens) | Bootstrap a whole token system (collection + modes + variables) atomically. |
  112. | [`figma-manage-variables`](figma-manage-variables) | CRUD + fast batch create/update, scopes, code syntax, add/rename modes. |
  113. | [`figma-library-variables`](figma-library-variables) | Discover & import variables from subscribed team libraries. |
  114. ### 🧩 Components & Design System
  115. | Skill | What it does |
  116. |---|---|
  117. | [`figma-analyze-component-set`](figma-analyze-component-set) | Extract a variant **state machine** + CSS pseudo-class mapping + per-variant visual diffs for code gen. |
  118. | [`figma-arrange-component-set`](figma-arrange-component-set) | Organize variants into a labeled grid container. |
  119. | [`figma-component-properties`](figma-component-properties) | Add/edit/delete component properties; instantiate + set instance properties. |
  120. | [`figma-design-system-inventory`](figma-design-system-inventory) | One-call unified extraction: tokens + components + styles + visual specs. |
  121. | [`figma-deep-component`](figma-deep-component) | Unlimited-depth component tree with resolved tokens, mainComponent refs, reactions. |
  122. ### ♿ Quality & Accessibility — _WCAG 2.2 + design-system audits, run right in the file_
  123. | Skill | What it does |
  124. |---|---|
  125. | [`figma-lint-design`](figma-lint-design) | WCAG 2.2 + design-system quality lint over a node tree. |
  126. | [`figma-audit-accessibility`](figma-audit-accessibility) | Per-component a11y scorecard: state coverage, focus, target size, color-blind sim. |
  127. | [`figma-scan-code-accessibility`](figma-scan-code-accessibility) | axe-core + JSDOM scan of generated HTML (code-side Node script). |
  128. | [`figma-check-design-parity`](figma-check-design-parity) | Compare a Figma node vs a code spec; parity score + discrepancies. |
  129. ### 🕓 Versioning & Collaboration — _⌨️ terminal + Figma token required_
  130. | Skill | What it does |
  131. |---|---|
  132. | [`figma-version-history`](figma-version-history) | List versions, snapshot a version, diff two versions. |
  133. | [`figma-generate-changelog`](figma-generate-changelog) | Human-readable markdown changelog between versions. |
  134. | [`figma-blame-node`](figma-blame-node) | Binary-search which version introduced a node/property change (~log₂N requests). |
  135. | [`figma-comments`](figma-comments) | Read / post / reply / delete file comments (with node pinning). |
  136. > ⌨️ **These four run shell commands** — they need a terminal-capable agent (Claude Code, the Code tab
  137. > inside Claude Desktop, Cursor, Codex, Gemini CLI) **plus a `FIGMA_TOKEN`**. They do **not** run in
  138. > plain Claude Desktop or claude.ai chat. Every other skill works anywhere the Figma connector does.
  139. ### 📝 Documentation, Annotations, FigJam & Slides
  140. | Skill | What it does |
  141. |---|---|
  142. | [`figma-generate-component-doc`](figma-generate-component-doc) | Generate complete component documentation markdown (anatomy, tokens, states, a11y, parity). |
  143. | [`figma-annotations`](figma-annotations) | Read & write designer annotations (specs pinned to nodes) + categories. |
  144. | [`figjam-create-content`](figjam-create-content) | Author FigJam: stickies, connectors, shapes, sections, tables, code blocks, auto-arrange. |
  145. | [`figma-slides`](figma-slides) | Author Figma Slides: create/reorder slides, text/shapes, backgrounds, transitions. |
  146. > `figjam-create-content` only works in a **FigJam** file and `figma-slides` only in a **Figma Slides**
  147. > file (the editor-specific node types throw elsewhere). The token, variable, component, lint, and
  148. > a11y skills work in standard Figma **design** files.
  149. ---
  150. ## What we deliberately left out (to avoid conflicts)
  151. These overlap with the native Figma MCP's built-in tools, so there's no skill for them — use the
  152. native tool instead:
  153. - **Design-to-code / inspect a node** → native `get_design_context`
  154. - **Screenshots** → native `get_screenshot`
  155. - **File metadata / structure** → native `get_metadata`
  156. - **Basic variable defs (default mode)** → native `get_variable_defs` _(our token skills go further:
  157. alias resolution + every mode)_
  158. - **Component search** → native `search_design_system`
  159. - **Code Connect** → native Code Connect suite
  160. - **Create a new file / diagram** → native `create_new_file` / `generate_diagram`
  161. - **Low-level node create/move/resize/fills/text** → already taught by the official `figma-use` skill
  162. ---
  163. ## FAQ
  164. **Do I need the Figma Console MCP installed?** No. These skills run on the native Figma MCP. They're
  165. distilled from the Console MCP's implementation so you get the capabilities without the extra server.
  166. **Why is `use_figma` enough for tokens/variables/components?** Because `use_figma` executes the Figma
  167. Plugin API in the file context — the same API the Console MCP's Desktop Bridge uses. The scripts here
  168. are that logic, rewritten for the `use_figma` idiom.
  169. **Why do four skills need a token?** Version history and comments live only in Figma's REST API, which
  170. the Plugin API (and therefore `use_figma`) can't reach. See
  171. [`references/rest-api-setup.md`](references/rest-api-setup.md).
  172. **My script errored on the first `use_figma` call.** Failed scripts are atomic — nothing was applied.
  173. Read the error, fix, retry. See [`references/use-figma-conventions.md`](references/use-figma-conventions.md).
  174. ---
  175. ## Contributing
  176. PRs welcome — new skills, better ports, more output formats. Keep each skill self-contained, mirror
  177. the existing `SKILL.md` structure (frontmatter + "Skill boundaries" + workflow), and make scripts
  178. follow the `use_figma` conventions. Run a quick syntax check (`node --check` wrapped in an async
  179. function for `use_figma` scripts; `bash -n` for shell) before opening a PR.
  180. ## Credits & license
  181. Distilled from the [Figma Console MCP](https://github.com/southleft/figma-console-mcp) by
  182. [Southleft](https://southleft.com). MIT licensed — see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.