Figma Use Figjam

If you're building FigJam boards programmatically through Claude, this is the companion skill to figma-use that adds all the FigJam-specific context. It teaches Claude how to create stickies, connectors, sections, and tables without hitting the common gotchas like trying to use createPage (which doesn't exist in FigJam) or forgetting to load fonts before editing text. The skill emphasizes using get_figjam upfront to inspect the board structure, batching tool calls instead of going one at a time, and following the canonical text mutation recipe. There's also solid guidance on planning board content for retros, brainstorms, and meeting templates. Worth pairing with figma-use for any serious FigJam automation work.

skills.sh installs: 2.2K
GitHub stars: 2.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add figma/mcp-server-guide --skill figma-use-figjam --agent claude-code

Installs into .claude/skills of the current project.

Files

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).