Home

Skill

MCP Tools

figma-create-new-file

figma/mcp-server-guide

**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `create_new_file` tool call. NEVER call `create_new_file` directly without loading this skill first. Trigger whenever the user wants a new blank Figma file — a new design, FigJam, or Slides file — or when you need a fresh file before calling `use_figma`. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review)

...Expand all

Updated time August 27, 2026

# automation # mcp # file-management # design # MCP ToolsProductivity & Workflow # figma

About figma-create-new-file

Wraps the create_new_file MCP tool, which creates a new blank Figma file in the user's drafts folder for a selected plan. It is positioned as a mandatory prerequisite that must be loaded before every create_new_file call, because it encodes the plan-resolution decision tree, the editor-type contract, and the post-creation handoff to use_figma. It is typically used before use_figma when a fresh file is needed, for example a new design, FigJam, or Slides file.

The skill accepts optional arguments in the form editorType then fileName, where editorType is design (the default), figjam, or slides, and fileName defaults to Untitled. The workflow first resolves a planKey: if the user already provided one it is used directly, otherwise the whoami tool is called and its plans array is inspected, automatically using the single plan's key or asking the user which team or organization to use when multiple plans exist. It then calls create_new_file with the required planKey, fileName, and editorType parameters, and uses the returned file_key and file_url, passing file_key to subsequent calls such as use_figma.

Editor-type behavior is part of the contract. Supported editor types are design, figjam, and slides, and every file is created in the drafts folder of the selected plan. A documented caveat applies to slides files: a newly created slides file starts with zero rows and zero slides, so figma.getSlideGrid() returns an empty array rather than a default first slide, and the page's only child is the empty SLIDE_GRID node. The first call to figma.createSlide() implicitly creates row zero and inserts the slide there, so follow-up use_figma scripts that assume at least one slide should guard for the empty case or call createSlide() first. When use_figma is the next step, the figma-use skill should be loaded before calling it.

FAQ

What arguments does this skill accept?

Optional editorType and fileName. editorType is design (default), figjam, or slides, and fileName defaults to Untitled. For example, /figma-create-new-file slides Q3 Review creates a Slides presentation named Q3 Review.

How is the planKey resolved?

If the user already supplied a planKey it is used directly. Otherwise the whoami tool is called: a single plan's key is used automatically, while multiple plans prompt the user to choose which team or organization to create the file in.

Where is the new file created?

In the user's drafts folder for the selected plan. The tool returns a file_key and a file_url that opens the file directly in Figma.

What is special about newly created Slides files?

A slides file starts with zero rows and zero slides, so figma.getSlideGrid() returns an empty array instead of a default first slide. The first figma.createSlide() call implicitly creates row zero, so guard for the empty case or call createSlide() first.

What should I do after the file is created?

Use the returned file_key for subsequent tool calls such as use_figma. If use_figma is the next step, load the figma-use skill before calling it.

View on GitHub

MANDATORY: load this skill before every create_new_file tool call. It encodes the plan-resolution decision tree, the editor-type contract, and the post-creation handoff to use_figma.

Use the create_new_file MCP tool to create a new blank Figma file in the user's drafts folder. This is typically used before use_figma when you need a fresh file to work with.

Skill Arguments

This skill accepts optional arguments: /figma-create-new-file [editorType] [fileName]

editorType: design (default), figjam, or slides
fileName: Name for the new file (defaults to "Untitled")

Examples:

/figma-create-new-file — creates a design file named "Untitled"
/figma-create-new-file figjam My Whiteboard — creates a FigJam file named "My Whiteboard"
/figma-create-new-file design My New Design — creates a design file named "My New Design"
/figma-create-new-file slides Q3 Review — creates a Slides presentation named "Q3 Review"

Parse the arguments from the skill invocation. If editorType is not provided, default to "design". If fileName is not provided, default to "Untitled".

Workflow

Step 1: Resolve the planKey

The create_new_file tool requires a planKey parameter. Follow this decision tree:

User already provided a planKey (e.g. from a previous whoami call or in their prompt) → use it directly, skip to Step 2.
No planKey available → call the whoami tool. The response contains a plans array. Each plan has a key, name, seat, and tier.
- Single plan: use its key field automatically.
- Multiple plans: ask the user which team or organization they want to create the file in, then use the corresponding plan's key.

Step 2: Call create_new_file

Call the create_new_file tool with:

Parameter	Required	Description
`planKey`	Yes	The plan key from Step 1
`fileName`	Yes	Name for the new file
`editorType`	Yes	`"design"`, `"figjam"`, or `"slides"`

Example:

{  "planKey": "team:123456",  "fileName": "My New Design",  "editorType": "design"}

Step 3: Use the result

The tool returns:

file_key — the key of the newly created file
file_url — a direct URL to open the file in Figma

Use the file_key for subsequent tool calls like use_figma.

Important Notes

The file is created in the user's drafts folder for the selected plan.
Supported editor types are "design", "figjam", and "slides".
If use_figma is your next step, load the figma-use skill before calling it.

Editor-specific notes

Slides — newly created files have an empty grid

A slides file produced by this tool starts with zero rows and zero slides — figma.getSlideGrid() returns [], not a default first slide. The page's only child is the SLIDE_GRID node itself, which is empty until you create content. The first call to figma.createSlide() implicitly creates row 0 and inserts the new slide there.

If your follow-up use_figma script assumes at least one slide exists (e.g. to read theme tokens off it), guard for the empty case or call createSlide() first. See figma-use-slides → slide-grid for full details.