Exporting the recorded Figma designs

The Wisent Figma files are exported by Weles, not by a script in wisent-components. weles design export --provider figma --request <export-request.json> reads the files the request's inventory names, with the Figma token Skarbiec holds for the Weles export workload, and publishes the export into the wisent-components checkout: it replaces one directory, commits only that directory and pushes it.

Where an export goes

The request's output is that directory, relative to the checkout. Without it, the export is the package's own library, figma/. A design library measured from its own Figma file is exported into libraries/<name>/figma, which node src/cli.mjs library pull <name> --export-request FILE names itself before it measures and builds the library.

After an export

node src/cli.mjs figma variables
node src/cli.mjs figma variables --library
node src/cli.mjs vocabulary
node src/cli.mjs tokens
node src/cli.mjs build

These read the exported files' variables and the library's text styles through the Figma MCP server, merge what the files draw, bind each token to its variable or style, and write dist/. Each takes --root to work on a library's directory instead of the package's.

Refusals

The export refuses an output outside the checkout, the checkout itself or inside .git; a request, inventory, scope file or signing key inside that directory; an existing directory that holds no export inventory; ignored files inside it; a dirty checkout, another branch, or a branch that has diverged from its remote. The full contract is on Weles' fleet products page; component measurement is on measuring current Figma components.