dotgui for Figma · plugin Coming soon
Export any Figma screen as a .gui file
The dotgui Figma plugin will export any layer:a frame, component, group, or single shape:as a .gui file, with high-fidelity coverage (~95%) of Figma's layer model: auto-layout, fills, gradients, effects, and tokens preserved, with documented limitations (gradient strokes, some effect types, heavily overridden instances). The plugin is in review with the Figma Community and not yet available:until it ships, an AI agent can already write .gui files directly from a prompt, no design tool required.
How it works
Select, export, done.
| Step | What happens |
|---|---|
01 | Install the dotgui plugin from the Figma Community (coming soon — the plugin is in review). |
02 | Select any visible layer:frames, components, groups, or individual shapes. |
03 | Export. Small selections produce inline .gui XML; larger ones download as a packaged .gui with an assets/ folder. |
04 | Render it with the kit, embed it on a page, or hand it to your agent as structured context. |
The plugin handles the whole translation: token extraction, font mapping, image encoding, and gradient computation. What was pixels locked in a design tool becomes a portable text file your whole toolchain can read.
Why it matters
Your designs, out of the walled garden.
Figma's native format is a proprietary API:not something you can paste into a prompt, check into a repo, or open in another tool. Exporting to .gui turns a screen into an open artifact: an AI agent can read the exact layout, text, colors, and spacing without screenshots or visual reasoning, and any renderer can draw it.
Roadmap
Round-trip is the goal.
Export ships first, once the plugin clears review. The round-trip:gui pull <figma-url> and gui push home.gui <figma-url> from the CLI:is on the roadmap, closing the loop: design in Figma, iterate with your agent, push back to Figma without losing fidelity.
Frequently asked
Which Figma layers can I export to .gui?
Any visible layer: full frames, components, groups, or even a single shape. The plugin walks the selection and translates the complete subtree.
How accurate is the export?
The plugin provides ~95% fidelity of Figma's layer model. Auto-layout becomes .gui stacks, and fills, gradients, effects, corner radii, and design tokens carry over. Known limitations: gradient strokes are not emitted (solid strokes work), some effect types are documented in comments, and instances with ≥75% overrides are detached to inline trees.
Where do images and other assets go?
Small exports inline everything into a single .gui XML file. Larger exports download as a packaged .gui:a zip with the markup plus an assets/ folder holding the images.
Can I import a .gui file back into Figma?
Not yet. The plugin is in review with the Figma Community; export ships first once it is live, and the pull/push round-trip via the CLI is on the roadmap.