Finds detached component instances in your document, so you can decide what to do with them.

Make sure to check replies for more ideas.

In this weekly Office Hours in Figma, Anthony DiSpezio and Rogie King are talking about team structure, multiple component libraries, versioning, and updating components at scale.

Smart workarounds for making reusable progress bar components that can indicate different values.

Drag-n-drop from the Assets tab is a time-saver.

Aleksei Kipin shows how to apply the Atomic Design approach to creating Figma components.

A valid point that specifying an element as a component and then detecting all the places where it has already been used would be a great alternative to the existing approach of defining components before using them.

A list of 5 solid principles for building components — reusability, nesting, UI and UX patterns, reusing styles, and consistent naming structure.

“A strategy that may help ease some of the pain and confusion when deprecating unwanted components.” That’s something we all have to do from time to time, so I’m glad Steve Dennis documented his approach.

Fantastic plugin for finding all instances of the component. I used it while migrating and unifying a large design system and it was irreplaceable.

This plugin enables you to select any instance of a local component (not from a library) and edit the master component in place from the context of wherever you are using the instance. Handy if your master components are on another page.

Master creates a new component from a set of similar objects. The demo video makes it easier to understand the concept. It seems like a really powerful tool for tidying up a project after design exploration is over.