DeepSeek Harness 插件

frameevidence

Bounded, read-only design evidence for DeepSeek Harness agents, compatible with the Figma REST API.(英文原文)

跳到安装方式

来源信息

GitHub 仓库
fieldnote-ops/frameevidence
最近更新
2026年8月15日
分类
文档与渲染
GitHub stars
1
载体类型
bundle
目录证据
上游声明已找到 dsh.bundle
证据路径
package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/fieldnote-ops/frameevidence
插件名:frameevidence
作者:fieldnote-ops

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器3 个文件
README.md来源说明 · 只读预览

FrameEvidence

![Self-test](https://github.com/fieldnote-ops/frameevidence/actions/workflows/self-test.yml)

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

SurfaceCurrent boundary
Figma accessRead-only REST requests to https://api.figma.com/v1; redirects are rejected and no tool writes to Figma.
Credential handlingThe 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 controlRaw responses are byte-capped; depth and returned node count are bounded before design evidence reaches the model.
Maintainer infrastructureNo maintainer server, analytics, telemetry, OAuth broker, or credential store is involved.
Verified today15 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:

printf 'Figma PAT: '
IFS= read -r -s FIGMA_ACCESS_TOKEN
printf '\n'
export FIGMA_ACCESS_TOKEN
npx @deepseek-ai/dsh web

Then give the agent a Figma file or node URL that the token-owning account can access and ask it to inspect the design before implementation. See Figma's official PAT instructions and scope reference.

Opt-in live API probe

To close the real-API evidence gap without sending data to a maintainer, clone this repository and run npm ci --ignore-scripts --registry=https://registry.npmjs.org. Inject the PAT and a caller-selected node URL through the process environment without putting either value in a command or committed file:

printf 'Figma PAT: '
IFS= read -r -s FIGMA_ACCESS_TOKEN
printf '\nFigma node URL: '
IFS= read -r FRAMEEVIDENCE_URL
export FIGMA_ACCESS_TOKEN FRAMEEVIDENCE_URL
npm run live:smoke
unset FIGMA_ACCESS_TOKEN FRAMEEVIDENCE_URL

The probe is never automatic. It executes both figma_inspect and figma_render, then creates a new 0600 frameevidence-live-smoke.json. It refuses to overwrite prior evidence and records no token, design URL, file key, node id, node name, raw API response, or temporary render URL.

Security and data boundary

  • The token is read only from the host environment. It is never accepted as a model tool argument and is never returned in output.
  • Requests go only to https://api.figma.com/v1 and redirects are rejected.
  • The plugin is read-only and requests only Figma file/node JSON or rendered assets.
  • Responses have a byte cap, node trees have a node cap, and successful reads are cached in memory to reduce rate-limit pressure.
  • Figma render URLs are temporary and should not be treated as durable storage.
  • The project has no maintainer-operated server, analytics, or telemetry. See [PRIVACY.md](./PRIVACY.md) and [SECURITY.md](./SECURITY.md).

Figma plan limitations

Figma's REST rate limits depend on seat and plan. Viewer/Collab seats can have very low Tier 1 quotas; Dev/Full seats receive per-minute quotas. The Variables REST API is Enterprise-only, so v0.1 preserves bound variable ids but does not fetch variable values.

Configuration

KeyDefaultMeaning
tokenEnvFIGMA_ACCESS_TOKENHost environment variable containing the PAT
defaultDepth4Default Figma subtree depth
maxDepth8Maximum model-requestable depth
maxNodes300Maximum nodes returned to the model
timeoutMs30000HTTP timeout
maxResponseBytes8388608Raw API response cap
cacheTtlMs300000In-memory GET cache duration

Development

npm install
npm run check

Non-goals for v0.1

  • Writing to Figma
  • OAuth or multi-user token storage
  • Full design-to-code generation
  • Claiming pixel-perfect implementation without browser comparison
  • Fetching Enterprise Variables values

MIT licensed.

Project status

FIELD NOTE built FrameEvidence as an AI-assisted, human-reviewed interoperability experiment. Unit tests use synthetic Figma API responses, and the release workflow uses HarnessProof to install the plugin's locked dependencies in an isolated copy before checking clean-profile composition and Web boot across DSH rc.6, latest, and experimental next, all without a Figma credential. An opt-in, credential-safe live probe is available but has not yet been executed against a real Figma file; Marketplace acceptance also remains unverified. There is no independent-user adoption, purchase validation, or income yet.

FrameEvidence is an independent open-source project. It is not affiliated with, sponsored by, or endorsed by Figma, Inc. or DeepSeek. Figma and DeepSeek names are used only to identify compatibility with their respective products and services.