Who needs a Figma Library?
Introducing the Astryx Figma Library, built and self-maintained by a Night Watch that keeps it in sync with code on every dot release.
Well, we got one for you here!
To be honest, we contemplated for a long time if we even needed a Figma library. Internally we saw a sharp 95% drop in our weekly insertion rate. And most designers around us are designing through code and not canvas. We wondered about the place that Figma serves in our design workflow…
What made us still want to give it a try is when we found ourselves still turning back to Figma in certain situations. It is still the fastest way to do rapid explorations and create visual assets. Though we no longer use it as a speccing or hand off tool, it's still useful as a sketchpad. Plus seeing how quickly community built Figma libraries popped up really motivated us. (Shoutout to Lee and Adrian. Go check out their libraries too!)
We decided that we would put something out if we can generally automate the building and maintenance of it. So that's what we did! We are putting out this Astryx Figma Library as an experiment on two fronts:
- Is there still a place for Figma library in the designer's workflow?
- Can we automate it so the effort to reward trade off is in balance?
Figma Librarian Night Watch
This Astryx Figma library is largely built and will be maintained by a Night Watch (Astryx's cron job set up) called the Figma Librarian. It is connected to the Figma MCP and is given a set of component build skills that includes our build preferences like, "always use a slot feature in reflection of a react node in code". The librarian checks for relevant changes to the system on every dot release and self maintains the library so it can stay up to date.
FigmaAIRelease