figma-bridge-doctor
figma-bridge-doctor
Domain owner for everything Figma Desktop + Bridge. When the user mentions opening a Figma file, activating the bridge, or any bridge issue, this skill picks the right action and verifies it worked.
Script paths below are relative to this skill's directory (the folder that holds this file). The scripts live in this skill's scripts/ directory. Resolve the path before running, wherever the skill is installed.
Tool names are written as base names (figma_get_status). Your client may add a prefix: in Claude Code, with the server registered under the name figma-console, they appear as mcp__figma-console__figma_get_status. If you registered it under another name, use that name wherever this skill writes figma-console.
Platform and permissions
- The automation is macOS only. The scripts use
open,osascript,launchctl,lsof,pgrepandps. On any other OS each macOS-only script prints a short manual checklist and exits 1: follow the "Manual checklist" section with the user instead. - Accessibility permission. The plugin is launched by a menu click through System Events. The app that runs the script (Terminal, iTerm, the IDE or whatever hosts the agent) needs the Accessibility permission: System Settings > Privacy & Security > Accessibility. Without it the click fails and the script prints
osascript click failed. Granting it is a user action. - English Figma UI. The click targets the menu items by name:
Plugins>Development>Figma Desktop Bridge. If Figma runs in another language the names do not match and the click fails. Ask the user to switch Figma to English or to run the plugin by hand. - Prerequisites. Figma Desktop, the figma-console MCP server (
figma-console-mcp, by Southleft) registered in the agent, and its Desktop Bridge plugin imported once from~/.figma-console-mcp/plugin/manifest.json.
State and environment
State files live under the state dir, ${FIGMA_MAXXING_STATE_DIR:-$HOME/.config/figma-maxxing}, written <state-dir> below. The scripts create it on first run.