I think you are on the right track with Figma Make with the recent feature of being able to select a design system library. However, if you take this a few more steps I think you might have something:
- Expand the definition of a Figma design library object to include design system concerns including: design components, design tokens, and guidelines (general usage, component usage, accessibility compliance, motion, etc.) - similar to what you can add to the Guidelines.md file.
- Allow designers to edit all of these concerns in Figma, attaching them to their design system.
- When the user selects a design library in Figma Make all of those concerns come with it. Think of it as a schema or blueprint for building components and applications.
- Provide the ability to connect to existing production (React, Angular, Web Components, etc.) components in GitHub so that designer prototypes are rendered with a very high level of accuracy and fidelity.
- Alternatively, generate components based on the guidelines and rules specified in the design library.
For me, the ultimate goal would be for designers to be able to generate their designs and prototypes using our existing Figma and production components. The handover from design to development would be a package that is 80% complete. The developers would just need to wire things up and connect it to the backend which would help accelerate time to market.
Or alternatively - for product teams consuming your design system - let them generate the component tech stack of their choice as long as it adheres to all of the guidelines specified in the design library.