Taming multiple design systems with a single plugin
summary
Intuit describes building a Figma plugin backed by a centralized design data as single source of truth that maps Figmas node ids to code via a developer portal and a data lake the team manages. The system reconciles 80+ published Figma libraries across business units, serves themed components with tokens and variants, and exposes code links and storybook metadata. The plugin is a web app rendered in an iframe build-once run-anywhere model (Figma VS Code Android Studio). They ship incrementally and plan to open source it.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:26Kellys example
- 6:44Solano example
- 8:43Kellys introduction
- 10:13Design data
- 12:00Applying design data
- 14:20What is design data
- 15:41Developer portal
- 16:58Data lake
- 19:37IFrame
- 21:42Conclusion
related talks
16mDesign Language on Autopilot: How Figma and Code Can Automate Your Workflow
29mBuilding custom Figma plugins to unlock new capabilities
25mUsing Figma to go beyond Figma
57mUnifying design and development through design systems
37mExtend what's possible with Figma Plugins
12mDesigner's workflow improvement with Figma - Notion integration
17mThe magic of ‹div›RIOTS plugins
19mBringing Developers into the Design Process