figma-create-new-file
by openaifigma-create-new-file creates a new blank Figma Design file or FigJam board in drafts. Use it when you need a fresh starting point before deeper Figma actions, including use_figma. It supports design or figjam, optional file naming, and can resolve plan access with whoami when needed.
This skill scores 78/100, which means it is a solid directory candidate for users who need a reliable way to create a new blank Figma or FigJam file before continuing work. The repo gives enough trigger and workflow detail to support installation decisions, though users should note the dependency on Figma’s MCP tools and the need to resolve a planKey when it is not already known.
- Explicit command syntax and examples make the skill easy to trigger correctly.
- Step-by-step workflow covers planKey resolution and defaults, reducing guesswork for agents.
- OpenAI agent config and Figma MCP dependency provide clear integration context.
- The workflow depends on external Figma MCP access and plan resolution, so it is not fully self-contained.
- The skill is narrowly scoped to file creation, so it is useful as a utility but not a broader Figma automation package.
Overview of figma-create-new-file skill
What figma-create-new-file does
figma-create-new-file creates a new blank Figma Design file or FigJam board in the user’s drafts, usually as the first step before deeper Figma actions. It is a good fit when you need a clean starting point, want to separate a new task from an existing file, or need to invoke use_figma only after the file exists.
Who should install it
Install the figma-create-new-file skill if you regularly automate UI Design setup, prototype kickoff, or workshop board creation inside Figma. It is most useful for agents and workflows that need a reliable, low-friction way to open a new file without hand-holding the file creation step every time.
What matters before using it
The main decision points are simple: choose design or figjam, and optionally name the file. The skill also handles plan resolution with whoami when a planKey is not already available, which is the main thing that can block a direct call if you skip the prerequisite context.
How to Use figma-create-new-file skill
Install and confirm the Figma MCP setup
Use the skill in the OpenAI skills environment with the Figma MCP server available. The repository points to https://mcp.figma.com/mcp, so this is not a standalone prompt trick; it depends on the Figma tool connection being active. If the skill is unavailable, the usual failure mode is missing MCP access rather than bad wording.
Give the skill the right input
The usage pattern is /figma-create-new-file [editorType] [fileName]. editorType defaults to design, and fileName defaults to Untitled, so only specify what changes the outcome. Good examples are:
/figma-create-new-file/figma-create-new-file figjam My Whiteboard/figma-create-new-file design Landing Page v2
For figma-create-new-file usage, the most useful input is a short, explicit intent plus the desired file type and name. If you want a board for collaboration, say figjam; if you want a working design canvas, say design.
Read these files first
For a quick install decision and reliable execution, read SKILL.md first, then agents/openai.yaml for prompt and dependency context, and LICENSE.TXT for the beta/terms boundary. If you want to understand why the skill can request plan resolution, inspect the whoami and create_new_file workflow in SKILL.md before trying to adapt it.
A practical workflow that avoids errors
Use the skill in this order: decide the editor type, choose a meaningful name, confirm whether a planKey is already known, then call the skill. If you are starting from a rough task like “make a place to sketch the onboarding flow,” turn it into a prompt such as: “Create a FigJam board named Onboarding Flow Workshop.” If you are preparing a design task, use: “Create a design file named Checkout Redesign Draft.” Clear naming reduces follow-up confusion later.
figma-create-new-file skill FAQ
Is figma-create-new-file only for new files?
Yes. The figma-create-new-file skill is specifically for creating a blank new file, not editing existing pages or generating layouts. If you already have a target file, this skill is the wrong entry point.
Do I need to provide a planKey every time?
No. The skill can resolve the plan key through whoami when needed. If you already have a valid planKey, pass it through from earlier context; otherwise, expect the skill to handle that lookup before file creation.
Is this good for UI Design work?
Yes, especially when you need a clean design file before using other Figma actions. For figma-create-new-file for UI Design, the key benefit is speed: it removes the startup step so you can move directly into structure, frames, or handoff-ready work.
When should I not use this skill?
Do not use figma-create-new-file if you need to modify an existing file, create multiple files at once, or produce design content automatically. It is also not useful if your environment cannot reach the Figma MCP server or if your workflow does not support Figma drafts.
How to Improve figma-create-new-file skill
Provide the smallest useful brief
The best results come from naming the editor type and file purpose in one line. “Create a FigJam board for a product kickoff” is better than “make a file” because it gives the skill a clear target and reduces naming ambiguity. For figma-create-new-file install decisions, this is the main reason the skill is worth adding: it converts a vague start into a usable file in one step.
Avoid the common failure modes
The most common issue is leaving the file type implied when you actually need the opposite default. Another is using a generic name like Untitled when the file will be shared with a team. If you expect to continue into use_figma, make sure the file name and file type match the next action so you do not waste time renaming or reopening later.
Iterate with better context next time
If the first output is not what you wanted, improve the next prompt by adding the board purpose, audience, and file type. Example upgrades:
- weak: “Create a file”
- stronger: “Create a design file named Mobile Nav Exploration for a redesign review”
- strongest: “Create a FigJam board named Q3 App Onboarding Workshop for cross-functional brainstorming”
That kind of context helps the figma-create-new-file guide stay aligned with the real job: opening the right kind of Figma workspace fast, with fewer corrections afterward.