Hey, I’m back with a new user story for the Figma product management team. I want to share an idea to improve Figma for design system engineers. It looks like Figma falls in love with prototypie-type guy designers and doesn’t care to design system engineers because in 2023 config release is conditional for them and 2024 year Figma slides 
Just kidding! Let’s get back to the problem. When developing a design system, we typically create core components first and then use them to create nested components. The best way to do this in Figma is by using the nested instance feature. However, a problem arises when I use a nested instance component in another parent component. I only want to edit one variant or boolean of my nested component, but Figma shows me all the variants, booleans, and text properties, making it complex to find the key variant or boolean to change. I believe that having a conditional logic or a boolean checklist for showing nested instance variants or booleans would be a better way to manage a design system, rather than showing all variants of a nested instance. Let’s take a look:
3 Likes
Its really usefull Good job
1 Like