I will build a design system with tokens components and docs

I built and maintained the company-wide design system at a software company that ships to airlines and large enterprise groups. Not a folder of Figma screens, a system engineers actually used.

What you get:

• Design tokens: colour, typography, spacing, radius, elevation, in a structure that maps cleanly to CSS variables or Tailwind config
• A component library in Figma with variants and proper auto layout, so it survives contact with a real team
• States covered: default, hover, focus, disabled, loading, error
• Light and dark, if you need both
• Documentation that says when to use a component and when not to
• Optional: the same components written as React and Tailwind code, from the same hands that designed them

The point of a design system is that the fifth screen takes an hour instead of a day. That only works if the naming, the tokens and the docs are right, which is where most systems fall down.

Tell me what you have today, Figma file, existing code, or nothing at all, and I'll tell you which package fits.