Case file 02 Design-system utility Working web app

Dee view

A token playground for enterprise dashboard systems.

Deeview turns design tokens from abstract values into something designers and developers can see, edit, test, and export immediately. The product gives token work a live enterprise UI context instead of leaving decisions trapped inside tables, swatches, and static documentation.

Deeview token editing, generated output, component preview, and dashboard workspace
Token controls, generated output, component testing, and a live dashboard preview in one workspace.

Problem

Tokens are decisions without context.

Design token work is often split across disconnected surfaces. Designers inspect values inside design tools, developers receive CSS variables or JSON later, maintainers document the rules separately, and accessibility issues are often found after tokens have already been applied.

The core question became simple: how can a team edit tokens and immediately understand their visual, functional, and implementation impact?

Platform-agnostic decisions Design tokens exist to express shared design decisions in a format that can move across tools, disciplines, and platforms.
Single source of truth Modern design systems use tokens to name and store reusable decisions across design and code.
4.5:1 contrast risk WCAG requires normal text to meet a 4.5:1 contrast ratio, which token editors can break quickly without live checks.

Product

A playground where token changes become visible.

Deeview lets users edit light and dark theme tokens, preview component behavior, inspect contextual layouts, and export theme-ready CSS variables, token JSON, and React usage snippets.

01

Edit relevant tokens

Component-specific controls keep users focused on the values that actually affect the selected UI pattern.

02

Preview real dashboard UI

Tokens are tested against enterprise scenarios like forms, analytics dashboards, navigation shells, and overlays.

03

Export usable outputs

The output panel generates CSS variables, token JSON, and React usage snippets from the same token source.

Interface model

Three zones. One feedback loop.

Left panel: token playground01
Center canvas: live preview02
Right panel: generated output03
Contrast safety checksAA
Undo and recovery actions3x
Light and dark token sets2

Architecture

Built around one shared token source.

Next.js handles the app shell. React renders the editor, preview, and output panels. Zustand stores tokens, selected component, preview mode, undo history, theme mode, and preferences. CSS variables apply token values to the preview surface.

Token editor
Zustand store
Preview CSS variables
CSS / JSON / React export

Screenshots

The product surface across editing, previewing, and export.

The screens show how Deeview turns token work into an immediate feedback loop: adjust values, inspect real interface impact, and export implementation-ready output from one workspace.

My role

From design-system idea to working tool.

  • Product strategyDefined Deeview as a token generator and preview playground for enterprise dashboards.
  • UX designStructured the app around a three-zone edit, preview, and export workflow.
  • Visual designCreated a restrained enterprise interface with dense panels and realistic dashboard surfaces.
  • Frontend developmentBuilt the Next.js app, token editor, preview system, output panel, custom picker, and interactive components.
  • Design-system logicMapped token groups to actual component usage so users can understand what each variable changes.

Future roadmap

From token playground to system intelligence layer.

01

More preview presets for mobile apps, marketing sites, admin tools, finance products, and AI interfaces.

02

A token dependency map showing which components and variants use each token.

03

Figma-friendly token export or sync with Figma variables.

04

Token versioning, snapshots, before-after comparison, and accessibility reports.