Back to work
Atoms
Molecules
Organisms
Templates

Moha DS

One foundation for 6 product lines. The rules enforce themselves.

Overview01/

What started as a component library became how the company ships. Six product lines now start from one governed foundation, and the rules hold without anyone policing them.

Role

Lead system architect. I defined the token logic and the component structure. I built the automation that enforces both.

Team

Lead designer, researcher, frontend developer, backend developer

The challenge

Three product lines were shipping with no shared foundation . Each fix caused new mismatches. Each team worked from memory.

The approach

Watch how each role actually works , agree on one shared language, then build tokens that hold that agreement in code.

Outcomes02/

6

Product lines

5+

Roles supported

AA+

Accessibility standard

Everynewprojectstartsfromthisfoundation.Threeyearson,itabsorbsnewresearchfindingswithoutbreaking.

Process03/
01/

Token foundation

Every design decision lives in a semantic token. Contrast checks ran in CI from day one.

Norawvaluesinproduction.Noexceptions.

02/

Component library

Every component exists twice, in Figma and in Storybook, matched 1:1. Any mismatch fails the build.

baseTextInput states
Figma
Label
Example goes here
1:1 sync
Storybook
Label
Placeholder
Example goes here
Components / BaseTextInput
Controls
state"default"
placeholder"Placeholder"
helperText"Example goes here"
disabledfalse
requiredfalse

Componentparityisnotoptional.

03/

Templates

Forms, layouts, and common flows were built once as templates and reused everywhere.

Atomic compositionradio
radio

Recurringpatternsbecometemplates.

04/

Multi-mode support

Dark theme and localization. Each mode is a token remap, not a second system.

Username
username@emailaddress.com

Modesaresemanticremaps,notparallelsystems.

05/

Automated governance

Every pull request runs token checks. A hardcoded value blocks the merge.

Automated governance
Merge blocked
border-radius: 15px
padding: 18px
color: #25272C

Ifthesystemcan'tenforceitautomatically,theruleisn'tworthhaving.

06/

Production

Six product lines share one system. Every new project starts from the same governed foundation.

buttonLabel
Primary
buttonLabel
Secondary
buttonLabel
Border
buttonLabel
Disabled
Reflections04/
  • Challenges1/4

    Changing behavior was harder than building components.

  • Insights2/4

    The real value was speed and a shared language across every role.

  • What wasn’t built3/4

    A formal onboarding program. People learned the system through pairing and PR reviews. Enforcement taught the rules, but a real curriculum would have spread them faster.

  • What’s next4/4

    Automated changelogs, a public Storybook, and adaptive tokens beyond light and dark.

Swipe to explore

Moha DS — Multi-product component library case study