od-figma-migration
Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
来源信息
- 仓库
- nexu-io/open-design
- 最近来源活动
- 2026年8月18日 07:09
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 96,674
- 分支
- 11,234
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
3 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- od-figma-migration
- description
- Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
- od
- {"scenario":"figma-migration","mode":"scenario"}
# od-figma-migration (scenario)
Spec §1 / §10.1 / §21.3.1 / §23.3.3: the canonical figma-migration
flow. The pipeline is sequenced so each stage's output is the next
stage's input — `figma-extract` writes `figma/tree.json`,
`token-map` writes `token-map/colors.json` (etc.), and `generate`
reads both before producing the HTML artifact.
## Default pipeline
```jsonc
{
"stages": [
{ "id": "extract", "atoms": ["figma-extract"] },
{ "id": "tokens", "atoms": ["token-map"] },
{ "id": "generate", "atoms": ["file-write", "live-artifact"] },
{
"id": "critique", "atoms": ["critique-theater"],
"repeat": true,
"until": "critique.score>=4 || iterations>=3"
}
]
}
```
## Required GenUI surfaces
The scenario expects two `oauth-prompt` / `form` surfaces from the
plugin layer:
- `figma-oauth` — `oauth.route='connector'`, `connectorId='figma'`,
persists at the project tier so multi-conversation work doesn't
re-prompt.
- `file-pick` — `kind='form'`, captures the Figma file URL on the
first turn so `figma-extract` knows where to read.
The daemon auto-derives the `figma-oauth` surface when
`od.connectors.required[].id='figma'` is declared and the connector
isn't yet authorised (spec §10.3.1 implicit oauth-prompt rule).
在 GitHub 查看