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: over 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

Headless UI came out a couple of weeks ago and since I'm using TailwindCSS too it was convenient to start using this too. Today I came across Radix UI, which is something similar to Headless UI. Source: almost 3 years ago

Nice. Have you seen Stitches? Together with Radix UI it's the foundation of Modulz, "Gutenberg for React" or "Figma with code" basically. Could be huge in a year or two from now.. Source: about 3 years ago