ClaudeSuperPower
SubmitLog in

figma-use-figjam

Skill

This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

0Design

Install

git clone https://github.com/figma/mcp-server-guide.git ~/.claude/skills/figma-use-figjam

What is figma-use-figjam?

This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~43 tokens of context used while enabled, before you invoke anything

Documentation

README · ~4 min read

use_figma — Figma Plugin API Skill for FigJam

This skill contains FigJam-specific context for the use_figma MCP tool. The figma-use skill provides foundational context for plugin API execution via MCP as well as the full Figma plugin API for more advanced use-cases that are not described here.

Always include figma-use-figjam in the comma-separated skillNames parameter when calling use_figma for FigJam operations. If this skill was loaded via an MCP resource, you MUST prefix the name with resource: (e.g. resource:figma-use-figjam). This is a logging parameter used to track skill usage — it does not affect execution.

FigJam URL is figma.com/board/.... Do NOT call figma.createPage() in FigJam — it throws TypeError: figma.createPage no such property 'createPage' on the figma global object. createPage() is a Design-file API only (figma.com/design/...). FigJam files have a single implicit page; organize content with sections instead (see create-section).

Inspecting FigJam Files

get_figjam is the inspection tool for FigJam files. It returns the full node tree as XML, including IDs of pages, sections, stickies, connectors, and other nodes you need to reference in subsequent use_figma calls.

  • Use get_figjam upfront before writing any use_figma code that needs to reference existing nodes (page IDs, section IDs, etc.). Don't try to discover IDs by running an inspection script — console.log output from use_figma is not returned to the agent (see figma-use Critical Rule #4). Only the return value comes back.
  • get_metadata does NOT work on FigJam files — it is design-mode only and will fail immediately with "unsupported for FigJam files".
  • get_screenshot requires a valid nodeId — passing an empty nodeId returns "invalid nodeId" error. Get IDs from get_figjam first.
  • If you forgot to return an ID from a previous use_figma call and need it now, call get_figjam rather than re-running an inspection script.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

code-architect

Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences

32.8K stars

plugin-validator

Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: <example> Context: User f

32.8K stars

scan-inventory

Restricted read-only repository cartographer dispatched by the Claude Security scan workflow to partition the tree into components and account for every top-level directory; not for direct invocation or vulnerability research.

32.8K stars