agentleFS
Sign inStart free
ulises-jeremiasulises-jeremias/agent-toolkit/skills/design/figma-create-new-file/SKILL.md

figma-create-new-file

Skill19 starsChanged 2 months agoMITView on GitHub

Create a new blank Figma file. Use when the user wants to create a new Figma design or FigJam

We split this skill into the rules it gives an agent

7 rules. 0 are common, 0 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the create_new_file MCP tool to create a new blank Figma file in the user's drafts folder.

    line 11
  2. Very specific:

    Single plan: use its key field automatically.

    line 37
  3. Very specific:

    Multiple plans: ask the user which team or organization they want to create the file in, then use the corresponding plan's key.

    line 38
  4. Very specific:

    Call the create_new_file tool with:

    line 42
  5. Very specific:

    Use the file_key for subsequent tool calls like use_figma.

    line 65
  6. Very specific:

    Only "design" and "figjam" editor types are supported.

    line 70
  7. Very specific:

    If use_figma is your next step, install and load the opt-in figma-use pack first (see docs/SKILLS.md).

    line 71

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

create_new_file — Create a New Figma File

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) or figjam
  • 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"

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:

ParameterRequiredDescription
planKeyYesThe plan key from Step 1
fileNameYesName for the new file
editorTypeYes"design" or "figjam"

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.
  • Only "design" and "figjam" editor types are supported.
  • If use_figma is your next step, install and load the opt-in figma-use pack first (see docs/SKILLS.md).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free