Reconnecting NEXT
Bringing the design and code behind Unica’s customer platform onto a shared foundation.
Situation
Unica NEXT is Unica’s customer platform. Its component library had drifted out of use: tokens were out of line, the documentation no longer worked as a living source of truth, and what left design was only partly systemised. The rest was interpreted or rebuilt in code, depending on who was working on it. That holds while the right people carry the context. It does not scale to a shared system, or to an LLM.
Approach
The first step was the foundation, not AI: an LLM does not remove ambiguity, it runs into it faster. We rebuilt the tokens as named decisions, with the repository as the source of truth and a custom plugin keeping Figma on the same tokens, and began pairing components one by one between Figma and React. Living docs show the components in the browser, Code Connect links each to its React, and automated audits flag drift instead of hiding it.
Result
The foundation phase is done. The system is reconnected: light and dark tokens from one source, more than forty components being paired one by one with live docs, a Figma-to-repo sync plugin and audits that surface every mismatch, around a hundred small ones logged for cleanup rather than buried. The team builds from one source now, instead of memory and interpretation. Making the patterns explorable and giving AI agents something reliable to build from is underway.