figma-extract
Pull a Figma file's node tree, design tokens, and embedded assets into the project cwd as a structured snapshot.
Profile →npx skills add nexu-io/open-design --skill figma-extract --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.
# 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 (`token-map`, `generate`, `critique`) operate on. ## Inputs | Source | Required | Notes | | --- | --- | --- | | Figma file URL or `node-id` | yes | Provide via the `figma-oauth` GenUI surface or `od plugin apply --input fileUrl=…` | | Figma OAuth token | yes | Routed through `oauth-prompt` with `oauth.route='connector'` and `connectorId='figma'`; the daemon never stores the token in SQLite | ## Output The atom writes a deterministic, JSON-shaped extract under the project cwd: ```text project-cwd/ ├── figma/ │ ├── tree.json # canonical node tree (id / type / parent / children / box / fills / text) │ ├── tokens.json # color + typography + spacing tokens lifted off the file │ ├── assets/ # rasterised exports of every leaf node that the file marks for export │ │ └── <node-id>.<png|svg|webp> │ └── meta.json # { fileUrl, version, lastModified, exportedAt, atomDigest } ``` `figma/tree.json` is the canonical pivot for every downstream atom. `figma/tokens.json` is the input to `token-map`. `assets/`
- Inputs
- Output
- Convergence
- Anti-patterns the prompt fragment forbids
- Status
What does the figma-extract skill do?
Pull a Figma file's node tree, design tokens, and embedded assets into the project cwd as a structured snapshot.
How do I install it?
Run `npx skills add nexu-io/open-design --skill figma-extract --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.