figma-create-new-file
by figmafigma-create-new-file creates a new blank Figma or FigJam file in drafts, with defaults for editor type and file name. This figma-create-new-file skill helps with design implementation, rapid prototyping, and starting a fresh canvas before use_figma. It also handles planKey resolution via whoami when needed.
This skill scores 81/100, which means it is a solid listing candidate for directory users. It clearly defines when to trigger it, how to invoke it, and what defaults to expect, so an agent can create a new Figma or FigJam file with less guesswork than a generic prompt.
- Explicit trigger and usage syntax: /figma-create-new-file [editorType] [fileName], with examples for design and FigJam.
- Operational workflow is concrete: it explains default values and the need to resolve planKey via whoami before calling create_new_file.
- Good progressive disclosure: the skill is scoped to one task and includes enough steps to execute without broad interpretation.
- No install command or supporting files, so adoption depends entirely on the SKILL.md instructions.
- The excerpt is truncated before the full workflow details, so edge-case handling and failure recovery may be limited or harder to evaluate.
Overview of figma-create-new-file skill
What figma-create-new-file does
The figma-create-new-file skill creates a new blank Figma file in the user’s drafts, with support for either a standard design file or a FigJam board. It is most useful when you already know you need a fresh canvas before other Figma actions, especially before use_figma or other follow-up workflow steps.
Who should install it
Install figma-create-new-file if you work in an agent flow where the model needs to open the right kind of file reliably instead of asking the user to do it manually. It is a good fit for design implementation, rapid prototyping, workshop setup, and any prompt where file creation is a repeatable first step.
Why this skill is more than a generic prompt
The main value of the figma-create-new-file skill is not just “create a file,” but handling the small operational details that often block automation: choosing design vs figjam, defaulting the file name sensibly, and resolving the required planKey when needed. That makes it safer than a one-off instruction when you want a predictable handoff into the Figma workflow.
How to Use figma-create-new-file skill
Install and locate the source
For install, use the directory’s normal skill add flow for figma/mcp-server-guide, then open skills/figma-create-new-file/SKILL.md first. There are no extra helper files in this skill, so the behavior you need to understand lives in that single document. Reading the skill directly matters because the figma-create-new-file install path is simple, but correct invocation still depends on the argument rules.
Pass the right input in the prompt
The figma-create-new-file usage pattern is:
/figma-create-new-file [editorType] [fileName]
Use design for a blank Figma design file and figjam for a whiteboard-style file. If you omit editorType, it defaults to design. If you omit the name, it defaults to Untitled. Strong prompts are explicit, for example: “Create a FigJam file called Q3 workshop notes, then continue with the planning flow.”
Handle plan resolution cleanly
The skill can require a planKey before it can call create_new_file. If you already have one from whoami or a prior step, include it in the workflow context and avoid re-resolving it. If you do not, expect the skill to check whoami first. This matters because prompt failures usually come from skipping identity or plan context, not from the file creation action itself.
Read the workflow in the right order
Start with the argument section, then the Workflow section, then the Step 1: Resolve the planKey and Step 2: Call create_new_file instructions. That order shows you the actual execution path: parse the command, confirm access context, then create the file. If you are using figma-create-new-file for Design Implementation, this is the path that gets you from a design brief to a usable Figma draft without extra manual setup.
figma-create-new-file skill FAQ
Is figma-create-new-file only for design files?
No. The figma-create-new-file skill supports both design and figjam. Use design files for interface work and FigJam for planning, workshops, and loose diagramming.
Do I need to provide a file name every time?
No. The skill defaults to Untitled when no name is given. Still, naming the file in the prompt improves downstream organization, especially if multiple drafts may be created in one session.
Is this different from just asking for a new Figma file?
Yes. A normal prompt can describe the intent, but the skill encodes the operational details: command syntax, default editor type, naming defaults, and plan lookup behavior. That makes it more reliable when the agent must actually trigger the file creation step.
When should I not use it?
Do not use it if you already have the target Figma file, if the task is only to edit an existing board, or if you cannot supply the access context needed to resolve planKey. In those cases, a different Figma skill or a direct edit workflow is a better fit.
How to Improve figma-create-new-file skill
Give the agent the exact file intent
The best way to improve figma-create-new-file results is to specify the file type, the purpose, and the desired name in one sentence. Better: “Create a FigJam file named Sprint retro for a team retrospective.” Weaker: “Make a Figma file.” The first version reduces ambiguity and prevents the skill from defaulting to a less useful file type.
Keep the workflow context available
If your environment already has a planKey, pass it through instead of forcing a lookup. That removes one dependency and lowers the chance of a stalled run. If you do not have it, make sure the surrounding prompt or session allows whoami to succeed.
Iterate from the first blank file
This skill only creates the file; it does not solve the design problem. After the file exists, follow with the next Figma action using the same naming and scope you requested here. If the first output is not what you wanted, adjust the editor type, file name, or access context before retrying rather than layering more instructions onto the create step.