Figma Edit

Edit Figma via MCP; GUI is last resort.

Skill metadata

Source	Bundled (installed by default)
Path	skills/creative/figma-edit
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	figma, design, mcp, creative, editor
Related skills	creative-studio, choose-interaction-surface, computer-use

Reference: full SKILL.md

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Figma Edit Skill

Adjust Figma frames/components for Creative Studio editor mode. Prefer the official Figma MCP (vibeos mcp install figma) over pixel clicks. Use computer_use only when MCP cannot complete the change.

When to Use

• User asks to inspect or tweak a Figma file/frame already shared by URL.
• Handoff from creative-studio mode editor when the target is Figma.

Do not use for greenfield logo generation (use image_generate / SVG / excalidraw first), or for purchases / team billing changes.

Prerequisites

• Figma MCP installed and OAuth completed: vibeos mcp install figma
• A Figma file or node URL from the user (link-based context)
• Destructive overwrites → human approve

How to Run

1. Confirm surface: MCP available → use Figma MCP tools; else ask user to install/connect before falling back to GUI.
2. Paste the Figma selection/file URL into the request context.
3. Read/inspect first; mutate only when the user asked for changes.
4. Export or screenshot proof into the creative workspace exports/.
5. If MCP is unavailable: choose-interaction-surface → headed Figma app via computer_use with SoM; max two retries then escalate.

Quick Reference

Step	Preferred	Fallback
Inspect	Figma MCP	Figma desktop + computer_use
Edit	Figma MCP mutate (if enabled)	Human edits / GUI playbook
Proof	export / screenshot → exports/	user confirms visually

Procedure

MCP path

1. vibeos mcp install figma (once) → OAuth in browser.
2. Restart session so tools load.
3. Provide node/file URL; call MCP read tools before write tools.
4. Summarize what changed; leave a note in qa.md.

GUI fallback

1. Open the Figma desktop/web app the user already uses.
2. computer_use capture with SoM; click by index — never blind pixels.
3. Stop before publishing/sharing publicly unless asked.
4. Web CAPTCHA / login walls → challenge-gate, not Figma clicks.

Pitfalls

• Do not invent Figma file keys or claim edits without tool confirmation.
• Team/library publish and billing are human gates.
• Vendor product stays at the MCP edge — no in-tree Figma plugin under plugins/.

Verification

• Requested frame reflects the change (MCP result or screenshot).
• exports/ has proof when the brief asks for it.
• qa.md Status is honest (pass/fail + gaps).