od-figma-migration
Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
Profile →npx skills add nexu-io/open-design --skill od-figma-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Default pipeline
- Required GenUI surfaces
What does the od-figma-migration skill do?
Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
How do I install it?
Run `npx skills add nexu-io/open-design --skill od-figma-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.