I built Solaris, a token-first design system that keeps enterprise products consistent. Topaz Teal and Bookmania set the brand. MUI and React components read semantic tokens, never raw values, so every product stays in sync.
Company
J.P. Morgan Chase
Role
Senior Product Designer, Workplace Solutions
Years
2024-2026
Design SystemMUI + ReactToken-FirstBookmania · Barlow · Open SansWCAG AAStorybook
About the visuals
The Solaris you see on this site is my recreation, rebuilt with Claude Code. It's very close to the system I created and managed at J.P. Morgan Chase, but it isn't a 1:1 copy, and the original stays internal.
Problem
Four products. Four visual languages. One brand.
Teams were rebuilding the same buttons, inputs, tables and modals in every product. Each version drifted. Button radii varied, focus rings came in three colors, and contrast slipped below AA on the busiest flows.
There was no token layer, so every brand refresh, accessibility audit or type update meant fixing the same patterns four times. Work slowed down and the design debt kept growing.
4
Products without shared primitives
40+
Inconsistent button variants in the wild
0
Cross-team token alignment at project start
Solution
Tokens at the root. Components composed from them.
Solaris starts with primitive tokens for color, spacing, type, elevation and motion, then builds up. Components read semantic tokens, never raw values, so a brand or theme change ships in a single PR. Three color families (Topaz Teal, Brown, BrandGreen) map straight to interaction states through CSS custom properties.
Every component ships with accessibility docs, a Storybook page and defined keyboard behavior. AA contrast is enforced at the token layer. If a pairing fails at build time, the PR doesn't merge.
Light and dark themes switch in one click, and responsive tokens cover four breakpoints and four grid systems.
Foundation tokensTopaz Teal · Brown · BrandGreen
Token System
If it's a decision, it gets a name.
Primitive tokens hold raw values. Semantic tokens give them meaning. Component tokens apply them in context. No component hardcodes a color, space or radius, and that is what makes the system safe to refactor at scale.
Typography Scale3 Typefaces · 7 Size Steps
Spacing & Borders8px Base Unit · 5 Radii · Responsive Grid
From component library to enterprise infrastructure.
Solaris grew from a shared component effort into product infrastructure. It supports 4 enterprise products with 476 published components (250+ in the core library) and 341 design variables. The usage numbers show how much teams lean on it: 250k+ table cell instances, 124k+ AG-grid inserts, 9k inserts a week and 93 active teams a year. One primary system owner runs it. That's me. Governance and token architecture did the scaling.
476
published components
341
design variables
615k+
token instances
250k+
table cell instances
124k+
AG-grid inserts
9k
weekly inserts
93 active teams yearly
Adoption held steady after launch. Teams kept coming back to Solaris as their main source of UI components all year.
4 enterprise products
One system under four products, at 100% adoption across 15+ squads. A brand or accessibility update reaches all of them in one change.
1 primary system owner
Enterprise-scale adoption, run by a team of one. Governance and token architecture let one person's work carry the whole organization.
Process
Audit. Define. Ship. Maintain.
Six phases from inventory to adoption. I mapped what already existed across four products, distilled it into three token tiers, and shipped components with Storybook docs teams could use without booking a meeting.
01
Component Audit
Inventory 4 products · catalog drift, duplication, and debt