This article discusses developing and implementing design system components using Tokens Studio (formerly Figma Tokens), and how to expose tokens to design system consumers so they can use them as well.

You’re using tokens and you don’t even know it. One of the goals of a design system is to close the gap between multiple disciplines and especially between design and development. With the features and tools Figma provides us, this gap becomes smaller. But what if I tell you with the proper integration of design tokens, we can make this gap closer than it was ever before. Let’s talk about tokens and how it can level up your design system.

In this article, we share the most common pitfalls we see companies make who are planning or stuck in a failing design system project.

A design system is a set of tools, processes, guidelines and philosophies that combine to drive how a team designs a product. The purpose of a design system is to not only systematize product development, but to also establish the processes that teams use to design, develop, test and more. As a tool, it sets the foundation for your digital experiences and products to look and feel consistent to users, increase efficiency and quality for your teams, and protect your brand across all your touchpoints in the market.

Named Design Contexts and Design Contexts as Code (DCaC) can greatly simplify the process of creating a scalable design system that is easier to understand and more friendly to change.