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.