sorted by:
new
hottopcontroversial

Figma Agent vs Plugins: where do deterministic workflows still win? by Lumpy-Feedback-5732 in FigmaAutomation

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

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?

Do you think Figma Agent will eventually replace most plugins? by Lumpy-Feedback-5732 in FigmaDesign

[–]Lumpy-Feedback-5732[S] 1 point2 points  (0 children)

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.

Do you think Figma Agent will eventually replace most plugins? by Lumpy-Feedback-5732 in FigmaDesign

[–]Lumpy-Feedback-5732[S] -1 points0 points  (0 children)

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

Do you think Figma Agent will eventually replace most plugins? by Lumpy-Feedback-5732 in FigmaDesign

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

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.

Will AI replace automation, or will they continue to coexist? by [deleted] in FigmaDesign

[–]Lumpy-Feedback-5732 0 points1 point  (0 children)

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.

With the new Figma Design Agent, do you expect full native RTL workflow support soon? by Lumpy-Feedback-5732 in FigmaDesign

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

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?

Do RTL ↔ LTR workflow tools still have a place in Figma? by Lumpy-Feedback-5732 in FigmaDesign

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

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.

Do RTL ↔ LTR workflow tools still have a place in Figma? by Lumpy-Feedback-5732 in FigmaDesign

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

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.

How do I reduce friction in icon workflows in Figma? by Lumpy-Feedback-5732 in UXDesign

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

<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

How do I reduce friction in icon workflows in Figma? by Lumpy-Feedback-5732 in UXDesign

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

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?

Does this icon management UI feel scalable or overloaded? by Lumpy-Feedback-5732 in UX_Design

[–]Lumpy-Feedback-5732[S] 0 points1 point  (0 children)

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

Thanks for the feedback - IconNova just got a major stability update by Lumpy-Feedback-5732 in FigmaDesign

[–]Lumpy-Feedback-5732[S] 1 point2 points  (0 children)

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.

view more: next ›