Skip to main content
Question

My design system components are copied into another file, and then published. Suddenly all my instances point to the newly published copies. Bug? Preventable?

  • June 10, 2026
  • 7 replies
  • 44 views

UsabilityJeff

Situation
My dev team is working with Claude. I’m told they need a clean design system file with the relevant component definitions and nothing else. My working design system file is full of random experiments, and all my prototypes use that set of components. (I manage my own versioning of said components when there needs to be major overhaul). Anyway, I’m told that the clean file needs to be published for Claude to digest.

Issue
When dev publishes the clean design system file, all my existing prototype instances suddenly point to the new kid on the block!

Questions

  1. Is this expected?
  2. Is it preventable?
     

7 replies

Celyn_L
Figmate
  • Figmate
  • June 10, 2026

Hi ​@UsabilityJeff, Celyn from Figma Community Support here.

Could you share a bit more about how the "clean" design system file was created and published?

For example:

  • Was the file duplicated from your existing design system?
  • Were the components copied into a brand new file?
  • Are both files currently published as libraries?

Understanding how the new library was set up will help determine whether the behavior you're seeing is expected and what options may be available to prevent it.

Happy to take a closer look once I have a bit more context. Thanks! 


UsabilityJeff
  • Author
  • New Participant
  • June 13, 2026

Hi Celyn,
Thanks for following up.


I used “Duplicate” from the context menu to create a new Figma design file. Then I quickly deleted all the experimental junk that wasn’t directly a component definition.
My working design system file (WIP) is published, since all of the actual prototypes reference it.
The Clean file must (so I’m told) also be published for Claude to find it. It only needs to exist for Claude.

I wanted to keep the Clean file distinct from the WIP, so that I could be more cavalier with my experiments to see how changes look/work in all the prototypes that consume the WIP components. Didn’t want to mess up Dev, even for only 30 min, if they happen to be needing the components. If there are other ways to achieve this I’m all ears!

Cheers,
Jeff


Celyn_L
Figmate
  • Figmate
  • June 16, 2026

Hi ​@UsabilityJeff, thanks for taking the time to explain your setup in more detail.

I can see why you'd want to keep a separate, clean design system file for Claude while continuing to use your WIP library for experimentation and ongoing work. From what you've described, it sounds like publishing the duplicated library caused your existing prototype instances to unexpectedly point to the newly published library, which isn't the outcome you were expecting.

I'd like to get this in front of the team so they can take a closer look at what's happening here.

I've gone ahead and created a support ticket for you. Your ticket number is #1964073.

It will be really helpful if you could reply directly to the ticket with:

  • A short screen recording showing the library setup and what happens when the clean file is published
  • Links to the impacted files, and invite support-share@figma.com with “Can View” access (this won’t impact your billing and will allow us to reproduce the issue and investigate further with Engineering).

Someone from the team will be reaching out with next steps shortly. Thanks!


UsabilityJeff
  • Author
  • New Participant
  • June 16, 2026

I’m so sorry, I looked everywhere I could, and googled, and still don’t see where to find my ticket and post the video. Can you please include a link?


Celyn_L
Figmate
  • Figmate
  • June 17, 2026

Hey ​@UsabilityJeff, no worries at all.

I took a look at your ticket #1964073 and saw that you’ve responded there. That’s your support ticket, and it goes directly to the email inbox associated with your Figma account.

That’s the right place to send your screen recording and file link, so feel free to reply there with those details when you have a chance.

Hope that clarifies, and let me know if you need any further help!


UsabilityJeff
  • Author
  • New Participant
  • June 17, 2026

I took a look at your ticket #1964073 and saw that you’ve responded there.

 

So sorry to be so stupid, but while you say I’ve responded there, I’m not sure how I would have done that given that I can’t currently find that page. I’m expecting to be able to go to a support style website and look up my ticket and see the thread, be able to post the requested files, etc. Can you please send me a link to such a page if it exists?


Celyn_L
Figmate
  • Figmate
  • June 18, 2026

Hi ​@UsabilityJeff, no worries at all, and thanks for following up.

Just to clarify, support tickets aren't hosted on a separate support portal. The support ticket (#1964073) that I have created for you is sent directly to the email address associated with your Figma account.

I've just sent another email through your support ticket (#1964073) to help make sure it reaches you. Please check your inbox (and spam/junk folder just in case) for a message from Figma Support.

If you're still unable to locate the email, please let me know and I'll be happy to take another look.

Once you receive it, you can simply reply directly to that email with your screen recording and file link, and the Technical Quality team will follow up with next steps.

Thanks!