mcpbeat Sign in

Figma Create New File Skill for Codex

**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)

986 tokens
context cost
SKILL.md, read when the skill is used
1
files
instructions only
1
copies elsewhere
how many repositories repackaged it
4 915
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/openai/plugins --skill figma-create-new-file

The instruction itself

9 sections, as written by the author

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:

  • 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.

Other skills for the same job

different authors, same section of the catalogue
Theme Factory
by anthropics
vendor ×19

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

781 tokens
Brand Guidelines
by anthropics
vendor ×16

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

558 tokens
Web Artifacts Builder
by anthropics
vendor ×10

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

771 tokens scripts
Artifacts Builder
by JayZeeDesign
×8

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

769 tokens scripts
Frontend Design
by Karanjot786
×7

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

1.1k tokens
UI Ux Pro Max
by ZhanlinCui
×5

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

3.6k tokens scripts
Frontend Design
by anthropics
vendor ×4

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

2.1k tokens
Web Performance SEO
by ZhanlinCui
×4

Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.

670 tokens

How to use it

Copy the folder

Take openai/plugins-figma-create-new-file from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.