Find out why Layerwright can't reach Figma (plugin not connected, wrong port, old plugin window, another server on the port) and fix it with the user. Use for /layer:doctor or when figma_* tools fail with PLUGIN_DISCONNECTED or TIMEOUT.
5 stars
0 votes
0 copies
0 views
Added October 6, 2026
ai-agents
Security analysis
A100/100
Scanned October 6, 2026
$npx -y skills add shayan-m81/layerwright --skill doctor --agent claude-code
Installs into .claude/skills of the current project.
Are you the author of Doctor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/shayan-m81-doctor)
---
name: doctor
description: Find out why Layerwright can't reach Figma (plugin not connected, wrong port, old plugin window, another server on the port) and fix it with the user. Use for /layer:doctor or when figma_* tools fail with PLUGIN_DISCONNECTED or TIMEOUT.
disable-model-invocation: true
---
# Connection doctor
1. `figma_status`. Connected → say so (file, page, sessions) and stop.
2. Run `npx layerwright doctor` in the project and read it top to bottom; each ✗ line has its fix.
3. The usual causes: the plugin window isn't open (Figma desktop → Plugins → Development → Layerwright); the plugin was never imported (`npx layerwright init`, then import `~/.layerwright/figma-plugin/manifest.json`); an old plugin window (close and reopen it); the browser version of Figma (it must be the desktop app); a different port (`LAYERWRIGHT_PORT`).
4. After a fix, `figma_status` again and confirm.
