Search and summarize material from the Acme research service.
日本語の概要は準備中です。原文の説明を表示しています。
**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)
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
This skill accepts optional arguments: /figma-create-new-file [editorType] [fileName]
design (default), figjam, or slidesExamples:
/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".
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.
key field automatically.key.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"
}
The tool returns:
file_key — the key of the newly created filefile_url — a direct URL to open the file in FigmaUse the file_key for subsequent tool calls like use_figma.
"design", "figjam", and "slides".use_figma is your next step, load the figma-use skill before calling it.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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Search and summarize material from the Acme research service.
日本語の概要は準備中です。原文の説明を表示しています。
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
日本語の概要は準備中です。原文の説明を表示しています。
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
日本語の概要は準備中です。原文の説明を表示しています。
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
日本語の概要は準備中です。原文の説明を表示しています。
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
日本語の概要は準備中です。原文の説明を表示しています。