Ninety Day Rule

The Ninety Day Rule cuts your Figma plugin collection down to the tools that actually earn their keep. It sets a hard 90 day window. Open a plugin in that time or delete it forever. The full audit adds two more questions that expose the real value. Does this tool solve a problem you encounter more than once a month. Does this tool do work that Figma cannot do natively in 2026. Plugins that fail any of these get removed immediately. The rule exists because the Figma plugin directory exploded past ten thousand entries with the vast majority abandoned since 2023 or replaced by native features. Variables replaced dozens of token managers. Dev Mode made most handoff plugins pointless. The 2024 auto layout upgrades buried the old helpers. This leaves a small set of plugins that deliver consistent returns instead of sitting idle and bloating your interface.

This rule does not work as a casual declutter. It does not forgive plugins you keep for sentimental reasons or because a respected designer recommended them two years ago. It rejects the 2022 habit of installing every tool mentioned in a viral thread then never touching them again. The rule has zero tolerance for the median setup of 40 installed plugins where only four see regular action. It refuses to let security risks from unmaintained tools linger in your workspace or create decision friction every single time you open the menu.

Take the concrete case of the design org at Notion in Q1 2026. After rapid hiring their shared team library had accumulated 71 plugins. The team lead scheduled a 90 minute audit using the decision tree with branches for keep and delete. They started at the top. The color palette generator installed in 2022 failed immediately because Tokens Studio combined with native Variables did the job better and connected to their Tailwind output. The auto layout helper from 2023 got deleted next since auto layout v4 fixed those issues natively and the plugin actually conflicted with new behaviors. Basic handoff tools from the pre Dev Mode era lasted three seconds in the review before hitting the trash. Pre 2024 AI plugins that promised full screen generation from text prompts were removed after the team compared them to the superior results from Figma MCP paired with Claude Code on real design system files. That left the keepers. Tokens Studio passed all three questions because the team exported versioned tokens to JSON files that fed directly into their production React components updated in every biweekly release. Stark cleared the bar by running weekly contrast checks and color blindness simulations on their constantly evolving database views preventing multiple accessibility regressions that would have reached users. Content Reel earned its spot when writers used it to fill placeholder content across 300 frames for the new AI features page with realistic names emails and product copy pulled from actual customer data. Google Sheets Sync pulled live data from their product roadmap sheet into 45 variant components avoiding hours of manual edits every sprint. Iconify supplied the exact Lucide icons needed for the sidebar without leaving Figma or searching GitHub repos. Remove BG cleaned up 22 hero images for their launch campaign in under five minutes each. Figmotion handled the keyframe animations for their interactive product tours that required Lottie export and precise timing curves which Smart Animate still cannot match. The Translator plugin allowed the localization team to test layout breaks in French German and Arabic in minutes before handing off to professional translators. After the audit the plugin panel showed a slim column of 11 active tools on the right and a long list of crossed out entries on the left. The before and after comparison images revealed cleaner handoffs with proper annotations real tokens and no more redundant layers or outdated CSS inspectors.

Run the Ninety Day Rule every time your plugin menu feels cluttered or when Figma ships updates that absorb old functionality like the Dev Mode expansions in 2024. Apply it at the start of major design system overhauls at companies like Vercel or Shopify. Use it ruthlessly when onboarding new hires to prevent them from repeating past mistakes. The rule delivers best for mature teams with established code connections where plugins must integrate deeply with GitHub repositories and component libraries instead of duplicating built in features. Turn to it if you want your tools to accelerate real work instead of creating overhead and security holes on NDA projects.

Avoid the rule during initial Figma onboarding when every new plugin reveals useful native shortcuts you did not know existed. Do not apply it to short term experiments designed to push the boundaries of what a single file can do or test wild new micro interaction techniques. Skip the full audit if your work involves highly specialized domains like medical device interfaces where each plugin requires separate compliance reviews from legal. Refrain from using it on plugins that serve different team functions on irregular schedules even if some members have not opened them recently.

Plugins that survive the Ninety Day Rule actually get used every week while the rest just get in the way.