A design system needs a story and a source trail
Tokens are not enough if nobody can see what they mean or tell whether they came from a real source.
- Loopy
- Design-system evidence
I added Storybook so Loopy's foundations, primitives, and components could be inspected as a real system rather than a pile of values. I also taught Loopy to reject source-generated systems that contained no useful evidence.
A Figma link, a website, or a Storybook catalog now leaves a source trail. Loopy shows what it found, what it inferred, and what is still missing. A hollow token file no longer passes as finished work. When a client asks why something looks the way it does, I can point back to the evidence.