fieldnote-ops/frameevidence

Name: fieldnote-ops/frameevidence
Author: fieldnote-ops

Plugin插件 Native原生 ⭐ 2 MIT Dev Workflow开发与代码工作流

独立、受约束的Figma REST证据插件，用于DeepSeek Harness：只读节点检查与临时渲染URL。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

FrameEvidence is a native plugin built specifically for DeepSeek Harness that enables the DSH agent to pull read-only design data from Figma before writing any code. It connects directly to Figma’s public REST API to get details like layout, typography, colors, component references, and variable bindings from a design file. It is deliberately designed to be fully read-only, with no ability to write changes back to Figma. Version 0.1 of the plugin ships two core tools: figma_inspect which returns a bounded, trimmed node tree that avoids dumping full Figma JSON into the agent’s context, and figma_render which returns a temporary URL for a rendered asset of the requested node.

To use FrameEvidence, you first need to generate a Figma Personal Access Token (PAT) with only the file_content:read scope, and store it as an environment variable on your local machine. You then install the plugin via the DSH CLI using the command dsh plugin --profile web add github:fieldnote-ops/frameevidence#<commit-hash>, where you should pin a reviewed commit for production use. Once installed, you can pass your DSH agent a link to a Figma file or node your PAT has access to, and ask the agent to inspect the design before starting implementation. This plugin is ideal for developers working on design-to-code workflows that need to pull structured design data from Figma for AI agents.

FrameEvidence enforces strict security boundaries to keep your Figma PAT safe. The token is only read from the host environment, it is never accepted as a tool argument from the model, and it is never returned in any tool output. All requests are sent only to Figma’s official v1 REST API, and redirects are blocked to prevent unintended requests. The current version has some limitations: it does not fetch values for Figma Enterprise variables, only preserves their binding IDs, and it is subject to Figma’s rate limits based on your plan. The project is released under the open-source MIT license, with no third-party maintainer servers, analytics, or telemetry.

FrameEvidence 是专为 DeepSeek Harness 打造的原生插件，作用是让 DSH 代理在编写代码前，通过 Figma REST API 读取设计信息，获取布局、排版、颜色、组件引用和变量绑定等设计证据。插件当前提供两个工具：figma_inspect 返回精简后的节点树，避免全量 JSON 占用过多上下文，figma_render 获取指定节点的临时渲染地址。

使用者需要先在 Figma 创建仅拥有 file_content:read 权限的个人访问令牌（PAT），再将令牌安全存入主机环境变量，之后通过 DSH 官方命令行安装该插件到 Web 配置文件。给 DSH 代理传入可访问的 Figma 文件或节点链接，即可让代理先审查设计再编写代码，适合开发设计转码工作流的开发者使用。

该插件遵循严格的安全边界，令牌仅从环境变量读取，不会被模型作为参数传入或输出，所有请求仅访问 Figma 官方 API 且全程只读，不向 Figma 写入任何内容。当前限制包括仅保留 Figma 企业版变量绑定 ID 不获取变量值，受 Figma 账户速率限制影响，项目采用 MIT 许可证开源，无维护者运营服务器、用户分析或遥测服务。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：frameevidence（fieldnote-ops/frameevidence）
仓库：https://github.com/fieldnote-ops/frameevidence
本站详情页：https://www.yhbd.top/plugins/fieldnote-ops-frameevidence/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-08-15 · 主语言 JavaScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

Only 2 stars - very few users, little community feedback星标只有 2，几乎没人在用，遇到问题缺少社区反馈

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

dsh plugin --profile web add github:fieldnote-ops/frameevidence#97f67c9a049a26c9e8b38e7e764d2572897a6429

把 fieldnote-ops/frameevidence 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

6.1 KB · 缓存于 2026-09-01 05:12:23 · 6.1 KB

FrameEvidence

Bounded, read-only design evidence for agent harnesses. FrameEvidence lets an agent inspect layout, typography, paints, component references, and variable bindings through the Figma REST API before it writes code. Version 0.1 is packaged as a plugin for DeepSeek Harness.

FrameEvidence is deliberately read-only. Version 0.1 provides two tools:

figma_inspect returns a bounded, implementation-focused node tree instead of dumping Figma's full JSON schema into the model context.
figma_render returns a temporary PNG, JPG, SVG, or PDF render URL for one node.

Evidence at a glance

Surface	Current boundary
Figma access	Read-only REST requests to `https://api.figma.com/v1`; redirects are rejected and no tool writes to Figma.
Credential handling	The PAT is read from a named host environment variable, never accepted as a model tool argument, and never returned in tool or probe output.
Context control	Raw responses are byte-capped; depth and returned node count are bounded before design evidence reaches the model.
Maintainer infrastructure	No maintainer server, analytics, telemetry, OAuth broker, or credential store is involved.
Verified today	15 credential-free tests and clean-profile DSH rc.6/`latest`/`next` consumers pass. A real Figma file has not yet completed the opt-in probe.

Install

Install the repository into the Web profile:

dsh plugin --profile web add github:fieldnote-ops/frameevidence#97f67c9a049a26c9e8b38e7e764d2572897a6429

The full commit above is the last publicly verified runtime revision. Inspect main for ongoing development, but pin a reviewed commit when a real design token is in scope.

Create a Figma personal access token under Settings → Security → Personal access tokens with only the file_content:read scope. Figma PATs expire after at most 90 days, so choose the shortest useful lifetime and revoke the token after the probe if it is no longer needed. Read the token interactively so it does not enter shell history:

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 fieldnote-ops/frameevidence 的 README.md。在 GitHub 查看原文 →