Design System
Labelbox · Sr. Web Engineer and Designer
Shared UI for teams and agents
Overview
Internal products, POCs, and demos were reinventing UI — and agents were starting to generate interfaces without a shared contract. The design system is the product that fixes that: an npm component library, Tailwind tokens and themes, plus Cursor skills and rules so both humans and agents ship against the same decisions. It underpins customer products like Evals, Recursion demos, and the internal surfaces teams stand up every week.
Context
POCs and demos were forking UI under time pressure. Agents made that worse unless the system was machine-readable, not only human-documented.
How it evolved
npm library + Tailwind themes as the contract; Cursor skills and rules so agents compose the same components humans do.
Where it is now
Used across internal POCs, demos, customer-gated Evals, and Labelbox Recursion.
What it delivered
One npm library and token system so POCs and real products share the same UI language
Cursor skills and rules encode those contracts for agents — not only Storybook for humans
Adopted across internal POCs, demos, customer-gated Evals, and Labelbox Recursion
How it ships
Tailwind themes as the source of truth so theming stays portable across Next.js apps instead of forked CSS
Documented patterns where demos used to diverge — buttons, layout, density — so FDEs compose instead of redesign
Keeps GTM and product demos on-brand when speed would otherwise force one-off UI
Surfaces
npm library · Cursor skills/rules · Evals · Recursion · internal demos
Stack
Team
Systems ownership; used across internal products and demos