WorkDesign systems
One Angular source. React at parity. Every team starts from the same place.
Product teams kept rebuilding the same components, and the UI drifted from team to team. I initiated and co-led a standard Angular and React component library, and personally designed and built 13+ of its components. Angular is the source of truth, React matches it, and behavior follows WCAG AA.
- The hard part
- Two frameworks can't drift apart. One has to lead, and the other has to match its behavior, not just its looks: keyboard support, states, and ARIA.
- The decision
- Make Angular the source of truth and hold React to functional parity. Then handle release and governance jointly, through a shared roadmap.
- Where it stands
- Frontend developers pointed to the libraries as a way to cut repeated implementation work. They're heading for their first official release.
The system
Labcorp's enterprise design system lives in two places that must never disagree: Figma libraries for design, and a Bootstrap-based SCSS framework for code. I co-lead both. Roughly 30 designers and researchers work from it, and the majority of internal product teams ship with it.
Why a component library
Product teams kept rebuilding the same components, and the UI drifted from team to team. I initiated a standard Angular and React component library to stop that, then co-led it.
I personally designed and developed 13+ of its reusable components. Angular is the source of truth; React is held to functional parity. The same keyboard model, the same states and the same WCAG AA expectations apply in both, so teams get identical behavior whichever stack they use.
Getting to release
The libraries are in beta and preparing for their first official release: versioned NPM packages, Storybook documentation, Figma Code Connect so what a designer inspects is what an engineer imports, adoption guidance, and a roadmap governed jointly with engineering.
Starting apps on the system
I integrated the SCSS framework and both component libraries into a Replit starter template, planned for distribution to internal builders. New applications start on a consistent, Labcorp-aligned foundation instead of from scratch.
Keeping it current with agents
A system this size is only useful if changes reach every layer. Our team keeps skills and Markdown design guidelines that spell out the rules, and I run several agents at once to find and fix discrepancies across Figma, SCSS, Angular, React and Storybook. It turns system updates that took months into days. I decide the change and review the result.