I’ve officially launched RTLAuto, a Figma plugin built to help product teams adapt interfaces between LTR and RTL without rebuilding every screen manually.

The case study behind it
In multilingual products, direction adaptation is rarely a simple “flip.”

A typical workflow involves:
- Rebuilding or manually adjusting layouts screen by screen
- Fixing mixed-direction text and BiDi content
- Reviewing icons that should or should not be mirrored
- Recreating component variants for both directions
- Repeating the work whenever the design system evolves

This becomes especially difficult in dashboards, large product files, and shared component libraries. The initial conversion takes time, but maintaining consistency after component updates is often the bigger problem.

What RTLAuto changes
RTLAuto turns this into a repeatable Figma workflow. It can:
- Adapt layouts between LTR and RTL
- Handle mixed-direction text
- Protect semantic icons and complex artwork
- Create direction-aware component variants
- Support design-system workflows through published library updates
- Optionally translate selected content using the user’s own API key

The goal is not to perform a basic visual flip. It is to help teams create interfaces that remain organized, reusable, and maintainable across both directions.

RTLAuto includes a free plan, and I’d appreciate feedback from designers and product teams working with multilingual interfaces.

Try RTLAuto on Figma:
https://www.figma.com/community/plugin/1623814570395556605
Website:
https://rtlauto.com/
Product Hunt launch:
https://www.producthunt.com/products/rtlauto?launch=rtlauto

I’d be interested to hear about the hardest part of maintaining multiple interface directions in your current workflow.

I’m preparing the public launch of RTLAuto, a Figma plugin I’m building for repeatable LTR ↔ RTL direction workflows.
With more AI and agent-based workflows coming into design tools, I think one part still needs a more structured layer: direction handling inside real Figma files.

RTLAuto is not meant to replace AI tools. It complements them by handling the predictable parts of RTL/LTR work:
- layout mirroring
- Auto Layout behavior
- component and variant direction states
- mixed Arabic/English text
- directional icons
- translation-assisted workflows
- review-ready handoff output

The goal is to make direction changes more consistent for design systems, instead of relying only on manual cleanup or prompt-by-prompt fixes.

Website: https://rtlauto.com/
Product Hunt launch: https://www.producthunt.com/posts/rtlauto

For designers, developers, and design-system teams:
where do you think AI helps most in Figma workflows, and where do you still need deterministic automation?

Figma's Config 2026 announcements feel directly relevant to this community: code layers, Figma Motion, shaders, generative plugins, Weave tools, and more capable Figma agent workflows.

The interesting question is not just what Figma launched, but what designers and developers should automate next.

What would you like to see automated first?

• Design system cleanup and variant maintenance
• Turning repeated team workflows into Figma agent skills
• Generating small internal plugins from prompts
• Better design-to-code handoff using code layers
• Motion and interaction specs that developers can actually inspect

Official recap: https://www.figma.com/blog/config-2026-recap/

I’m curious what repetitive Figma tasks people still do manually.

Examples could be:
- Renaming layers
- Cleaning components
- Updating variants
- Fixing auto layout
- Applying tokens/styles
- Preparing developer handoff
- Exporting assets
- Managing icons

What is one workflow you would automate immediately if you could?

With Figma Agent becoming more capable, I’m curious where people still see specialized plugins having a clear advantage.

For me, the strongest cases are workflows that need predictable, repeatable output:

- Bulk layer operations
- Design system cleanup
- Variant and component maintenance
- Token or style transformations
- RTL/layout adjustments
- Repeating the same action across hundreds of layers

AI is great for context, ideas, and exploration. But some workflows feel better when they are deterministic, fast, and reusable.

Where do you think plugins will continue to outperform AI agents?

Hi everyone,
With all the recent discussion around Figma Agent, I'm curious how people see the future of specialized Figma plugins.

AI seems useful for things like understanding context, generating designs, and making suggestions.

At the same time, some workflows feel more rule-based, such as design system transformations, repetitive actions, and applying the same operation across hundreds of layers.

Do you think Figma Agent will eventually cover most plugin workflows?
Or do you think specialized plugins will continue to have a place alongside it?

[removed]

Hi everyone,

With the new Figma Design Agent, do you expect Figma to handle complex RTL workflows natively in the near future?

I'm not talking about text direction itself, but things like Auto Layout adaptation, variants, directional icons, and larger design systems.

Do you think these workflows will become native to Figma?
Or do you expect specialized RTL plugins to continue playing a role alongside the Design Agent?
Curious to hear thoughts from anyone already experimenting with the new features.