@skilly-hand/skilly-hand 0.29.1 → 0.29.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -16,6 +16,21 @@ All notable changes to this project are documented in this file.
16
16
  ### Removed
17
17
  - _None._
18
18
 
19
+ ## [0.29.2] - 2026-06-20
20
+ [View on npm](https://www.npmjs.com/package/@skilly-hand/skilly-hand/v/0.29.2)
21
+
22
+ ### Added
23
+ - _None._
24
+
25
+ ### Changed
26
+ - Synchronized `figma-mcp-0to1` with the current official Figma MCP tools, Figma Slides workflows, asset transfer, Code Connect context, supported clients, permissions, and rate limits.
27
+
28
+ ### Fixed
29
+ - _None._
30
+
31
+ ### Removed
32
+ - _None._
33
+
19
34
  ## [0.29.1] - 2026-05-23
20
35
  [View on npm](https://www.npmjs.com/package/@skilly-hand/skilly-hand/v/0.29.1)
21
36
 
@@ -3,10 +3,10 @@ name: "figma-mcp-0to1"
3
3
  description: "Guide users from Figma MCP installation and authentication through first canvas creation, with function-level tool coverage and operational recovery patterns."
4
4
  skillMetadata:
5
5
  author: "skilly-hand"
6
- last-edit: "2026-05-09"
6
+ last-edit: "2026-06-20"
7
7
  license: "Apache-2.0"
8
- version: "1.0.3"
9
- changelog: "Updated Figma MCP guidance for current remote-first docs, supported-client coverage, Figma-provided skills, FigJam write workflows, code-to-canvas support, and access/rate-limit language; affects setup routing, tool selection, prompt assets, and official matrix"
8
+ version: "1.1.0"
9
+ changelog: "Synced the official Figma MCP surface for asset transfer, Code Connect context, library discovery, Figma Slides, current Figma-provided skills, and per-minute limits; affects tool routing, canvas workflows, prompts, troubleshooting, and the official matrix"
10
10
  auto-invoke: "Installing, configuring, or using Figma MCP from setup through first canvas creation"
11
11
  allowed-tools:
12
12
  - "Read"
@@ -73,7 +73,8 @@ Choose subskills by intent:
73
73
  - Use link-based node targeting for reliable design-context extraction.
74
74
  - Keep a clear distinction between read context tools and write/canvas tools.
75
75
  - For repeated team workflows, reuse prompts and config snippets from `assets/`, and prefer Figma-provided skills when they exist.
76
- - Use `figma-use` with `use_figma` for Figma Design writes and `figma-use-figjam` for FigJam writes when those skills are available.
76
+ - Pair `use_figma` with the editor-specific skill: `figma-use` for Design, `figma-use-figjam` for FigJam, or `figma-use-slides` for Slides.
77
+ - Use `download_assets` and `upload_assets` when the task requires asset delivery, non-PNG exports, original images, or cross-file image transfer.
77
78
 
78
79
  ---
79
80
 
@@ -83,9 +84,9 @@ Figma MCP support and skilly-hand installation support are related but not ident
83
84
 
84
85
  | Coverage | Agents or Clients | Guidance |
85
86
  | --- | --- | --- |
86
- | Figma-supported and skilly-hand-supported | `codex`, `claude`, `cursor`, `copilot`, `gemini` | Include concrete setup paths when Figma publishes them; otherwise point to client docs/catalog. |
87
- | Figma-supported but not skilly-hand-native | Amazon Q, Android Studio, VS Code, Warp, Augment, Factory, Firebender, Kiro, OpenHands, Replit | Mention as Figma-supported clients, but do not add skilly-hand install assumptions. |
88
- | skilly-hand-supported but not source-backed in current Figma docs | `antigravity`, `windsurf`, `trae` | Keep broad `agentSupport`; document that Figma-specific setup may require client documentation or manual MCP config. |
87
+ | Figma-documented and skilly-hand-supported | `codex`, `claude`, `cursor`, `copilot` | Use concrete setup paths where published; Copilot support is currently documented for Copilot CLI write-to-canvas. |
88
+ | Figma-documented but not skilly-hand-native | VS Code, Xcode, Claude Desktop, Warp, Augment, Factory, Firebender | Mention only for the workflows where Figma lists them; do not add skilly-hand install assumptions. |
89
+ | skilly-hand-supported but not source-backed in current Figma docs | `gemini`, `antigravity`, `windsurf`, `trae` | Keep broad `agentSupport`; require verification in the Figma MCP Catalog or client documentation before setup. |
89
90
 
90
91
  ## Figma-Provided Skills
91
92
 
@@ -95,10 +96,11 @@ Prefer Figma-provided skills for workflows they cover:
95
96
  | --- | --- |
96
97
  | `figma-use` | Foundational Figma Design write-to-canvas workflow for frames, components, variables, styles, and auto layout. |
97
98
  | `figma-use-figjam` | Foundational FigJam write workflow for boards, stickies, sections, connectors, shapes, tables, and code blocks. |
98
- | `figma-create-new-file` | Create blank Figma Design or FigJam files before writing. |
99
- | `figma-implement-design` | Generate production code from a Figma design URL. |
100
- | `figma-code-connect-components` | Map published Figma components to code implementations. |
101
- | `figma-create-design-system-rules` | Generate reusable code-generation rules for a project. |
99
+ | `figma-use-slides` | Foundational Slides write workflow for decks, sections, themes, and speaker notes. |
100
+ | `figma-swiftui` | Translate between Figma designs and SwiftUI in both directions. |
101
+ | `figma-code-connect` | Map published Figma components to code implementations. |
102
+ | `figma-create-new-file` | Create blank Design, FigJam, or Slides files before writing. |
103
+ | `figma-generate-diagram` | Create editable FigJam diagrams from descriptions or source material. |
102
104
  | `figma-generate-library` | Example workflow for creating or syncing a Figma design-system library from code. |
103
105
  | `figma-generate-design` | Example workflow for building screens/views in Figma from code or a design-system-aware brief. |
104
106
 
@@ -133,9 +135,6 @@ claude mcp add --transport http figma-desktop http://127.0.0.1:3845/mcp
133
135
  # Cursor plugin setup
134
136
  /add-plugin figma
135
137
 
136
- # Gemini CLI
137
- # Follow the Figma MCP catalog/client instructions for the Gemini CLI extension.
138
-
139
138
  # Verify catalog integrity in this repository
140
139
  npm run catalog:check
141
140
  ```
@@ -7,7 +7,7 @@ Deliver a first successful Figma canvas result with low risk and clear verificat
7
7
  ## Safe 0-to-1 Workflow
8
8
 
9
9
  1. **Create or choose file context**
10
- - New file path: run `whoami` if needed to obtain a plan/team context, then call `create_new_file`.
10
+ - New file path: run `whoami` if needed to confirm identity, then call `create_new_file` for Design, FigJam, or Slides; choose a team or organization if prompted.
11
11
  - Existing file path: confirm URL/node target and permissions.
12
12
  - Live web UI path: use `generate_figma_design` to capture to a new file, existing file, or clipboard.
13
13
  - Make path: use MCP resources from a Figma Make link to fetch project/file context before implementation.
@@ -17,7 +17,7 @@ Deliver a first successful Figma canvas result with low risk and clear verificat
17
17
  - If access mismatch appears, stop and fix permissions first.
18
18
 
19
19
  3. **Read before write**
20
- - Use `get_libraries` if the Codex Figma plugin exposes it and library scope matters.
20
+ - Use `get_libraries` when library scope matters.
21
21
  - Call `search_design_system` to reuse components/variables.
22
22
  - Optionally call `get_metadata` for structure baseline.
23
23
 
@@ -28,6 +28,7 @@ Deliver a first successful Figma canvas result with low risk and clear verificat
28
28
  - Apply one style/token decision.
29
29
  - For Figma Design, load or invoke `figma-use` when available.
30
30
  - For FigJam, load or invoke `figma-use-figjam` when available, then create or update one small board object such as a sticky, section, connector, shape, table, or code block.
31
+ - For Slides, load or invoke `figma-use-slides` when available, then create or update one slide, section, theme decision, or speaker-note block.
31
32
 
32
33
  5. **Validate state**
33
34
  - Inspect with `get_metadata` or `get_screenshot`.
@@ -51,6 +52,18 @@ Deliver a first successful Figma canvas result with low risk and clear verificat
51
52
  2. Use `figma-use-figjam` with `use_figma` for small write steps.
52
53
  3. Validate with `get_figjam` or `get_screenshot`.
53
54
 
55
+ ### Slides deck-first flow
56
+
57
+ 1. Create or choose a Slides file, using `create_new_file` with the Slides editor type for a fresh deck.
58
+ 2. Use `figma-use-slides` with `use_figma` for small write steps.
59
+ 3. Validate the deck or selected slide with `get_screenshot`.
60
+
61
+ ### Asset-transfer flow
62
+
63
+ 1. Use `download_assets` with the smallest relevant node set; choose raw mode for original source images.
64
+ 2. Fetch the returned temporary URLs before they expire.
65
+ 3. Deliver the files, or pass them to `upload_assets` to transfer images into another Figma file.
66
+
54
67
  ### Code-to-canvas flow
55
68
 
56
69
  1. Ask client to start local app capture workflow.
@@ -8,7 +8,7 @@ Get Figma MCP connected and authenticated, with a verified first tool call.
8
8
 
9
9
  | Mode | Endpoint | Recommended | Notes |
10
10
  | --- | --- | --- | --- |
11
- | Remote | `https://mcp.figma.com/mcp` | Yes | Broadest feature coverage, including write-to-canvas, code-to-canvas, FigJam workflows, diagrams, and file creation. Remote access is documented for all seats/plans, with plan/seat-based limits. |
11
+ | Remote | `https://mcp.figma.com/mcp` | Yes | Broadest feature coverage, including Design, FigJam, Slides, asset transfer, write-to-canvas, code-to-canvas, diagrams, and file creation. Remote access is documented for all seats/plans, with plan/seat-based limits. |
12
12
  | Desktop | `http://127.0.0.1:3845/mcp` | Only for local selection-based or special org/enterprise needs | Requires Figma desktop app + Dev Mode desktop MCP toggle; narrower workflow coverage and paid Dev/Full seat access. |
13
13
 
14
14
  ## Codex Setup
@@ -36,9 +36,9 @@ Use concrete setup paths for agents that are both Figma-supported and skilly-han
36
36
  - Claude Code manual desktop: `claude mcp add --transport http figma-desktop http://127.0.0.1:3845/mcp`
37
37
  - Cursor plugin: `/add-plugin figma`
38
38
  - Cursor manual: add the remote or desktop endpoint in MCP settings.
39
- - Copilot: use the VS Code MCP route and enable GitHub Copilot in the client.
40
- - Gemini CLI: follow the Figma MCP catalog/client instructions for the Gemini CLI extension.
39
+ - Copilot CLI: follow its current Figma MCP Catalog setup path and verify the requested feature is exposed.
41
40
  - VS Code: add HTTP MCP server in `mcp.json` using the remote endpoint.
41
+ - Xcode: use Figma's one-click setup; current docs require Xcode 27 beta.
42
42
 
43
43
  See exact snippets in [../assets/client-config-snippets.md](../assets/client-config-snippets.md).
44
44
 
@@ -46,9 +46,9 @@ See exact snippets in [../assets/client-config-snippets.md](../assets/client-con
46
46
 
47
47
  | Coverage | Agents or Clients | Guidance |
48
48
  | --- | --- | --- |
49
- | Figma-supported and skilly-hand-supported | `codex`, `claude`, `cursor`, `copilot`, `gemini` | Use the commands and setup paths above where documented; otherwise follow the Figma MCP catalog/client docs. |
50
- | Figma-supported but not skilly-hand-native | Amazon Q, Android Studio, VS Code, Warp, Augment, Factory, Firebender, Kiro, OpenHands, Replit | Follow Figma/client setup docs; do not assume skilly-hand skill install paths. |
51
- | skilly-hand-supported but not source-backed in current Figma docs | `antigravity`, `windsurf`, `trae` | Keep install support, but verify Figma MCP setup through that client's docs or manual MCP config. |
49
+ | Figma-documented and skilly-hand-supported | `codex`, `claude`, `cursor`, `copilot` | Use documented setup paths; verify that the requested feature is supported by the active client. |
50
+ | Figma-documented but not skilly-hand-native | VS Code, Xcode, Claude Desktop, Warp, Augment, Factory, Firebender | Follow Figma/client setup docs; do not assume skilly-hand skill install paths. |
51
+ | skilly-hand-supported but not source-backed in current Figma docs | `gemini`, `antigravity`, `windsurf`, `trae` | Verify inclusion in the Figma MCP Catalog or current client docs before setup. |
52
52
 
53
53
  ## Verification Checklist
54
54
 
@@ -57,8 +57,8 @@ See exact snippets in [../assets/client-config-snippets.md](../assets/client-con
57
57
  - Remote: `whoami` (recommended)
58
58
  - Desktop-only contexts: `get_metadata` or `get_design_context` on a known node
59
59
  3. Confirm the authenticated user has access to the target Figma file.
60
- 4. For write workflows, confirm the authenticated seat can edit the target file.
61
- 5. For Dev seats, confirm the target is a draft or that the workflow does not require edit access outside drafts.
60
+ 4. For `use_figma` write workflows, confirm the authenticated user has a Full seat and edit access to the target file.
61
+ 5. For code-to-canvas, any seat can create or edit files in drafts; editing an existing file outside drafts requires a Full seat and edit permission.
62
62
 
63
63
  ## First Prompt After Setup
64
64
 
@@ -7,7 +7,7 @@ Pick the smallest correct Figma MCP function for the task, with predictable inpu
7
7
  ## Start Here
8
8
 
9
9
  1. Read [../references/official-tools-matrix.md](../references/official-tools-matrix.md).
10
- 2. Identify whether task is read, write, FigJam, design-system search, code-connect, diagram, live UI capture, or Make resource context.
10
+ 2. Identify whether task is read, write, asset transfer, Slides, FigJam, design-system search, Code Connect, diagram, live UI capture, or Make resource context.
11
11
  3. Prefer read-first calls before write calls on unknown files.
12
12
 
13
13
  ## Selection Rules
@@ -17,27 +17,33 @@ Pick the smallest correct Figma MCP function for the task, with predictable inpu
17
17
  - Output too large or structure-first pass: `get_metadata` first, then targeted `get_design_context`.
18
18
  - Need variables/tokens only: `get_variable_defs`.
19
19
  - Need visual reference: `get_screenshot`.
20
+ - Need deliverable exports, original images, or multi-node/non-PNG output: `download_assets`.
21
+ - Need to place image assets in a Figma file or transfer images across files: `upload_assets` (use with `download_assets` for cross-file transfer).
20
22
  - Need FigJam extraction: `get_figjam`.
21
23
  - Need FigJam creation/editing: `use_figma` with the `figma-use-figjam` skill when available.
22
- - Need library discovery in Codex before a scoped search: `get_libraries` if the Codex Figma plugin exposes it.
24
+ - Need library discovery before a scoped search: `get_libraries`.
23
25
  - Need design-system discovery before creating: `search_design_system`.
24
26
  - Need to write/create/update Figma Design content: `use_figma` (remote write workflow; use `figma-use` skill when available).
25
27
  - Need to write/create/update FigJam content: `use_figma` (remote write workflow; use `figma-use-figjam` skill when available).
28
+ - Need to write/create/update Slides content: `use_figma` (remote write workflow; use `figma-use-slides` skill when available).
26
29
  - Need first-time live web UI capture: `generate_figma_design`.
27
- - Need new blank file: `create_new_file` (requires plan/team context such as `planKey` in some clients).
30
+ - Need new blank Design, FigJam, or Slides file: `create_new_file` (the user may need to choose a team or organization).
28
31
  - Need Mermaid-to-FigJam: `generate_diagram` (creates its own FigJam file unless an existing FigJam file key is provided).
29
- - Need code-connect lookup/update: `get_code_connect_map`, `add_code_connect_map`, suggestion/confirm functions.
32
+ - Need Code Connect lookup/update: `get_code_connect_map`, `add_code_connect_map`, suggestion/confirm functions; let the `figma-code-connect` skill invoke `get_context_for_code_connect` when generating templates.
30
33
 
31
34
  ## Prompting Pattern
32
35
 
33
36
  Use direct tool-trigger language when selection is ambiguous:
34
37
 
35
38
  - "Use Figma MCP `get_metadata` first, then `get_design_context` only for the selected child nodes."
36
- - "Use `get_libraries` if available, then use Figma MCP `search_design_system` for the selected library."
39
+ - "Use Figma MCP `get_libraries`, then `search_design_system` for the selected library."
40
+ - "Use Figma MCP `download_assets` to deliver SVG exports for these nodes."
41
+ - "Transfer these images to the target file using `download_assets` raw mode, then `upload_assets`."
37
42
  - "Use Figma MCP `search_design_system` before creating any new component."
38
43
  - "Use Figma MCP `generate_figma_design` to capture this live web UI to a new Figma file."
39
44
  - "Use Figma MCP `create_new_file`, then `use_figma` to add a first frame and typography style."
40
45
  - "Use `figma-use-figjam` with `use_figma` to organize this FigJam board into sections and connectors."
46
+ - "Use `figma-use-slides` with `use_figma` to build this kickoff deck and add speaker notes."
41
47
  - "Use MCP resources from this Figma Make link and fetch only the files needed for implementation."
42
48
 
43
49
  ## Remote/Desktop Caveats
@@ -33,7 +33,7 @@ Failure observed?
33
33
  1. Validate Figma URL format and node id.
34
34
  2. Run `whoami` to verify authenticated account.
35
35
  3. Confirm authenticated user belongs to correct plan and has file access.
36
- 4. For write-to-canvas, confirm the user has edit access; Dev seats are read-only outside drafts.
36
+ 4. For `use_figma`, confirm the user has a Full seat and edit access; current write-to-canvas docs describe Dev seats as read-only.
37
37
 
38
38
  ### Rate limiting
39
39
 
@@ -42,7 +42,8 @@ Failure observed?
42
42
  - Dev/Full seats on Professional or Organization plans have higher daily usage.
43
43
  - Enterprise Dev/Full seats have the highest documented daily usage.
44
44
  - Officially documented exempt tools include `add_code_connect_map`, `generate_figma_design`, and `whoami`.
45
- - `use_figma` write tools may be documented outside standard read limits, but still require correct seat and edit permissions.
45
+ - Professional Dev/Full seats allow up to 10 read calls per minute, Organization 15, and Enterprise 20.
46
+ - Write tools are exempt from read rate limits, but still require correct seat and edit permissions.
46
47
  - Use smaller selections and fewer repeated reads.
47
48
  - Prefer `get_metadata` preflight before broad `get_design_context`.
48
49
  - Batch intent into fewer, targeted calls.
@@ -50,7 +51,7 @@ Failure observed?
50
51
  ### Missing expected tools
51
52
 
52
53
  - Official Figma MCP tools may not be exposed by every client plugin surface.
53
- - Client-specific helpers, such as Codex `get_libraries`, are not official substitutes for every client.
54
+ - Official tools may still be absent from a particular client surface; verify the active tool list before choosing a fallback.
54
55
  - Prefer a documented fallback rather than forcing an unavailable tool.
55
56
 
56
57
  ### Write step errors
@@ -58,7 +59,9 @@ Failure observed?
58
59
  - Do not immediately retry the exact same large request.
59
60
  - Split into smaller write actions.
60
61
  - Verify partial outcomes using read tools before next step.
61
- - For `create_new_file`, ensure a plan/team context is available.
62
+ - For `create_new_file`, handle the team or organization choice when the account belongs to multiple plans.
63
+ - For Slides writes, use `figma-use-slides` rather than Design or FigJam assumptions.
64
+ - `use_figma` currently has no image/video asset support; use `upload_assets` for supported image uploads instead.
62
65
  - For `generate_diagram`, do not pre-create a blank FigJam file unless adding to an existing file is the explicit goal.
63
66
  - For FigJam writes, use `figma-use-figjam` guidance where available instead of generic Figma Design assumptions.
64
67
 
@@ -66,6 +69,7 @@ Failure observed?
66
69
 
67
70
  - Figma-hosted image URLs returned by MCP can expire.
68
71
  - Refresh the design context to get new URLs, or download/save assets into the project and reference local files for durable implementation.
72
+ - URLs returned by `download_assets` are also temporary; fetch them promptly before delivery or `upload_assets` transfer.
69
73
 
70
74
  ## Scoped Retry Pattern
71
75
 
@@ -90,10 +90,6 @@ claude mcp list
90
90
  /add-plugin figma
91
91
  ```
92
92
 
93
- ## Gemini CLI
94
-
95
- Use the Figma MCP catalog/client instructions for the Gemini CLI extension. Figma currently lists Gemini CLI as a supported client for remote and desktop setup.
96
-
97
93
  ## Cursor MCP config (desktop)
98
94
 
99
95
  ```json
@@ -120,7 +116,6 @@ Use the Figma MCP catalog/client instructions for the Gemini CLI extension. Figm
120
116
 
121
117
  ## Agent Coverage Notes
122
118
 
123
- - Figma-supported and skilly-hand-supported: `codex`, `claude`, `cursor`, `copilot`.
124
- - Figma-supported and skilly-hand-supported via client docs/catalog: `gemini`.
125
- - Figma-supported but not skilly-hand-native: Amazon Q, Android Studio, VS Code, Warp, Augment, Factory, Firebender, Kiro, OpenHands, Replit.
126
- - skilly-hand-supported but not source-backed in current Figma docs: `antigravity`, `windsurf`, `trae`.
119
+ - Figma-documented and skilly-hand-supported: `codex`, `claude`, `cursor`, `copilot`.
120
+ - Figma-documented but not skilly-hand-native: VS Code, Xcode, Claude Desktop, Warp, Augment, Factory, Firebender.
121
+ - skilly-hand-supported but not source-backed in current Figma docs: `gemini`, `antigravity`, `windsurf`, `trae`.
@@ -17,13 +17,19 @@
17
17
 
18
18
  ## Design-System and Code Connect
19
19
 
20
- - "Use `get_libraries` if available, then search only the relevant design libraries."
20
+ - "Use `get_libraries`, then search only the relevant design libraries."
21
21
  - "Use `search_design_system` to find an existing card and button component before creating anything new."
22
22
  - "Use `search_design_system` to find primary color, typography, and spacing variables."
23
23
  - "Use `get_code_connect_map` for this node and show mapped source locations."
24
24
  - "Use `add_code_connect_map` to map this Figma node to my component path."
25
25
  - "Use `get_code_connect_suggestions`, then confirm mappings with `send_code_connect_mappings` if the suggestions are correct."
26
- - "Use `figma-create-design-system-rules` to generate project rules before implementing designs from Figma."
26
+ - "Use the `figma-code-connect` skill to inspect and connect these published components."
27
+
28
+ ## Asset Transfer
29
+
30
+ - "Use `download_assets` to export these nodes as SVG and PDF deliverables."
31
+ - "Use `download_assets` raw mode to retrieve the original uploaded images."
32
+ - "Copy the images from this file into the target file using `download_assets` followed by `upload_assets`."
27
33
 
28
34
  ## First Canvas Creation
29
35
 
@@ -49,13 +55,21 @@
49
55
  - "Use `figma-use-figjam` with `use_figma` to organize this FigJam board into sections with stickies and connectors."
50
56
  - "Use `use_figma` to update this architecture diagram with a new service."
51
57
 
58
+ ## Figma Slides
59
+
60
+ - "Use `create_new_file` to create a Figma Slides deck named 'Q3 Review'."
61
+ - "Use `figma-use-slides` with `use_figma` to build a five-slide kickoff deck with speaker notes."
62
+ - "Use `get_screenshot` to verify the title slide and agenda slide."
63
+
52
64
  ## Figma Skills
53
65
 
54
66
  - "Use `figma-use` for this Figma Design write-to-canvas task."
55
67
  - "Use `figma-use-figjam` for this FigJam board update."
68
+ - "Use `figma-use-slides` for this Figma Slides deck update."
69
+ - "Use `figma-swiftui` to implement this design in SwiftUI or push these SwiftUI views into Figma."
70
+ - "Use `figma-generate-diagram` to turn this architecture description into an editable FigJam diagram."
56
71
  - "Use `figma-generate-design` to build this app screen in Figma using the connected design system."
57
72
  - "Use `figma-generate-library` to create or sync a Figma design-system library from this codebase."
58
- - "Use `figma-implement-design` to turn this Figma frame URL into production code."
59
73
 
60
74
  ## Agent Coverage
61
75
 
@@ -67,5 +81,6 @@
67
81
  - "I got a permission error. Use `whoami` and tell me what to check next."
68
82
  - "I am rate-limited. Switch to a staged workflow with fewer `get_design_context` calls."
69
83
  - "This client does not expose `get_screenshot`. Choose the closest supported verification path."
70
- - "My `create_new_file` call failed. Check whether a plan key or team context is missing."
84
+ - "My `create_new_file` call failed. Check whether I need to choose a team or organization."
71
85
  - "Images from the MCP response expired. Refresh the design context or save the assets locally."
86
+ - "The `download_assets` URLs expired. Run the scoped export again and fetch the returned URLs immediately."
@@ -10,10 +10,10 @@
10
10
  "agentSupport": ["codex", "claude", "cursor", "gemini", "copilot", "antigravity", "windsurf", "trae"],
11
11
  "skillMetadata": {
12
12
  "author": "skilly-hand",
13
- "last-edit": "2026-05-09",
13
+ "last-edit": "2026-06-20",
14
14
  "license": "Apache-2.0",
15
- "version": "1.0.3",
16
- "changelog": "Updated Figma MCP guidance for current remote-first docs, supported-client coverage, Figma-provided skills, FigJam write workflows, code-to-canvas support, and access/rate-limit language; affects setup routing, tool selection, prompt assets, and official matrix",
15
+ "version": "1.1.0",
16
+ "changelog": "Synced the official Figma MCP surface for asset transfer, Code Connect context, library discovery, Figma Slides, current Figma-provided skills, and per-minute limits; affects tool routing, canvas workflows, prompts, troubleshooting, and the official matrix",
17
17
  "auto-invoke": "Installing, configuring, or using Figma MCP from setup through first canvas creation",
18
18
  "allowed-modes": [
19
19
  "install-auth",
@@ -1,27 +1,30 @@
1
- # Official Figma MCP Tools Matrix (As of 2026-05-09)
1
+ # Official Figma MCP Tools Matrix (As of 2026-06-20)
2
2
 
3
- This matrix tracks the official Figma MCP tool/function set in current Figma documentation. Treat it as the source of truth for official tool names, supported file types, and remote-only status. Client-specific helpers are listed separately.
3
+ This matrix tracks the official Figma MCP tool/function set in current Figma documentation. Treat it as the source of truth for official tool names, supported file types, and remote-only status.
4
4
 
5
5
  ## Coverage Matrix
6
6
 
7
7
  | Tool | Primary Purpose | Typical Input | Supported File Types | Availability Notes |
8
8
  | --- | --- | --- | --- | --- |
9
+ | `download_assets` | Download rendered exports and original source images | Up to 20 node IDs and optional export settings | Figma Design, FigJam, Figma Slides | Remote-only; returns temporary URLs; use for delivery, non-PNG formats, full-resolution exports, or cross-file transfer. |
10
+ | `upload_assets` | Upload supported image assets to a file or node | PNG, JPG, GIF, or WebP URLs/files | Figma Design, FigJam, Figma Slides | Remote-only; maximum 10 MB per asset; uploads to a node fill or creates image-filled frames. |
9
11
  | `generate_figma_design` | Generate editable design layers from live web UI | URL/local app capture context | Figma Design output | Remote-only; select clients only; can output to new file, existing file, or clipboard; exempt from standard read limits. |
10
12
  | `get_design_context` | Fetch rich design context for implementation | Figma URL or `fileKey` + `nodeId` | Figma Design, Figma Make | Read tool; remote server requires link-based node targeting; desktop can use selection-based prompts. |
11
13
  | `get_variable_defs` | Retrieve variable/token definitions | `fileKey` + `nodeId` | Figma Design | Best for token-only extraction. |
12
14
  | `get_code_connect_map` | Read existing Code Connect mappings | `fileKey` + `nodeId` | Figma Design | Use to inspect mapping before updates. |
13
15
  | `add_code_connect_map` | Add mapping from node to code component | `fileKey`, `nodeId`, source details | Figma Design | Write-style utility; exempt from read rate limits in docs. |
14
- | `get_screenshot` | Render node screenshot for visual verification | `fileKey` + `nodeId` | Figma Design, FigJam | Useful verification after write steps and for preserving visual fidelity. |
15
- | `create_design_system_rules` | Generate design-system rules prompt/scaffold | Framework/language context | No file context required | Use to enforce repeatable design-system workflows. |
16
+ | `get_context_for_code_connect` | Fetch component metadata for Code Connect template generation | Figma component context | Figma Design | Remote-only; prompted by Figma and intended for the `figma-code-connect` skill, not direct user invocation. |
17
+ | `get_screenshot` | Render node screenshot for visual verification | `fileKey` + `nodeId` | Figma Design, FigJam, Figma Slides | Use for visual inspection; prefer `download_assets` for delivery, multiple nodes, other formats, or original images. |
16
18
  | `get_metadata` | Sparse XML structure (ids, names, hierarchy, bounds) | Selection or `fileKey` + `nodeId` | Figma Design | Preferred preflight for large contexts. |
17
19
  | `get_figjam` | Fetch FigJam metadata (and node visuals) | `fileKey` + `nodeId` | FigJam | FigJam-specific extraction. |
18
20
  | `generate_diagram` | Create FigJam diagram from Mermaid or natural language intent | Diagram description or Mermaid syntax | No file context required | Remote-only; supports flowchart, gantt, state, sequence, architecture, and ERD workflows. |
19
21
  | `whoami` | Show authenticated Figma identity, plans, and seat types | None | No file context required | Remote-only in official docs; exempt from read rate limits. |
20
22
  | `get_code_connect_suggestions` | Suggest candidate node-to-code mappings | File context + repo context | Figma Design | Usually part of Code Connect workflows. |
21
23
  | `send_code_connect_mappings` | Confirm/persist mapping suggestions | Suggestions payload | Figma Design | Follow-up action after suggestion generation. |
22
- | `use_figma` | General-purpose write/edit/delete/inspect via Plugin API workflow | Task instructions and file context | Figma Design, FigJam | Remote-only; default direct write/update path; use `figma-use` for Figma Design and `figma-use-figjam` for FigJam when available. |
24
+ | `get_libraries` | List subscribed and available design libraries | Figma file context | Figma Design | Remote-only; use with `search_design_system` for scoped reuse. |
25
+ | `use_figma` | General-purpose write/edit/delete/inspect via Plugin API workflow | Task instructions and file context | Figma Design, FigJam, Figma Slides | Remote-only; pair with `figma-use`, `figma-use-figjam`, or `figma-use-slides` for the active editor. |
23
26
  | `search_design_system` | Search libraries for components, variables, styles | Query text and optional type narrowing | Figma Design | Remote-only; use before creating new artifacts when design-system reuse is relevant. |
24
- | `create_new_file` | Create new blank Design or FigJam file | File name, file type, plan context | No file context required | Remote-only; creates files in drafts or a project; requires plan/team context in some clients. |
27
+ | `create_new_file` | Create new blank Design, FigJam, or Slides file | File name, file type, plan context | No file context required | Remote-only; creates files in drafts and may ask which team or organization to use. |
25
28
 
26
29
  ## Figma Make Resources
27
30
 
@@ -35,30 +38,23 @@ Figma documents these skills as the preferred guidance layer for common MCP work
35
38
  | --- | --- |
36
39
  | `figma-use` | Foundational Figma Design write-to-canvas workflow. |
37
40
  | `figma-use-figjam` | Foundational FigJam write workflow. |
38
- | `figma-code-connect-components` | Connect published Figma components to code implementations. |
39
- | `figma-create-design-system-rules` | Generate project rules for design-to-code workflows. |
40
- | `figma-create-new-file` | Create blank Design or FigJam files. |
41
- | `figma-implement-design` | Translate a Figma design URL into production code. |
41
+ | `figma-use-slides` | Foundational Figma Slides write workflow. |
42
+ | `figma-swiftui` | Translate between Figma designs and SwiftUI in both directions. |
43
+ | `figma-code-connect` | Connect published Figma components to code implementations. |
44
+ | `figma-create-new-file` | Create blank Design, FigJam, or Slides files. |
45
+ | `figma-generate-diagram` | Generate editable FigJam diagrams from descriptions or source material. |
42
46
  | `figma-generate-library` | Example workflow for generating or syncing a design-system library. |
43
47
  | `figma-generate-design` | Example workflow for building screens/views from a design system. |
44
48
 
45
- ## Codex Plugin Helpers
46
-
47
- The Codex Figma plugin may expose helper tools beyond the current official tools page. Keep these documented as client-specific helpers:
48
-
49
- | Helper | Purpose | Notes |
50
- | --- | --- | --- |
51
- | `get_libraries` | List libraries associated with a Figma file | Use before scoped `search_design_system`; not listed on the official Figma tools page as of this matrix date. |
52
-
53
49
  Some official Figma MCP tools may not be exposed by every client plugin surface. Prefer the active client's tool list over assumptions when executing.
54
50
 
55
51
  ## Client and Agent Coverage
56
52
 
57
53
  | Coverage | Agents or Clients | Guidance |
58
54
  | --- | --- | --- |
59
- | Figma-supported and skilly-hand-supported | `codex`, `claude`, `cursor`, `copilot`, `gemini` | Include concrete setup paths where documented; otherwise point to the Figma MCP catalog/client docs. |
60
- | Figma-supported but not skilly-hand-native | Amazon Q, Android Studio, VS Code, Warp, Augment, Factory, Firebender, Kiro, OpenHands, Replit | Mention as Figma-supported clients; do not add skilly-hand install assumptions. |
61
- | skilly-hand-supported but not source-backed in current Figma docs | `antigravity`, `windsurf`, `trae` | Keep broad install support; advise manual MCP/client docs for Figma-specific setup. |
55
+ | Figma-documented and skilly-hand-supported | `codex`, `claude`, `cursor`, `copilot` | Use published setup paths; Copilot is currently listed for Copilot CLI write-to-canvas. |
56
+ | Figma-documented but not skilly-hand-native | VS Code, Xcode, Claude Desktop, Warp, Augment, Factory, Firebender | Mention only for workflows where Figma lists them; do not add skilly-hand install assumptions. |
57
+ | skilly-hand-supported but not source-backed in current Figma docs | `gemini`, `antigravity`, `windsurf`, `trae` | Verify the Figma MCP Catalog or current client docs before recommending setup. |
62
58
 
63
59
  ## Rate-Limit Notes (Official)
64
60
 
@@ -66,9 +62,11 @@ Some official Figma MCP tools may not be exposed by every client plugin surface.
66
62
  - Remote server access is documented for all seats/plans, but practical usage is governed by seat/plan limits.
67
63
  - Desktop server access is documented for Dev or Full seats on paid plans.
68
64
  - Starter plan or View/Collab seats: up to 6 tool calls per month.
69
- - Professional or Organization with Dev/Full seat: up to 200 tool calls per day.
70
- - Enterprise with Dev/Full seat: up to 600 tool calls per day.
71
- - Dev seats only have read-only access outside drafts for write-to-canvas workflows.
65
+ - Professional with Dev/Full seat: up to 200 tool calls per day and 10 per minute.
66
+ - Organization with Dev/Full seat: up to 200 tool calls per day and 15 per minute.
67
+ - Enterprise with Dev/Full seat: up to 600 tool calls per day and 20 per minute.
68
+ - Current write-to-canvas docs require a Full seat for `use_figma`; Dev seats are described as read-only.
69
+ - Code-to-canvas can create or edit draft files with any seat; existing files outside drafts require a Full seat and edit permission.
72
70
  - Officially documented exempt tools include:
73
71
  - `add_code_connect_map`
74
72
  - `generate_figma_design`
@@ -78,12 +76,13 @@ Some official Figma MCP tools may not be exposed by every client plugin surface.
78
76
 
79
77
  1. Start with `whoami` when authentication or permissions are uncertain.
80
78
  2. Use `get_metadata` before `get_design_context` for large files.
81
- 3. Use `get_libraries` where available, then `search_design_system` for scoped design-system reuse.
79
+ 3. Use `get_libraries`, then `search_design_system` for scoped design-system reuse.
82
80
  4. Use `generate_figma_design` for first-time live web UI capture.
83
- 5. Use `use_figma` for direct Figma Design or FigJam writes and updates.
81
+ 5. Use `use_figma` for direct Figma Design, FigJam, or Slides writes and updates.
84
82
  6. Keep `use_figma` calls small and validate after each step.
85
83
  7. Use `get_screenshot` as final visual verification after edits when available.
86
- 8. Use `figma-use-figjam` rather than Figma Design assumptions for FigJam board edits.
84
+ 8. Use the editor-specific skill for writes: `figma-use`, `figma-use-figjam`, or `figma-use-slides`.
85
+ 9. Use `download_assets` and `upload_assets` for asset delivery or cross-file image transfer; returned download URLs are temporary.
87
86
 
88
87
  ## Sources
89
88
 
@@ -94,6 +93,6 @@ Some official Figma MCP tools may not be exposed by every client plugin surface.
94
93
  - https://developers.figma.com/docs/figma-mcp-server/write-to-canvas/
95
94
  - https://developers.figma.com/docs/figma-mcp-server/code-to-canvas/
96
95
  - https://developers.figma.com/docs/figma-mcp-server/bringing-make-context-to-your-agent/
97
- - https://developers.figma.com/docs/figma-mcp-server/plans-access-and-permissions/
96
+ - https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/
98
97
  - https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Figma-MCP-server
99
98
  - https://help.figma.com/hc/en-us/articles/39166810751895-Figma-skills-for-MCP
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skilly-hand/skilly-hand",
3
- "version": "0.29.1",
3
+ "version": "0.29.2",
4
4
  "license": "CC-BY-NC-4.0",
5
5
  "type": "module",
6
6
  "repository": {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skilly-hand/catalog",
3
- "version": "0.29.1",
3
+ "version": "0.29.2",
4
4
  "private": true,
5
5
  "type": "module"
6
6
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skilly-hand/cli",
3
- "version": "0.29.1",
3
+ "version": "0.29.2",
4
4
  "private": true,
5
5
  "type": "module",
6
6
  "bin": {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skilly-hand/core",
3
- "version": "0.29.1",
3
+ "version": "0.29.2",
4
4
  "private": true,
5
5
  "type": "module"
6
6
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skilly-hand/detectors",
3
- "version": "0.29.1",
3
+ "version": "0.29.2",
4
4
  "private": true,
5
5
  "type": "module"
6
6
  }