Figma plugins

Design files are where work is decided and almost never where it ends up. Most of these plugins exist because I hit the same wall twice in a week and it was cheaper to write the bridge than to keep crossing the gap by hand.

The set

• Async Design — reads a frame and generates components and styles from it, including a Tailwind parser so class strings in the design map onto real tokens rather than being retyped by whoever picks up the ticket.
• Styles & Variables Fetcher — pulls a file’s styles and variables out over a backend, so a style guide can be generated from the source of truth instead of maintained beside it.
• Design System AI — generates a system’s foundations from an existing file.
• Shadcn Code Generator — emits shadcn-flavoured component code from selection.
• V3 Code to AI — packages a selection’s structure into something a model can reason about without being handed a screenshot and asked to guess.
• HTML to Design — the other direction: an existing page structure brought back into Figma as editable layers.
• CMYK Export — colour-converted export for anything heading to print, because a screen palette that was never checked in CMYK is a surprise waiting at the printer.
• Section PDF Exporter and Figma to Canva — section-by-section PDF, and a PPTX export path for teams whose actual deliverable is a deck in Canva.

What they have in common

Each one is small, does a single conversion, and treats the design file as data. That’s the useful frame: once a Figma document is queryable structure rather than a picture, the question stops being “how do I rebuild this” and becomes “what do I want out of it.”