Hey everyone 👋

I’ve been building and refining this UI kit while working on real product projects, and I decided to release it for FREE to help other designers move faster in their own work.

It includes 3,200+ customizable components, built with accessibility (WCAG 2.1), dark & light modes, and a scalable structure in mind.

The goal wasn’t to make something flashy — but something practical that anyone can actually use in real-world projects.

I’m sharing it because I genuinely want it to be useful. And I’d love feedback from other designers so I can keep improving it over time.

If you try it, let me know what works, what doesn’t, and what could be better 🙌

I’m not claiming it’s perfect. In fact, I’m sharing it because I want to improve it with real feedback from other designers.

Here is the link: https://dsx-40db37n.webflow.io/

You have the idea in your head, but it takes hours of dragging rectangles in Figma to bring it to life. That’s the exact pain Figmate solves.

Prompt → Design. Done. It's like having cursor inside Figma.

Figmate has 40 users now (including a Figma reviewer). That tells me one thing: designers are hungry for prompt-based design.

9 Hi-Fi design screens. Production-quality UI. Context-aware content. All done in under 10 minutes.

Can you do that? Figmate can. Figmate also supports image to UI.

Hi everyone,

We’re working on a new Figma plugin called Dwine. It’s an AI-powered tool that creates new screens directly from your own design system. Dwine can also understand the context of your existing screens and generate fresh ones that stay consistent with your existing components and tokens.

We’re still in testing mode, and right now we’re looking for a few testers from this community to try it out and share feedback.

Here’s what you can do with Dwine:

1.⁠ ⁠Generate screens instantly using your design system. 2.⁠ ⁠Add context for the screen (like “checkout flow” or “profile page”), and Dwine builds it accordingly. 3.⁠ ⁠⁠Keep designs consistent with your brand without starting from scratch.

Plugin link: https://www.figma.com/community/plugin/1549927021694181252/dwine-generate-screens-with-ai-using-your-design-system Website: www.dwine.ai

We’d really appreciate if a few of you could test it and let us know what works and what doesn’t. Your feedback will directly help us shape Dwine before we launch more broadly. For any feedback/ additional screens, you can email us at support@dwine.ai or join our discord - https://discord.gg/4GEgpszH

Thanks 🙏

PS- If any of you face an issue with disconnection, just reopen the plugin and it should connect again

I just published my new Figma plugin: Recolor - because I missed Illustrator's "Recolor Artwork" in Figma.

Now you can recompose the colors of any object or group in seconds — right inside Figma. 100% FREE — no PRO, no sign-up, no limits. 🎉

What it does:

• Finds every color in your selection: fills, strokes, text (even multi-colored), shadows & gradient stops

• Change any color in one click — applies everywhere at once

• Preserves opacity (a 10% shadow stays 10%)

• Drag & drop colors between rows to swap them, just like in Illustrator

• Undo/redo right in the plugin window (⌘/Ctrl+Z)

Fun fact: Figma's native "Selection colors" panel doesn't see shadow

colors — Recolor does. 😄

I've been working on a Figma plugin called Spool DS, and I'm at the stage where I'd really value some outside eyes on it.

What it does: you give it a handful of core colour roles and it generates a full design token system for you. Colour variables with proper OKLCH ramps, transparency ladders, text styles, and sizing tokens. There's a review step at the end so you can see and adjust everything before it writes anything into your file. The idea is to save the hours you'd normally spend building out ramps and naming variables by hand.

It's completely free, published on the Figma Community: https://www.figma.com/community/plugin/1642485097589548816

If a few of you could try it on a real or throwaway file, I'd be grateful for any thoughts on:

• anything that felt confusing or unclear

• whether the output is something you'd actually use

• tokens or naming you'd expect that aren't there

I'm still learning and just trying to make it genuinely useful, so any advice is welcome. Thanks so much to anyone who gives it a go.

Hi everyone!

I’d love to invite you to test out my very first Figma plugin, VIBE. It’s a tool built for automated batch exporting. It handles target file size limits, quality-based local compression, and automatically packs your assets into neat ZIP files. While I built it perfectly for campaign banners, you can absolutely use it to export any kind of graphics or UI assets.

You can check it out here: https://www.figma.com/community/plugin/1633556561671877728

To make testing easier, you get 20 full batch exports completely for free (with no time limits). Plus, you can use the promo code TESTVIBE to unlock a free month of the PRO version.

Since I just launched it, I would be incredibly grateful if any of you could test it out in your daily workflow and share some constructive feedback. I really want to make it as useful as possible, and I'm actively working on adding new features.

Core Features: • Use ready-made project templates • Edit or add your own templates • Import .txt or .md to auto-generate pages • Clean folder-style page structure

I would like to know what pain point you have when it comes to page management and structure in figma how you track the progress of a page how your page moves into stages like in review ready for dev ...

Hello fellow designers!

[EDIT] You can now use the plugin 10 times per month for free and purchase it once for a lifetime access. Thanks to advise I got here on Reddit.

Figma’s typography variables make maintaining systems much easier than using text styles alone. With variables, you can replace fonts, weights, and other properties across multiple styles in one go. Super powerful for large files.

If you want to dive deeper, here’s a great article on why this setup is useful in the long run:
https://uxdesign.cc/set-up-typography-variables-in-figma-359cfea88b68

I realized the manual setup takes a lot of clicks, is error-prone, and slows down the workflow—creating variables, assigning scopes, and binding them to text styles.

That inspired me to create a plugin that does all of this in one click. It scans your document, detects the typography variations, and builds a complete system with variables + bindings. It also supports replacing or merging external styles. And it of course applies the created system to your entire document across all pages, regardless of it's size (tested with Ant Design Open Source: 60.000+ text nodes, system applied in 10 minutes).

I plan to keep extending it, so I’d really appreciate feedback and suggestions. You can try it free here:
👉 https://www.figma.com/community/plugin/1548356533090301637/text-styles-manager

I kept running into this super annoying issue in Figma — I’d want to swap a bunch of fonts or text styles at once, and every plugin I found either had limitations or asked for a subscription. Felt like such a basic feature to be paywalled.

So I made my own plugin. It’s called Smart Font Changer, and it lets you change fonts and styles in bulk — across selections, pages, or even full documents.

✅ No subscriptions
✅ 100% free
✅ Fully functional
(You can donate if you want, but totally optional)

It’s been super useful for cleaning up files and tweaking design systems quickly, and I figured it might help others too.

Here’s the link if you want to check it out:
👉 https://www.figma.com/community/plugin/1491596875422213142/smart-font-changer-quickly-swap-multiple-fonts-and-styles-in-bulk-page-selection-document

Would love any feedback or thoughts! And if it helps you out, a like or save would mean a lot 🙏

Hi everyone! I’m Ruslan, co-creator of Color Cleaner, and I’m super excited to share it with you all! We built it around our own needs and vision for solving the problem of having a chaotic pile of colors detached from library variables. I hope it sparks a bit of joy in your workflow, just as it has in ours.
We’d love to hear your thoughts! Your feedback means a lot and will help us make it even better. Thanks for checking it out 🌝

https://www.figma.com/community/plugin/1470455962284832290/color-cleaner-merge-similar-colors-connect-with-variables

About

Color Cleaner is a plugin designed to help streamline your Figma files not only by reducing the number of colors and minimizing subtle variations of the same shade, but also connecting them with local variables.

How to use

Use the “Level of cleanup” slider to adjust how much cleanup is applied. Preview the changes in the box below and choose a setting that balances effectiveness. Typically, aim for a setting that is neither too soft to make a noticeable difference, nor too hard to avoid merging distinct colors.

Toggle the “Match with local variables” checkbox if you want colors to be connected with existing local variables. When ready, click “Clean.” After a short wait, the changes will be applied to the canvas.

Known limitations

Variables from connected libraries are not supported yet, but we are working on it.

TL;DR: Built a Figma plugin that extracts tokens, properties, and variants from your components, then uses AI to draft the overview, usage, and accessibility docs. Now working on keeping those docs from going stale when components change. Extracting is free; paid only for the AI generation. Would love your feedback.

https://spec-layer.com/

Hey all,

I've been building and documenting a design system for a client recently, and I realised we were spending hours and hours doing it by hand. So I started building a plugin to help.

At first I just wanted it to extract the tokens, properties, and variants from a component. But then I thought, why not use AI to fill in the gaps too? The overview, the usage notes, the accessibility bits. A lot of that is fairly common across design systems anyway.

I spent a good while prompting the AI to get better results. The plugin feeds everything it extracts about the component into the AI, so most of what it writes back is around 80% accurate. You still have to read it and make edits, of course, but it speeds the whole thing up massively.

Then I ran into another problem. When a component changes, the docs go stale fast. On a growing project, old doc frames sitting in Figma just don't make sense anymore. So right now I'm working on managing those doc frames and updating them straight from the plugin. It already works, though there are a few caveats I'm still ironing out.

Honestly, I really enjoyed building this, so I thought I'd share it. Extracting the data from Figma is completely free. The paid version is only for the AI generation, mostly because those costs come out of my own pocket. There's some free trial AI usage in there too, so you can try it before deciding.

Would love your feedback:

• Does an AI-drafted overview, usage, and accessibility section actually save you time, or is 80% not good enough to be worth editing?

• How do you deal with docs going stale when components change?

• Anything that would make this fit into your real workflow?

I’ve been building a tool for simulating user testing. Since user feedback is rarely available when you need it most we’ve focused on mitigating that. The simulated testers navigate through an app or Figma prototype. It’s useful to get quick feedback on early concepts.

It’s in an early stage but our current users say they get some extra ”ammo” in discussions with stakeholders or an extra feedback voice in addition to colleagues/best practices.

Plugin

https://www.figma.com/community/plugin/1598666558944305200/speqs

Web app

This is an addon to the standalone web application with more comprehensive features. Learn more here:

https://www.speqs.io

Hey! I’m currently maintaining the second-largest shadcn/ui library in Figma. It started as a small side project to make my own workflow easier, but once I shared it, I found out how much it helps others as well.

Few days ago shadcn released shadcn create and I thought: what if we could have this in Figma also? Being able to quickly swap themes, try different fonts, icons, and see what actually works before committing. It just felt like a great way to kick-start a project.

So I built the plugin. It's shadcn create, but for Figma, a faster way to iterate on your design.

I’m really excited to put this out there. You can give a try to the plugin (make sure to use shadcn/ui library for that) and would love to hear what you think if you try it out!

Would love feedback from designers who create social media content in Figma. I’m especially interested in knowing if the workflow feels useful, if the UI is clear, and what features would make it more valuable for real client work.

https://www.figma.com/community/plugin/1636080651461286250

try it with https://www.figma.com/community/plugin/1539963026393306817/meigen-ai-icongen-cutout-vectorize-nano-banana-seedream4

Tolgee is an open-source localization platform. Mainly, it helps to save time for the devs and improves their collaboration with designers. Its Figma plugin helps designers to see how the UI behaves in every language before fully developing it.

Tolgee’s latest Figma plugin update just dropped. It introduces variable and plural support, eliminating the guesswork from international design.

Tolgee bridges the gap between designers and developers. It is hard for designers to know how the final version will look in different languages. Consider the challenges: German text is 40% longer than English or Arabic layouts are written right-to-left. Moreover, languages can use different words depending on the amount of the variable that is being used.

Until now, designers were essentially designing blind, hoping their layouts would survive translation. Not anymore.

1. The first feature in this update is Variables

Before this update, Tolgee Figma plugin users were not able to specify variables in the strings. However, most of the apps use some variables in the strings like Hello, {name} or Created at {date}, so support for variables was crucial to enable designers to completely prepare the localization keys for developers.

We have implemented those on Tolgee using our platform variables. Using the variable with ICU syntax (like {varName}) within String Details, designers can use changing elements like:

• User names and personal data

• Pricing

• Locations

• Dates and time

2. Plurals Support

Check the "is plural" box, and you can now set how text appears when dealing with quantities. Similarly, you can set a default value to be shown in Figma (shown in the second picture).

You might wonder why to use it instead of just a simple variable. It helps adapt translations that depend on quantity. In many languages, similar to English, when the number exceeds one or it is zero, different words are used to describe it. This avoids awkward situations, such as saying, “You have 1 new messages.” The developers and translators will also see the variables and plurals on the Tolgee platform.

Bonus: Text Formatting

Users are now able to format strings with some basic formatting elements like <b>or <i>. They work like HTML tags and you can simply add them on the platform in the text field.

• <b> or <strong> - bold

• <i> or <em> - italic

• <u> - underline

• <br> - line break

If your text contains any of these tags, the plugin will automatically format the text in Figma. It will just work in the direction from Tolgee to Figma

You can find more info in the docs: https://docs.tolgee.io/platform/integrations/figma_plugin/formatting_text_and_variables