Design System Docs: Put Them Where the Work Happens
Design systems documentation raises a recurring set of questions: where should components be cataloged, should that live in Figma or a separate wiki, and how much time should go into building a large reference site? The harder problem is that every new destination for information adds a new place people have to remember to look. Designers need one resource, engineers need another, and platform-specific teams need their own special case. For anyone outside the core design systems team who just wants to ship a feature, that sprawl becomes a barrier.
The most practical answer after struggling with these questions for years is to meet colleagues where they already are. For most organizations, that place is Slack. Instead of pushing people toward yet another bookmarked link or standalone tool, the design system can come to them in the conversation where they’re already working.
Answering Questions With Slackbot
Custom Slackbot responses are a surprisingly effective way to surface design system information without introducing a new tool. The setup in Slack is straightforward: from the organization settings, open the “Customize” option in the dropdown.

Selecting “Slackbot” from the “Customize your Workspace” tab reveals existing custom responses, where a new one can be added:

The key is the \n escape sequence, which breaks the response onto separate lines. Once saved, the response can be tested in a direct message to yourself:

This approach was initially used for a broad color me trigger that pastes the full set of color variables and hex values. Because that response takes up so much space, separate answers for individual colors like blue and purple were added as well.
Extending the Idea
The Slackbot trick is only a starting point. It points toward a broader principle: design systems tooling doesn’t have to live exclusively in dedicated apps and portals. Chat tools like Slack are full of opportunities to make design system work easier, and there is plenty of room to improve daily workflows within these familiar environments.



