Robert TaFounder & CEO, Clarity · Building Hyper-Personalized Agents

The Living Design System Trick I Stole From Meta

18 Jun 2026 · 1 min

Watch on YouTube

0:59

In this video segment, Robert Ta explains a workflow for creating a "living" design system that stays in sync with a mobile app. He demonstrates how he uses Cloud Code to access the mobile app repository and generate a design‑system HTML file containing all UI components. The app is also integrated with the Clarity API, enabling easy updates. To keep the component tree current, he proposes maintaining a Cloud‑MD file that is updated whenever new components are added or existing ones are modified during code check‑ins, ensuring the design system file automatically reflects the latest component structure.

Chapters

This is interesting. What'd you think of this? Which is, um, the Living Design System meta. I love this. I started doing this right away. Uh, and I like, yeah, I just built such a cool design system. Here, I'll show you one of the ones we made for a client. They just changed their brand guidelines and using this, like I just— we're servicing their mobile app and integrating their mobile app with Clarity API. And so using this. I was able to easily just go to the mobile app repo, talk to it with Cloud Code and create a design system HTML file that has all the components we would use in the app. And then I had the thought that, hey, anytime we create new components, we should check this, like a Cloud MD file, that harness should evolve. We should check this whenever we're checking in new components or there's a new component to be made, we cross-reference it and then evolve it as part of this. Design system. So the component tree all lives up to date in this file that is updated in the codebase, which I thought was really, really cool.