Extend what’s possible with plugins for you and your team | Figma Blog (opens in new tab)

Figma’s post argues that plugins can turn repetitive, team-specific design tasks into fast, reusable workflows. Examples from GitHub, Atlassian, and Uber show how teams use plugins for component management, theming, realistic content, critique, and collaboration. The conclusion is that when no public plugin fits a specialized need, teams should build bespoke tools—and potentially combine them into a unified plugin.

Building a Unified Plugin at GitHub

Brian Lovin began creating plugins at GitHub after noticing how much time designers spent on repetitive operations.

• A borders utility toggled the visibility of divider layers within list-item components.
  • This allowed GitHub to maintain one flexible component instead of multiple components for every divider size and placement.
• A color-theming plugin helped designers manage light, dark, and high-contrast themes.
  • It searched functionally named styles and quickly switched entire designs between themes.
• A data population plugin pulled live API data into designs.
  • It mapped avatars, usernames, and names to appropriately named component layers.
• These tools were consolidated into a single “mono plugin,” giving the team one interface for several workflow improvements.

Product-Specific Content at Atlassian

Atlassian created the ADG Data Generator to prevent designers from using generic or misleading placeholder content.

• Designers can generate data appropriate to specific products:
  • Jira projects and ticket numbers
  • Bitbucket branches and commit messages
• The plugin keeps related content logically connected, such as matching project names with project descriptions.
• For user imagery, it generates realistic but entirely artificial faces instead of using stock photos of real people.
• Atlassian shared the generator’s source code with the broader community.

Collaboration and Critique at Uber

Uber’s design team developed more than four plugins to improve collaboration, consistency, and speed.

• A mobile design critique plugin creates a QR code and URL for the selected Figma frame.
• Critique participants can open the design on their own phones and experience it at the intended mobile scale.
• This gives each reviewer a better sense of how the design feels in-hand than viewing it on a shared large screen.

A Pattern for Identifying Plugin Opportunities

The examples show that useful plugins often emerge from recurring friction rather than from abstract experimentation.

• Look for repetitive tasks that require many clicks.
• Target workflows tied to a company’s own products, components, data, or design system.
• Automate tasks involving large sets of styles, layers, or content.
• Combine related utilities into one accessible team tool when multiple plugins begin to accumulate.

Teams should start by identifying a specific, repeated workflow problem and build the smallest tool that removes it. Over time, those focused tools can become a broader internal plugin tailored to the team’s design system and processes.