Figma Make not using my library components

I’m also having the same issue. I created a fresh Figma Make file and made sure it was referencing my Design Library Figma file that I had imported over previously. It didn’t pull over any of the components from my library and just updated the general font/colors being used. None of the elements actually match those of the components in my design system, and after working with the AI model it’s asking me to just upload components one at a time, which also doesn’t work well because it only accepts links for component instances, not component sets. So I can’t point it to my Button component that has 108 different variants with different colors and states (hover, disabled, outlined vs filled vs text only, etc.).

Is there any update on this feature?

I am using Figma Make and selecting my Library which contains a Design System with Styles, Colours and Components. However Figma Make doesn’t seem to ingest any of this information and the code which is produced is a generic design system with components not from my Figma file. It doesn’t even pull my colour variables.

We're having the same problem. We can't get Figma Make to see our library at all, despite it being published.

I tried manually teaching it each component, but it won't accept frames with component sets or main components. I eventually tried pasting a documentation frame with instances and property descriptions into Figma Make. The model finally 'saw' something, but the output has major issues with styles and padding. It seems like documenting components within the Figma Make file itself is causing a lot of property errors

We’re having the same issues here. Doesn’t matter what I try, Make will not find or use my components or library. 

I haven’t gone as far to try to create a new component to test this (because that solution isn’t helpful), but Make is currently unusable and there is so much potential for it (at least for my team and business model).

Me again, for those of you who are having issues, I ended up just prompting the AI to update the native React components in the “Code” section it references to match my design system states and appearances. I had to do it manually for each component, so it’s definitely not an ideal solution for those of you with multiple brands and hundreds of components. I focused on getting key foundational components right (buttons, checkboxes, radios, input fields, selectors, etc.) and I’ve just been doing other ones one-by-one as I need them.

The way I got around the component set issue was by making a new frame and just selecting all of my component variants and ALT+Dragging them over into the new frame to turn them into instance sets. I then copied the link to that frame and uploaded it to Figma Make to reference for my prompt.

I then manually go in and adjust the React code (which isn’t too bad if you know very basic coding fundamentals) to clean up any discrepancies from how it interpreted my prompt and component instance sets to how they should be.

Again judge whether or not this process is worth it for your team and workflow.

Any solutions or updates on this?

Hi All, thank you for continuing to share your experience with using Library components in Figma Make!  

We hear you. This is a persistent and genuinely frustrating gap, so we want to be transparent about where things stand. We've confirmed that even when a library is correctly connected and published, Figma Make currently has limited visibility into your component sets, variants, and tokens. While it can access styling context (colors, typography, etc.), it often cannot reliably resolve and apply the actual components. Component extraction for Make Kits is a known limitation we're actively working on, though it's not yet generally available.

In the meantime, here are the best practices we'd recommend based on what's working for people in this thread:

• Always start from a fresh Figma Make file
  • Re-iterating from an existing Make file can cause library references to break. A clean file gives Make the best chance to correctly pick up your library on load.
• Create a Make Kit from your library file to apply styles
  • To apply your library's styles (colors, typography, etc.) consistently, create a Make Kit directly from within Figma Make, not from the library file itself. Once set up, that Make Kit can then be applied to any new Make file.
• For components, manually create Make versions one frame at a time

  • Make currently accepts links to component instances, not component sets or main components. You can do this in two ways:

    • Attach one frame at a time as a reference → create a new frame, ALT+drag your component variants into it (converting them to instances), then share that frame link with Make.
    • Use a Make Kit if you want these component references to be reusable across files.
• Manually update the base React components in the Code section
  • For foundational components (buttons, inputs, checkboxes, etc.), you can prompt Make to update its native React components to match your design system's appearance and states. It's time-consuming, but once done, those components persist across your Make sessions. You can also do this within a Make Kit if you want those component definitions to be reusable.

We know these are only temporary workarounds, and we want to do better. We've escalated the full scope of this thread to the Figma Make team. We'll update this thread when we have more to share. Thank you for your patience and understanding. Your feedback is genuinely helping us improve.

Make Kit is not MVP at all, just a half-MVP and useless at all. Why did you publish a function like that. Did you guys do some research how many people will just import token to Make but not import actually components into Make production env?????