Why Are You Detaching? A Figma Concept

This is a concept, not a Figma feature. I built it as a working prototype.

Design system teams can see that people detach their components, but not why. A detach is the clearest signal that a component doesn't fit someone's work, and right now that signal disappears.

When you detach a component from a shared library, a small popover asks why. The reasons are the ones that actually come up: missing a variant, spacing doesn't fit, content doesn't fit, it's broken, or just exploring. There's an optional note for anything else.

On the other side, the design system team sees those reasons in library analytics, per component, so they can see which components keep getting detached and for what reason.

The detach always happens. The question comes after it, never before it, so nobody's work is blocked.

It only asks about library components. Local components stay silent, because they're not anyone else's problem.

It asks once per component per session. After that, a quiet toast offers to share the reason instead of interrupting again, and there's a "Don't ask today" option.

"Just exploring" is never sent to the library team. It isn't a signal, so it shouldn't show up as noise in their analytics.

Built with React, TypeScript and Motion. Try it here, best on a laptop: https://uzookafor.com/figma-detach