Agent skill · software engineering · nexu-io
od-figma-migration
Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
Why this skill is useful
Provides a detailed pipeline for Figma migration that includes specific stages and their interactions, which the AI wouldn't reliably generate on its own.
What it needs
Requires figma account access. About 1k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
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 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).
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/od-figma-migration