Multiple Figma Files | Scaling Your Design System Without Chaos

Headway on YouTubeWatch on YouTube

SaveMark complete

Sign in to save videos and track what you’ve finished.

AdvancedDesign Systems3 min

About this video

Explains why splitting a design system into several Figma files does not break agentic workflows when components are defined in code and Storybook. Covers centralising design tokens and variables in one file, pulling them into product-specific files, and loosening governance so designers can publish new components themselves.

What you’ll learn

  • Centralise design tokens and variables in one Figma file
  • Pull shared tokens into product-specific Figma files
  • Set up governance so designers can publish new components without a bottleneck