Atoms
Molecules
Organisms
Templates

Moha DS

Tokens, components, and automated governance across 3 product lines.

Overview01/

Three product lines were shipping with no shared foundation. This project built the system that connected them, from raw tokens to governed components across every surface.

Role

Led design and prompt engineering, defining token logic, component structure, and automated governance from zero foundation to production system.

Team

Lead designer + prompt engineer, full-stack developer

The challenge

No design system existed, inconsistencies were everywhere, and multiple roles depended on a foundation that was clear , scalable , and adaptable.

The approach

First, observe how every role actually works . Then run workshops to get everyone on the same page . Finally, build an atomic token structure that adapts to each role's needs .

Outcomes02/

6

Product lines

5+

Roles supported

AA+

Accessibility standard

Thissystembecamethefoundationforeverynewproject.Itadaptedtoanychallenge,absorbedresearchfindingswithoutbreaking,andstayedreliableandwell-documentedasthecompanyscaled.

Process03/
01/

Token foundation

Every design decision was captured as a semantic token, with automated contrast checks running in CI from day one.

Norawvaluesinproduction.Noexceptions.

02/

Component library

Every component was designed in Figma and matched 1:1 in Storybook, where any mismatch would trigger a CI failure.

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

Recurring patterns became templates. Forms, layouts, and common flows were built once and reused everywhere.

Atomic compositionradio
radio

Recurringpatternsbecometemplates.

04/

Multi-mode support

Every mode, from dark theme to localization, was built as a semantic token remap, not a duplicate system.

Username
username@emailaddress.com

Modesaresemanticremaps,notparallelsystems.

05/

Automated governance

Every pull request ran automated token checks. Hardcoded values blocked 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, scaling without breaking.

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

    Changing behavior was harder than building components.

  • Insights2/3

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

  • What’s next3/3

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

Swipe to explore

Moha DS — Multi-product component library case study