菜单
Export Figma frames as PNG images via Figma REST API. Use when you need to get a design screenshot from a Figma URL for visual comparison.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the conversation surfaces knowledge that code, types, tests, or git history can't reveal — the user explains a business rule or a spec, shares a gotcha, gives the why behind a decision, says "that's intentional, not a bug", or you hit a pitfall or dig up a non-obvious root cause while debugging. Record it into docs/lore/ before the session ends and it evaporates.
Use when asked whether the project's lore is healthy or still helping, or when the 30-day heartbeat suggests a re-check — audits coverage, link health, freshness, entry quality, adoption, and language health, read-only, then hands fixes off to lore-maintain, lore-capture, and lore-ul.
Use when about to plan a feature, fix a bug, or touch unfamiliar code in a repo that has a docs/lore/ folder, before writing any implementation — surfaces the business rules, pitfalls, glossary terms, and API map relevant to the task, and flags entries that look stale.
Use when about to commit, open a PR, or claim a change is done in a repo that has docs/lore/ — maps the changed files to lore entries through their code: links and reports any business rule, pitfall, or glossary naming rule the change violates. Read-only for both code and lore.
Use when a project has no docs/lore/ yet and implicit knowledge starts coming up in conversation, or when the user asks to initialize, bootstrap, or set up project lore — scaffolds the docs/lore/ knowledge base.
Use when lore looks stale or noisy, when a lore-check report flags problems, or on a periodic sweep — finds stale, duplicate, or wrong entries, checks that code links and the README index still hold, and prunes obsolete content; marking over deleting, with confirmation for destructive actions.
| name | figma-export |
| description | Export Figma frames as PNG images via Figma REST API. Use when you need to get a design screenshot from a Figma URL for visual comparison. |
從 Figma URL 導出指定 frame 的 PNG 截圖。
FIGMA_ACCESS_TOKEN：環境變數，或放在專案根的 .env（腳本會自己讀）python "${CLAUDE_PLUGIN_ROOT}/scripts/figma-export.py" "<figma_url>" --output design.png [--scale 1] [--node-id <id>]
腳本在 plugin 目錄裡，不在使用者專案裡——路徑一定要用 ${CLAUDE_PLUGIN_ROOT}，寫相對路徑會找不到檔案。
| 參數 | 必填 | 說明 |
|---|---|---|
figma_url | 是 | Figma 檔案或 frame 的 URL |
--output | 否 | 輸出檔名（預設 figma-export.png） |
--scale | 否 | 縮放倍數（預設 1）。要跟網頁截圖的 device pixel ratio 一致，不然像素比對會滿版假差異 |
--node-id | 否 | 指定 node ID（從 URL 的 node-id= 參數取得） |
支援以下格式：
https://www.figma.com/file/XXXXX/FileName?node-id=1-2https://www.figma.com/design/XXXXX/FileName?node-id=1-2如果沒有 Figma Token：