omp-figma-remote-auth 0.1.5 → 0.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -0
- package/README.zh-CN.md +18 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -47,6 +47,24 @@ The server name is `figma`. Once connected, give OMP a Figma file or node URL yo
|
|
|
47
47
|
|
|
48
48
|
The package also includes the on-demand `figma-mcp` skill. When you provide a Figma file or node link, it guides OMP through parsing the node reference and discovering the Figma MCP tools, including tools mounted under `xd://`.
|
|
49
49
|
|
|
50
|
+
### Figma skill routing limitation
|
|
51
|
+
|
|
52
|
+
The bundled `figma-mcp` skill is an OMP skill, not a copy of Figma's official workflow skill. Its purpose is to recognize Figma tasks, parse file/node references, select the right MCP tool, and guide tool discovery under `xd://`. It cannot rewrite the Figma MCP server's tool descriptions or intercept a `read` request already emitted by the model.
|
|
53
|
+
|
|
54
|
+
Figma's `get_design_context` guidance currently asks clients to read:
|
|
55
|
+
|
|
56
|
+
```text
|
|
57
|
+
skill://figma/figma-design-to-code/SKILL.md
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
In OMP, `skill://` is the local skill namespace. If the model follows that instruction literally, OMP can return `Unknown skill: figma` before the model reaches the plugin guidance. In the verified OMP 18.1.18 environment, the Figma MCP resource can instead be read with OMP's MCP-specific wrapper:
|
|
61
|
+
|
|
62
|
+
```text
|
|
63
|
+
read mcp://skill://figma/figma-design-to-code/SKILL.md
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
This workaround requires the Figma MCP server to be connected and to advertise that resource; `mcp://skill://...` is OMP-specific, not a general MCP URI syntax. A model may still first try the bare `skill://` path because the Figma tool description uses mandatory wording. Metadata queries that do not require this workflow resource may still work, but a `get_design_context` design-to-code request can fail or return incomplete results if the prerequisite resource is not loaded.
|
|
67
|
+
|
|
50
68
|
## Commands
|
|
51
69
|
|
|
52
70
|
These commands run **inside OMP's TUI**, not in your terminal.
|
package/README.zh-CN.md
CHANGED
|
@@ -47,6 +47,24 @@ omp
|
|
|
47
47
|
|
|
48
48
|
插件还内置按需加载的 `figma-mcp` skill。提供 Figma 文件或节点链接后，它会引导 OMP 解析节点参数并发现 Figma MCP 工具，包括挂载在 `xd://` 下的工具。
|
|
49
49
|
|
|
50
|
+
### Figma skill 路由限制
|
|
51
|
+
|
|
52
|
+
包内的 `figma-mcp` 是 OMP skill，不是 Figma 官方 workflow skill 的复制品。它的作用是识别 Figma 任务、解析文件/节点引用、选择合适的 MCP 工具，并引导模型发现挂载在 `xd://` 下的工具。它不能改写 Figma MCP 服务端的工具描述，也不能拦截模型已经发出的 `read` 请求。
|
|
53
|
+
|
|
54
|
+
Figma 的 `get_design_context` 指引目前要求客户端读取：
|
|
55
|
+
|
|
56
|
+
```text
|
|
57
|
+
skill://figma/figma-design-to-code/SKILL.md
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
但在 OMP 中，`skill://` 是本地 skill 命名空间。模型若严格执行这条指引，OMP 可能先返回 `Unknown skill: figma`，之后才有机会根据插件 skill 修正。在已验证的 OMP 18.1.18 环境中，Figma MCP 资源可以通过 OMP 专用 wrapper 读取：
|
|
61
|
+
|
|
62
|
+
```text
|
|
63
|
+
read mcp://skill://figma/figma-design-to-code/SKILL.md
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
该 workaround 要求 Figma MCP 已连接并广告对应资源；`mcp://skill://...` 是 OMP 专用路径，不是通用 MCP URI 语法。由于 Figma 工具描述使用强制性措辞，模型仍可能先尝试裸 `skill://` 路径。不依赖该 workflow 资源的 metadata 查询可能仍能完成，但如果前置资源未成功读取，`get_design_context` 设计转代码请求可能失败或结果不完整。
|
|
67
|
+
|
|
50
68
|
## 常用命令
|
|
51
69
|
|
|
52
70
|
以下均在 **OMP TUI** 中执行，不是终端命令。
|