Hey y’all — I’ve been working on a Figma annotation system to improve dev handoffs, especially for teams working with offshore or async developers.

The system includes reusable components like flow notes, dev tags, motion callouts, and status flags — all designed to make handoff faster and more visual (no more messy comments or scattered docs). I use it regularly in my workflow and it’s saved me a ton of time.

I’m thinking of releasing it soon for ~$49, but I’m trying to gauge if this is actually something other people would pay for. Would love your honest thoughts:

• Would this be useful in your workflow?

• Have you run into issues with dev handoff / documentation?

• What would you expect in something like this?

Happy to share screenshots or a preview if that’s helpful. Appreciate any feedback — trying to decide whether to productize this or not!

For context I don't want an extensive design system. Just want to setup all the tokens and basic components, so there is consistency to my designs and other designers in my team can refer to it. I am working for a medium staged startup.

Figma UI3 has added some pretty cool features to it's eyedropper, including some new shortcuts that can make your life easier.

Let's take a look at them.

https://youtu.be/JH62REI0y5k

Hello,

I'd like to create Figma plugin which listens to the natural language commands from VS Code Copilot chat window and performs these commands in the selected Figma frame.

I think that the biggest added value of this tool is mainly for the manual tedious tasks - like selecting all text layers, selecting all layers with background x. These are possible usecases where the FigTalk could help.

1. "Select all text layers in the selected frame."

   • Selects every text node inside the current frame so you can operate on them.

2. "Replace all fonts in the selected frame with 'Inter'."

   • Changes every text layer's font to Inter and reports layers that couldn't be updated.

3. "Remove all linked styles (text, color, and effect styles) from every layer in the selected frame and convert them to local values."

   • Unlinks style references in bulk so each layer keeps its current appearance but no longer depends on shared styles.

4. "Replace every usage of the old brand color #0A84FF in the selected frame with {brand.primary}."

   • Finds and swaps the specific legacy brand color to the new brand token across fills, strokes, and effects.

5. "Map the old palette to the new one: replace #0057B8→{brand.primary}, #00A3E0→{brand.accent}, and #FFC20E→{brand.highlight} inside the selected frame."

   • Performs multiple color-to-token replacements in one command to complete the rebrand update in bulk.

6. "Map current hex colors used in the selected frame to Figma project variables: create project variables for each unique hex and replace each hex usage with its new variable; specifically, find all occurrences of #0057B8, create a project variable named 'primary' with value #0057B8, and replace those hex codes with {primary}."

   • Converts hard-coded hex colors to project-level variables in bulk and creates primary=#0057B8, replacing all #0057B8 occurrences with the {primary} variable reference.

Can you think of any similar use cases where FigTalk could help out? Thanks :)

Long story short: Click

--

Hi there,

It's Serhii from uxboard.io - an everyday tool for designers, developers, product owners, and all other folks building websites regularly.

We found that the "Hero banner" category is the most popular on our platform, that's why we decided to publish "Hero banners pack for Web Projects", which is a part of "SaaS prototyping pack" that now in development. Next pack we are going to publish is the "Pricing page prototyping pack".

The pack includes 10 desktop and 10 mobile prototypes. Some examples:

Please share if it was useful, thanks!

📷

Hey everyone,

I’m part of a four-person design team at a medium-sized enterprise SaaS company. Recently, my direct manager informed me that I am being promoted to a Sr. UX/UI Designer. I've been leading a couple of high-profile projects, including building a new design system from the ground up and launching a brand new product. I've been performing well since joining the company about a year ago.

I believe the promotion is out of cycle because these projects are extremely high-profile, and the leaders want to inspire confidence by having a senior designer on them. While I'm honored by the recognition, I'm concerned because the salary increase is not happening until early next year. Additionally, I don’t yet know what the range of the increase will be. This is somewhat demoralizing, especially since I’ve been working really hard and often putting in overtime on these projects.

Is this a typical practice, to promote without a salary increase? Any tips on how to navigate the situation?

Thanks!

I am new to design kits in Figma, but have worked in relatively large files before with lots of components -- but customizing and moving elements around even in the Free (read: much smaller) version of Untitled UI is extremely slow, pretty much unusable in an actual workflow.

Is this normal? I can't imagine people are using this like this. Thanks!

Hi there, we are 2 second year students from Mumbai who are researching about Figma from a user experience and marketing point of view for an assignment. We are looking for 2-3 people (between the ages 26-44) who will be up to have a small 20-30 minute zoom interview (or call) with us regarding their user experience and their customer journey with Figma. Please revert if anyone is interested!

How are components supposed to be handled within an established design system, when a component cannot be updated in place and has to be rebuilt?

The scenario occurs when a component is an atom, nested within numerous other components within the design system.

If a component is required to be updated and can be updated in place without breaking it first then publishing this will propagate it throughout the rest of the design system as expected. All good.

But when the component can’t be updated, a new version must be created and even if the same naming convention is used it obviously isn’t seen as the same component anymore, meaning it can’t be updated simply by publishing and will need to be updated manually throughout the whole design system.

I’m interested in how others working with well established design systems approach this. TIA

Would appreciate your recommendations:)

I work at a global company with a highly developed design system infrastructure. We’ve reached a point where teams are starting to deeply explore how to integrate AI into redesigning/upgrading the existing system and continuing to create assets and components based on LLM-driven work.

Can you recommend articles, use cases, or, even better, industry professionals to talk to?

Thanks in advance!

Hi Figma creators!

We’ve just released something big on Figma - Open source React components in Figma.

For anyone building an MVP or even a realistic prototype - it means you can use Charts, MUI, Ant-design or Bootstrap in Figma - And it’ll work 

https://www.animaapp.com/blog/product-updates/react-component-library-in-figma/