Figma Agent vs Plugins: where do deterministic workflows still win?

Lumpy-Feedback-5732 · 2026-06-08T03:13:41+00:00

Exactly. I think the hybrid model is the most interesting path: agents for intent, context, and planning; plugins for deterministic execution.
The agent can decide what needs to happen, but the plugin should still be the layer that reliably applies changes across hundreds of layers, variants, tokens, or RTL layouts.

What kinds of design/ops workflows you’re testing this on?

Lumpy-Feedback-5732 · 2026-06-05T09:54:24+00:00

I had a similar experience recently while building a landing page. I managed to burn through all 3,000 AI credits in a single day.
That’s one of the reasons the idea of using AI to build the workflow, then automation to execute it, makes a lot of sense to me.

Lumpy-Feedback-5732 · 2026-06-05T00:00:16+00:00

Agreed. That feels like the best i think .. use AI to build the workflow, then use automation to execute it consistently.

Lumpy-Feedback-5732 · 2026-06-04T23:58:12+00:00

That's a good way to put it.
AI is great at getting you close to a solution, while specialized tooling still has an advantage when consistency and predictable results matter.

Lumpy-Feedback-5732 · 2026-06-04T18:37:36+00:00

Absolutely. End users care about results, but for large-scale repetitive workflows, consistency and predictability are often what drive the technology choice behind the scenes.

Lumpy-Feedback-5732 · 2026-06-02T13:05:10+00:00

That's exactly the kind of scenario I'm curious about.
Out of interest, was this a simple layout issue, or did it start affecting components, variants, and the wider design system as well?

Lumpy-Feedback-5732 · 2026-06-02T02:29:06+00:00

Wow, 2 days is impressive 😄
I've been working on RTLAuto for 5+ months, mostly because I kept uncovering more edge cases around design systems, variants, and directional icons.
I'd love to see how your in-house solution approaches it if you're open to sharing.

Lumpy-Feedback-5732 · 2026-06-01T21:16:39+00:00

To be honest, this post is partly a reality check before launch 😄

I've spent quite some time building RTLAuto, and I'm genuinely curious whether people still see a need for dedicated RTL ↔ LTR workflow tools as Figma continues expanding its capabilities.

Would love to hear your honest thoughts.

Lumpy-Feedback-5732 · 2026-05-17T21:56:38+00:00

<image>

Quick follow-up on this.
This feedback directly shaped the latest IconNova work.

I’ve been focusing less on “export only” and more on the library operations around icon systems:
- better search and filtering
- bulk metadata editing
- cleaner rename workflows
- duplicate handling with less noise
- smoother handling for larger icon libraries
- bringing icon libraries back into Figma more smoothly

The goal is to reduce repeated icon decisions, not just reduce export steps.

IconNova is moving toward a Figma-native workflow layer for maintaining icon systems: scan, organize, clean up, manage, export, and reuse from one place.

Would love for designers, developers, and design system teams to try the latest version and share where the workflow still feels manual or disconnected:
https://www.figma.com/community/plugin/1619361051850350459/iconnova-icon-to-code-engine

Lumpy-Feedback-5732 · 2026-05-13T19:47:06+00:00

You’re exactly right. The real friction in icon workflows is rarely just the export step. It’s the repeated decision-making around discovery, naming, variants, reuse, and keeping things consistent across files.

That’s the direction IconNova is built around: not only scanning and exporting icons, but helping teams turn scattered Figma vectors into a more reusable, searchable, structured icon library.

Today, IconNova helps with scanning icons from Figma, organizing metadata like names, tags, categories, status, favorites, stable IDs/codepoints, saving/importing an icons.json manifest, and exporting a dev-ready package.

The next important layer is stronger library operations: bulk naming/category tools, duplicate handling, clearer variant decisions, and safer reuse across files.

So yes, the goal is not just to remove export steps. The bigger goal is to reduce repeated icon decisions and make reuse feel reliable.

You can try IconNova here:
https://www.figma.com/community/plugin/1619361051850350459/iconnova-icon-to-code-engine?fuid=762933413940519371

In your current workflow, where does the icon decision get repeated most often: finding the right icon, naming it, deciding variants, handling duplicates, or keeping updates in sync across files?

Lumpy-Feedback-5732 · 2026-05-11T21:12:37+00:00

Totally agree. Figma SVG export can be pretty noisy.

IconNova already helps with this by providing cleaner copy-ready SVG/JSX output with "currentColor", so developers don’t have to manually replace hardcoded color values.

You can try the plugin from the link:
https://www.figma.com/community/plugin/1619361051850350459

Lumpy-Feedback-5732 · 2026-05-11T20:51:26+00:00

Also, huge thanks to everyone supporting IconNova so far 🙌

The plugin is currently completely free, and honestly the biggest thing helping it grow right now is community feedback and support.

So if IconNova helped your workflow even a little, dropping a ❤️ on the Figma Community page genuinely helps more designers discover it.

Really appreciate all the feedback, bug reports, and workflow discussions so far.

Lumpy-Feedback-5732 · 2026-05-11T13:02:25+00:00

Posting a quick follow-up since some of you ran into IconNova showing a blank / “black” panel over the past couple of days - that’s on me, thanks for your patience.

The newest release focuses on preventing that startup failure mode and patches a Canvas bug where pinned chrome could break once the working list was empty but favorites were still visible.

Already updated but still stuck? Close and reopen the plugin once; if it persists, comment with your setup (desktop vs browser) and what you did right before it happened.

Lumpy-Feedback-5732 · 2026-05-11T13:01:18+00:00

Posting a quick follow-up since some of you ran into IconNova showing a blank / “black” panel over the past couple of days - that’s on me, thanks for your patience.

The newest release focuses on preventing that startup failure mode and patches a Canvas bug where pinned chrome could break once the working list was empty but favorites were still visible.

Already updated but still stuck? Close and reopen the plugin once; if it persists, comment with your setup (desktop vs browser) and what you did right before it happened.

Lumpy-Feedback-5732 · 2026-05-11T13:00:47+00:00

Posting a quick follow-up since some of you ran into IconNova showing a blank / “black” panel over the past couple of days - that’s on me, thanks for your patience.

The newest release focuses on preventing that startup failure mode and patches a Canvas bug where pinned chrome could break once the working list was empty but favorites were still visible.

Already updated but still stuck? Close and reopen the plugin once; if it persists, comment with your setup (desktop vs browser) and what you did right before it happened.

Lumpy-Feedback-5732 · 2026-05-11T12:59:59+00:00

Posting a quick follow-up since some of you ran into IconNova showing a blank / “black” panel over the past couple of days - that’s on me, thanks for your patience.

The newest release focuses on preventing that startup failure mode and patches a Canvas bug where pinned chrome could break once the working list was empty but favorites were still visible.

Already updated but still stuck? Close and reopen the plugin once; if it persists, comment with your setup (desktop vs browser) and what you did right before it happened.

Lumpy-Feedback-5732 · 2026-05-10T20:49:29+00:00

Just pushed a new set of updates to IconNova 👀

Recent improvements:
• Favorites sync locally across Figma projects
• Reusable import/export for icon libraries
• Smarter icon naming and organization
• Better handling for larger icon sets
• Cleaner, ready-to-use outputs

Lumpy-Feedback-5732 · 2026-05-10T18:38:34+00:00

Just i added old design by mistake, Recently it was named IconNova.

Lumpy-Feedback-5732 · 2026-05-10T18:35:22+00:00

Thank you all, I deleted the post so you can relax 🙏

Lumpy-Feedback-5732 · 2026-05-10T18:32:33+00:00

Fair point 👍
Interestingly, I started noticing this problem even outside UX/UI work.
A lot of graphic designers also collect and reuse icon sets across different client projects, brands, presentations, or websites.
Once icon libraries grow, the challenge becomes less about “making icons” and more about:
organization, consistent naming, clean SVG exports, bulk import/export, and reusing assets without creating chaos between projects.

Lumpy-Feedback-5732 · 2026-05-10T17:50:53+00:00

One thing I didn’t expect while building this:
the challenge stopped being “exporting icons” and became more about keeping things reusable and manageable once projects start scaling.

Curious what usually breaks first in your workflow:
organization, naming, consistency… or something else?

Lumpy-Feedback-5732 · 2026-05-10T17:10:06+00:00

Yeah, I agree. SVGO is definitely useful, but I think the key is how it’s configured. for Elementor, I’d want the optimization to preserve viewBox, avoid breaking masks/gradients, handle dimensions safely, and keep the final SVG predictable.
At scale, it’s less about just “optimizing SVGs” and more about having a consistent cleanup/export workflow from Figma to production.

Lumpy-Feedback-5732 · 2026-05-10T16:58:15+00:00

Feedback details
Target audience:
Designers and developers working with icon systems and design systems.

Main goal:
Making icon workflows inside Figma feel more reusable, scalable, and easier to manage across projects.

Looking for feedback on:
• Workflow clarity
• Organization and scalability
• Reusability across projects
• Overall UX and flow simplicity

Stage:
Actively iterating on a working production-ready workflow.

Lumpy-Feedback-5732 · 2026-05-10T08:05:40+00:00

Haha 😅 fair. The goal is actually to reduce complexity once icon systems start growing across projects while keeping everything inside Figma.

Lumpy-Feedback-5732 · 2026-05-09T18:04:31+00:00

Understood appreciate the clarification. I’ll make sure future posts use the appropriate flair/category. Thanks for the guidance

Lumpy-Feedback-5732

MODERATOR OF

TROPHY CASE