Figma extract Spec §10 / §21.3.1: the figma-migration scenario starts with a Figma file URL + an OAuth token. This atom turns that pair into the authoritative on-disk record subsequent stages ( , , ) operate on. Inputs | Source | Required | Notes | | --- | --- | --- | | Figma file URL or | yes | Provide via the GenUI surface or | | Figma OAuth token | yes | Routed through with and ; the daemon never stores the token in SQLite | Output The atom writes a deterministic, JSON-shaped extract under the project cwd: is the canonical pivot for every downstream atom. is the input to . is the input to…