There's a whole idea of design system in frontend development, you can learn that more here: https://storybook.js.org/tutorials/design-systems-for-developers/ (I actually haven't read them, it's just one of the first result google gave me, but I know and use storybook.js and I can recommend their tool for creating a robust design system. Source: about 1 year ago

You basically work in a team of developers and designers that maintain a catalog of components for a company. Your team would make sure all the components are accessible, consistent across all platforms, and are being used correctly within your applications. Here is a deep dive for developers on how these systems are used, built, and maintained. Source: about 2 years ago

ℹ️ This article goes deep into design system foundational topics like tokens, themes, variants. If you aren’t sure what some of these are, I’d check out a guide or tutorial that covers those. - Source: dev.to / over 2 years ago

Storybook is a really good tool for building design systems. Ideally you'll want to distribute them library through npm. Here's a tutorial for it: https://storybook.js.org/tutorials/design-systems-for-developers/. Source: almost 3 years ago

I think supernova.io can help you out with having proper documentation that doesn't interrupt the workflows you have. You can now create documentation that is dynamic and connected to your sources of design truth, and that truly reflects the ideals of your design system. Source: over 2 years ago

I think the answer to all your questions is supernova.io. Source: over 2 years ago

Check out supernova.io we have made the delivery automation super easy. Supernova allows you to seamlessly export code and assets automatically from your design system when data change, with you being in full control of the process at any point. For example, you can open a pull request with new assets every time a new version of the design system library is published in Figma. Source: over 2 years ago