Airokit
Afiniti's internal component platform: a typed monorepo of 50+ React components with Storybook-driven development and automated visual regression testing.
The problem
Multiple product teams at Afiniti were each building their own version of the same UI patterns, with no shared, tested source of truth to pull from, and no safety net to catch a breaking change before it reached a consumer team.
Our approach
We built Airokit as a platform, not a component library bolted on after the fact: a single, fully typed monorepo with Storybook-driven development at its centre, so every component shipped with a documented, visually verifiable state before any consumer team touched it.
What we built
A monorepo housing 50+ production-grade React components, each typed end to end and documented in Storybook. Automated visual regression testing runs against every change, catching unintended UI drift before it reaches the multiple product teams consuming the library.
The outcome
Airokit shipped with zero breaking changes across its consumer teams, giving Afiniti's product teams a shared, tested component foundation instead of each rebuilding the same patterns independently.