Skip to content
Back to skills

Connect

ASecurity

Connect this session to Figma and keep it listening for requests from the Layerwright window, so the user can send work from Figma and this session starts on it by itself. Use for /layer:connect, or when the user asks to connect, link or pair this session with Figma.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
ai-agents

Works with

  • claude code

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add shayan-m81/layerwright --skill connect --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Connect?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Connect
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/shayan-m81-connect/badge)](https://www.skillsdirectory.com/skills/shayan-m81-connect)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: connect
description: Connect this session to Figma and keep it listening for requests from the Layerwright window, so the user can send work from Figma and this session starts on it by itself. Use for /layer:connect, or when the user asks to connect, link or pair this session with Figma.
---

# Connect to Figma

1. `figma_status({ title, listen: true })`: the title is the task in 2–4 words ("Figma connection" if there is none yet).
2. It returns `doFirst`: call that tool with exactly those arguments (step 4 tells the user this session now listens), unless a Monitor with the description "Requests from the Layerwright window in Figma" already runs in this session (a second one exits at once anyway). Whenever it expires, start it again. No `doFirst` (not Claude Code) → requests arrive with the next Figma step, or with `/layer:inbox`.
3. Not connected: say so in one line and how to open it: Figma desktop → Plugins → Development → Layerwright (never imported: `npx layerwright init`, then Import plugin from manifest → `~/.layerwright/figma-plugin/manifest.json`). The watcher keeps running, so the session still wakes up when the window opens and the user sends something. Still nothing after that → `/layer:doctor`.
4. Connected: one or two lines, in the user's language (`language` from figma_status, if it returns one): the file and page, what is selected, how many sessions share Figma, and that this session now listens. In the Layerwright window they select layers, pick this session ("<the title>") and send a request or their own words; it starts here by itself, and the answer appears in the window.
5. When a request arrives (the Monitor reports it), do it as `/layer:inbox` says: `figma_inbox`, `figma_reply` working, do it, `figma_reply` done with one line.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…