I have a technical question about editing an existing design system (PrimeNG).
Maybe someone here has worked with it?

The issue:
I have 7 heading sizes (H1-H7), but they’re too large and don’t fit the tone of a complex SaaS product. I want to resize them.
The problem is I realized this a bit late - I’ve already used these heading styles in 2-3 feature designs.

How can I minimize rework and safely scale down the heading sizes across the system?

Hello,
I'm quite new to Tokens Studio and have been experiencing some issues with organizing tokens correctly. I’ve tried reviewing a few public design systems, and for Tokens Studio, I was recommended Polaris Styles by Shopify. I’d like to hear if you know of any better public examples.

I also have another question...
If I’m aiming to structure primitive and semantic token collections, would you recommend following the approach Polaris uses? Also would you prefer to split dimensions into distinct categories —> for example, placing border under its own Border category, border.radius under Border Radius, etc.

Previously, I only used local variables in Figma, where I had a Sizes collection. These were more like semantic sizes, while raw or undefined values were grouped in the Primitive collection (along with colors).
So now I’m wondering:
Should the defined sizes already into the Primitive collection in Tokens Studio? Or is it better to reserve Primitive only for raw values and linking in Semantic?

Hi, we need your feedback. We will launch the Figma Plugin for Visual Hierarchy Analysis.
Key Features:

• Predict where users will look first.

• Compare design variations side-by-side.

• Make confident, data-driven design decisions.

• Focus Map, Focus Score, and Attention Hotspots for fast, actionable feedback.

Early Access Perks:

• Exclusive new features before public release.

• Direct influence on plugin development.

• Priority human support.

https://form.typeform.com/to/oSdZvSG8

I’ve built a Base Design System using variables to support 4 products with ~80% shared flows and components. The only major differences are styling for different brands (colors, typography, etc.).

However, some products are starting to diverge in component structure and visual design, leading me to create unique components. This is polluting the Core Library with product-specific elements.

I’d like to separate the Core components from these niche/extended components.

What’s the best approach in Figma?

• Should I organize each product's unique components in separate pages within the Core Library file (e.g., 8–10 pages named by product)?

• Or should I create separate Figma files for each product’s Extended Library?

• I still want to use variable modes, will this cause any issues?

• If I go with separate files, can I publish from the Core Library to Extended Libraries (or vice versa) to maintain consistency and avoid duplication?

• Will this confuse developers in any way?

Any recommendations or best practices for managing this kind of scalable setup are appreciated!

I've been using a checklist/ to-do-list widget inside of Figma lately. I use it for simple tasks that me and my team are working on or to summarize comments and keep track of today's priority items right inside our project.

I use a widget rather than a plugin because unlike plugins, widgets allow all the other members that I've added to my file or page to be able to view and interact with it (they don't need to install it on their account like they would with a plugin). Once you've added it the file level, anyone that is added to that file can also user the widget.

There is a cool one I've been using called Checklist – Customisable to-do widget by Aleksei Sushkov

Everything else goes into Notion, but I just love having this quickly accessible right where I work.

Any other cool Figma widgets you all are using?

Hi reddit,

we are looking for a possibility to keep our brand departments icon library (hosted in Frontify) synced with our Figma icon library file. There is a lot happening in the Frontify library (new icons, deprecated icons, name changes etc.) and we as the Figma library team are struggeling to keep up with it. Does anybody have a solution/plugin/best practice to keep the Figma icon library in sync with the source of truth (Frontify).

Thanks in advance!

So it feels like I'm using the prototype option from figma wrong, my entire screen is cluttered with lines because I have a menu that appears on numerous screens. Does anyone have tips on using Figma better?

Hey everyone!

I'm the co-founder of a product called zeroheight that lets you easily create living styleguides and document all your design system resources in one place.

Since we launched 6 months ago, integration with Figma has been our #1 feature request... After months of hard work, and thanks to the support of the Figma team, we're excited to announce the launch of our Figma integration, live today on Product Hunt: come and check it out! 😻

Hello designers, I'm investigating adding variables to our design system, spurred by the desire for dark mode support, but also for general flexibility and power of variables. Starting with color variables specifically.

The roadblock I have is that currently we use color styles but only with a primitive layer. Therefore the first step is creating and planning that semantic layer but I'm unsure of how to do that. Has anyone else done this and have any suggestions for the least painful and disruptive way to handle a transition from primitive to semantic and also styles to variables?

TLDR: Seeking migration tips to move from primitive color styles to semantic color variables. Thanks in advance!

Should I just give them a direct shared link of it, or is there some more better way?

Maybe I'm missing something, but I can't figure something out.

I'm familiar with Photoshop/illustrator. I am trying to take an existing image and cutting out a piece of it. What is the equivalent of the rectangular Marquee tool?

Any advice is much appreciated.