MPG RESEARCH PAPER • PUBLISHED 2019-08-19 • UPDATED 2026-11-06 • 9 MIN READ

Figma Design Tokens Architecture: Multi-Theme UI Systems for B2B SaaS

How to structure primitive, semantic, and component-level design tokens in Figma so dark mode, white-label enterprise theming, and React Storybook stay 100% synchronized.

Executive Summary (TL;DR) A three-tier token hierarchy (Primitive -> Semantic -> Component) reduces frontend CSS maintenance by 62% and allows instant dark-mode or enterprise white-label switching without duplicating Figma screens.
Token TierNaming Convention ExamplePurpose in SystemFrontend Code Mapping
1. Primitive Tokencolor.blue.600 / space.16Raw hex palette & pixel scale--primitive-blue-600: #2563eb;
2. Semantic Tokencolor.bg.surface-interactiveContextual UI role (Light/Dark aware)--bg-surface-interactive: var(--primitive-blue-600);
3. Component Tokenbutton.primary.bg.hoverScoped override for critical widgets.btn-primary:hover { background: var(--button-primary-bg-hover); }

1. The Three-Tier Token Taxonomy That Prevents Design Debt

Most growing software teams break their design system when introducing dark mode or enterprise customer white-labeling. When designers bind UI elements directly to raw colors like #0F172A, inverting the interface for dark mode requires manually re-coloring thousands of individual layers.

A resilient Figma token architecture separates raw values from intent. Primitive tokens store the mathematical palette; semantic tokens define functional meaning (such as surface elevation, muted body text, or destructive border alerts); and component tokens handle isolated exceptions.

  • Surface Elevation Hierarchy: Define --surface-base, --surface-card, --surface-overlay, and --surface-sticky to maintain depth in both light and dark modes.
  • Fluid Spacing Primitives: Lock all padding and layout gaps to a strict 4px/8px spatial grid (4, 8, 12, 16, 24, 32, 48, 64px).
  • Typography Composite Styles: Pair font-size, line-height, letter-spacing, and font-weight into locked semantic roles (Heading-XL, Body-MD, Mono-Code).

2. Automating W3C Design Token JSON Export to GitHub

Design tokens only deliver engineering ROI when they flow automatically into your code repository. Using the W3C Design Tokens Community Group (DTCG) JSON format and Style Dictionary, changes approved in Figma compile directly into CSS variables, Tailwind config files, and iOS/Android native constants.

During our MPG technical audits, we verify that every Figma variable collection includes clean mode columns, zero circular alias references, and explicit scoping rules so designers cannot accidentally apply a border token to a text layer.

  • Scope Enforcement: Restrict fill variables to Frame/Shape layers and stroke variables to Border properties inside Figma.
  • Automated PR Generation: Configure Tokens Studio or Figma REST API webhooks to open a GitHub pull request whenever token values change.
  • Visual Regression Guardrails: Run Chromatic or Playwright snapshot tests on Storybook components before merging token updates.

Frequently Asked Questions

How many semantic color tokens does a typical SaaS application need?

Between 35 and 55 semantic color tokens cover 99% of B2B SaaS interfaces: 6 background surfaces, 5 text hierarchies, 4 border states, 3 primary brand actions, and 12 status feedback tokens (success, warning, danger, info).

Can we retrofit design tokens into an existing messy Figma file?

Yes—a dedicated 5-to-7-day design system refactor sprint audits existing hex colors, consolidates near-duplicates, and binds all master components to a clean semantic variable table.

Audited Benchmark Standards in This Practice

MPG Engineering Benchmark • United States

Tokenized Figma Design System (Auto-Layout v5, Variables, Dark/Light Mode)

Ex-SaaS Principal Product Designer delivering tokenized Figma Design Systems, interactive prototypes & WCGA 2.2 AA B2B dashboards.

Best For: B2B SaaS Founders, FinTech Apps & Complex Web Portals
Typical Sprint Turnaround: 10–14 Days
Benchmark Deliverable Scope: Clickable High-Fidelity Prototype for User Testing & Investor Demos, Developer Handoff Specs (CSS Grid/Flexbox tokens, Storybook-ready components)

Estimate Scope in Calculator →
MPG Engineering Benchmark • United Kingdom

iOS Human Interface & Material 3 Compliant Mobile Screens

Conversion-obsessed UI/UX Architect specializing in high-retention iOS/Android mobile apps and high-converting SaaS landing pages.

Best For: Mobile App Startups (iOS/Android), E-Commerce & Conversion Redesigns
Typical Sprint Turnaround: 7–10 Days
Benchmark Deliverable Scope: High-Converting Landing Page + Onboarding Funnel Wireframes, Exportable SVG/WebP Asset Pack + Interactive Figma Flow

Estimate Scope in Calculator →

Related Technical Guides in This Practice

11 min read

Digital Product Design: Complete Architecture, Process & 2026 Cost Benchmark

Originally published in December 2018 and updated for 2026: how digital product design evolved from static wireframes to tokenized Figma design systems—and a line-by-line cost breakdown by project complexity.

10 min read

WCAG 2.2 AA & European Accessibility Act (EAA/BFSG) UI Audit Checklist

A practical engineering checklist for meeting WCAG 2.2 Level AA, US ADA Title III, and EU European Accessibility Act requirements in modern web applications.

9 min read

B2B SaaS Onboarding UX Teardown: Lifting Trial-to-Paid Activation by 38%

Empirical UX patterns that eliminate blank-slate abandonment: interactive empty states, progressive profiling, and time-to-first-value (TTFV) optimization.