Figma has no built-in way to track design system component usage across files
I manage a design system used across 40+ Figma files by a team of 8 designers. We have 200+ components (buttons, cards, modals, etc.). The problem: I have no idea which components are actually being used and which are dead weight. Are designers using the new button variants or still creating custom ones? Is anyone using that complex table component I spent 2 weeks perfecting? What I'm trying to do: Clean up the design system and prioritize updates based on actual usage. But I can't make data-driven decisions because Figma doesn't show "this component is used in 47 instances across 12 files" vs "this component has never been used." Current workaround: Manually searching for component instances file by file. It's impossible with 40+ files. I've tried asking designers in Slack "do you use Component X?" but memories are unreliable. Why this matters: Our design system file is bloated. Loading times are slow. New designers are overwhelmed by 200+ components when maybe only 80 are actively used. I want to archive unused components and focus maintenance on what matters. Who else faces this: Any design team with a component library bigger than 50 components or used across multiple files/projects. Existing plugins don't solve this because they only work within a single file, not across an entire workspace. I need workspace-level analytics showing "Button/Primary is used 340 times across 23 files, Button/Ghost is used 4 times in 2 files." This should be a native Figma feature or at least a Figma plugin with workspace access.
No clear way to understand how effectively I am studying
I spend a lot of time studying, but I struggle to understand how productive that time actually is. I don’t know which subjects I spend the most time on, which topics I struggle with, or whether my study habits are improving over time. My current workaround is guessing based on how tired I feel or how confident I am before an exam. Some tools allow time tracking, but they require constant manual input and don’t reflect real study behavior. There is no simple way to connect time spent, topics studied, and actual learning progress in a way that is easy for students to use. This makes it hard to adjust study strategies or identify weak areas early.