r/FigmaAddOns

Hey everyone,

I keep seeing the same deck workflow in design teams:
The actual design happens in Figma, because that’s where layout, spacing,typography, and visual polish are easiest to control. But the final deck still needs to be in Google Slides because clients, PMs, sales, investors, or internal teams need to comment, edit, and present from there.

The annoying part is that the handoff usually destroys the rhythm. Exporting images makes the deck hard to edit. Rebuilding in Slides is slow. And small layout differences stack up fast.

So I built a Figma plugin called DeckSync.The goal is not just “send something to Google Slides.” I wanted the imported deck to keep the original Figma layout as closely as possible, close to pixel-level fidelity, so there is basically no cleanup after export.

Current workflow:

- Select Figma frames / Figma Slides / sections / components
- Create a Google Slides deck directly from the selection
- Preserve layout, positioning, typography, images, and slide structure as closely as possible
- Keep speaker notes when available
- Re-sync later changes back to the managed Google Slides deck
- Import local .pptx files into Google Slides too

What I personally care about most is the “zero cleanup” part. If I still have to spend 30 minutes fixing spacing, text boxes, and image positions after export, the plugin hasn’t really solved the problem.

Plugin link: https://www.figma.com/community/plugin/1629139683176758901/decksync-create-sync-google-slides-from-figma

I’m curious how other designers handle this right now.

When you need to move a polished Figma deck into Google Slides, do you export flat images, rebuild manually, use PDF, or just force everyone to review in Figma? What usually breaks for you: fonts, text wrapping, spacing, images, or editability?

Today I’m launching Designry on Product Hunt 🎉

Over the last few months, I’ve been building a browser-based design system tool focused on one thing:

Making design systems faster and easier to create.

Because honestly:
setting up tokens, variables, typography, exports, and documentation manually still takes way too much time.

With Designry, you can start with a single brand color and generate:

• OKLCH color palettes
• Typography & spacing tokens
• Figma Variables export
• Tailwind export
• Full component documentation

—all directly in the browser.

No Figma plugin. No installation. Free to start.

Would genuinely love your feedback and support 👇

Product Hunt → https://www.producthunt.com/products/designry?launch=designry
Live Demo → getdesignry.com

#designsystem #designtokens #buildinpublic #figma

Hey all 👋

After a lot of feedback on my previous icon workflow post, I kept iterating on the idea.

What started as:
scan → organize → export
is slowly turning into something closer to a reusable icon system inside Figma.

Some of the recent improvements:
• Favorites now sync locally across Figma projects
• Smarter icon naming and organization
• Better handling for large icon sets
• Reusable icon libraries via import/export
• Cleaner, ready-to-use outputs
• Keeping the whole flow inside Figma without jumping between tools

The interesting challenge stopped being “exporting icons” and became more about:
consistency, reuse, and keeping things manageable at scale.

Curious:
How are you currently managing icon systems across projects?

What does your icon workflow usually rely on today?
libraries manual?
organization inside Figma?
or custom workflows?

Trying to drive your development efforts using AI? but AI not able to read your tokens?
Here's my 5 step framework to make your DS AI readable.

AI has prerequisites:
1/ Components has to be Token connected. Do Token Audit using FigSpecs to find the gap.
2/ Provide Context & Intent to AI tools like Claude. Figspecs - A figma plugin helps you to generate it in seconds by generating rules.md & tailwind file.
3/ Upload files into Claude or any AI tool
4/ Share designs via MCP
5/ AI will build solutions that are connected to your tokens.

Try it & let me know if you need any assistance.
Reshare & support.

I built FigSpecs out of challenges experienced.

I kept watching the same thing happen, design approved, engineer picks up the ticket, opens Figma, clicks through 40 layers trying to find padding values and token names. Meanwhile the AI agent they're using is guessing layout from a screenshot.

The problem isn't the model. It's that there's no machine-readable file bridging design and code.

FigSpecs fixes that. Select any Figma component and it generates:

→ Detailed Token audit that identifies layers not connected to variables

→ Anatomy diagrams with numbered callouts

→ Accessibility audit (WCAG-aligned, Voiceover, Talkback)

→ component.rules.md: full structural hierarchy, token paths, flex direction, alignment, your Cursor/Claude Code agent reads it directly.

→ Tailwind v4 block CSS custom properties, correct namespaces, pixel values

→ specs.json for token pipelines and CI validation

→ 1-click Jira ticket with everything attached

If you are a Designer, Design system Manager, Product manager, Developer or Architect, this product is for you.

Try for free: https://www.figma.com/community/plugin/1612756059828219731

You can:
• Turn your Figma prototypes into Lottie animations
• Edit timing & easing for the entire flow inside the plugin
• Use the compressor for production-ready files

Export and compress Lottie in one workflow:
https://figma.com/community/plugin/1630333167443650772

Would love to hear your feedback ✌️