**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)
Installs into .claude/skills of the current project.
Are you the author of X Openai Figma Create New File Ffa32bb?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/geruyang-x-openai-figma-create-new-file-ffa32bb)
---
name: x-openai-figma-create-new-file-ffa32bb
description: '**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)'
---
### 导出副本边界与技能别名
迁移、安装、修复和经验回写只作用于当前加载的目标宿主技能副本。原 Codex 技能/MCP、下载的源码和 `original-skills` 均为来源材料,不因执行本副本而写入;只有用户另行明确要求配置 Codex 产品本身时,才按该产品流程处理指定目标。脚本需要安装目录或状态目录时,显式提供目标路径;不得从 `CODEX_HOME` 隐式推断写入位置。
跨技能名称可能沿用源库别名。先查 [技能别名表](../../skill-aliases.json),优先选择同来源、同插件的条目,再使用其 `id` 调用或读取对应入口;不得假定旧 `$skill`、`superpowers:skill` 名称在新宿主直接注册。不能确定目标时先核对,不替换真实产品命令或 Shell 环境变量。
## Reviewed capability mapping (TRAE / Claude)
Discover an authenticated Figma file-creation capability and account/plan discovery first. The `create_new_file`, `whoami`, `planKey`, `file_key`, and `file_url` contract below belongs to the referenced Figma MCP integration; use it only if its schema is exposed. An alternative adapter must document equivalent editor type, ownership, creation, and returned identifiers. The generic Figma REST API must not be assumed to support blank-file creation. If no supported creator exists, report the blocked step. Slash-command examples are optional host shortcuts; natural-language invocation works too.
## 跨宿主使用约定
本副本供支持 Agent Skills 的客户端使用。先检查当前宿主实际提供的工具、权限和已连接服务,再执行正文工作流。原文中的宿主工具标识是能力参考;只有实际发现该工具时才可调用,其他宿主应使用经核验的等价 MCP、CLI 或 API。没有等价能力的步骤必须报告不可用,不能虚构调用或完成状态。
技能资源以本技能目录为基准;输出写入当前项目中用户指定的位置。通过技能名称或自然语言触发,具体快捷命令由宿主决定。涉及真实产品、模型 API、协议字段和官方网址的名称保持原意。授权、审批、隐私和工具范围限制在迁移后仍然有效;不得为兼容而扩大权限。具体依赖与迁移说明见同目录 `PORTABILITY.md`。
# create_new_file — Create a New Figma File
**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:
1. **User already provided a planKey** (e.g. from a previous `whoami` call or in their prompt) → use it directly, skip to Step 2.
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:
```json
{
"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](../x-openai-figma-use-slides-2e7b5c9/references/slide-grid.md) for full details.