Work · Tarva · 2025–2026 · Operational · v2.0

Tarva’s own infrastructure · supports product delivery · not a client engagement

@tarva/ui

One component library, many brands, light and dark.

@tarva/ui: storybook getting started

The problem

Every Tarva and client product needed the same primitives under a different identity, and per-brand forks with hand-written tokens drifted within weeks.

The system

Tarva's component library: accessible primitives, token-driven theming, charts, layouts and patterns, with a generator that emits CSS tokens and Figma variables from one typed palette, plus an MCP server so agents use the right props.

Outcome

Product brands share one set of primitives and swap their whole identity, light and dark, from a single bundle instead of maintaining forks.

Proof

@tarva/ui is operational and used across Tarva and client projects.

Role

@tarva/ui is Tarva's own library. Tarva architected and led its AI-assisted development and led information architecture, UX/UI, brand and design.

Supporting stack

React 19 · TypeScript · Tailwind v4 · Radix · Storybook · Figma Code Connect · MCP

Scale

500+ named exports · 20+ projects

End of page · return to main content