From figma
Provides FigJam-specific context for Figma's use_figma MCP tool: inspect files with get_figjam, plan board content, batch-load schemas. Pair with figma-use skill for FigJam operations.
npx claudepluginhub anthropics/claude-plugins-official --plugin figmaThis skill uses the workspace's default tool permissions.
This skill contains FigJam-specific context for the `use_figma` MCP tool. The [figma-use](../figma-use/SKILL.md) 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.
references/batch-modify.mdreferences/create-code-block.mdreferences/create-connector.mdreferences/create-label.mdreferences/create-section.mdreferences/create-shape-with-text.mdreferences/create-sticky.mdreferences/create-table.mdreferences/create-text.mdreferences/edit-text.mdreferences/plan-board-content.mdreferences/position-figjam-nodes.mdCreate diagrams (flowchart, UML, ER, mindmap), documents, tables on Miro boards; extract context, read items/tables/images, edit docs via MCP tools.
Routes generate_diagram tool calls to type-specific Mermaid guides for flowcharts, architecture diagrams, sequences, ERDs, states, Gantts with universal constraints for Figma FigJam output.
Creates new blank Figma design or FigJam file in user's drafts. Resolves plan via whoami if needed, returns file key/URL for use_figma.
Share bugs, ideas, or general feedback.
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 pass skillNames: "figma-use-figjam" when calling use_figma for FigJam operations. This is a logging parameter used to track skill usage — it does not affect execution.
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.
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.return an ID from a previous use_figma call and need it now, call get_figjam rather than re-running an inspection script.Load only the references your task needs — but when you do need to load multiple, issue all reads in a single parallel tool-call batch, not sequentially across turns. For a typical board-creation task, that means a single message containing reads for plan-board-content plus the 3-4 specific node-type references you'll use.
The Figma MCP tools (use_figma, get_figjam, get_screenshot, get_metadata, create_new_file, whoami) often appear as deferred tools that require ToolSearch to load their schemas before they can be called. Load all schemas in a single ToolSearch call using the select: syntax instead of one call per tool:
ToolSearch query="select:use_figma,get_figjam,get_screenshot,get_metadata,create_new_file"
Six sequential ToolSearch calls is six round trips before any work happens. One batched call is one round trip.