Design System

Design System

Design System

SaaS

Collaboration

Collaboration

SaaS

Design System

OVERVIEW

TYPE

Design System

ROLE

Product Designer

YEAR

2026

TYPE

Design System

ROLE

Product Designer

YEAR

2026

I designed Kobe Platform’s design system from scratch, first alone and then with the platform’s two other designers. Today it powers App Studio, Nodo and the dashboards, in light and dark mode.

I designed Kobe Platform’s design system from scratch, first alone and then with the platform’s two other designers. Today it powers App Studio, Nodo and the dashboards, in light and dark mode.

THE PROBLEM

With three designers building modules in parallel, each could end up with its own buttons and patterns, and engineering would build the same things twice. We needed one language for design and code.

WHAT I DID

Structure, naming and foundations on my own; components, governance and handoff with the team.

IMPACT

1

1

shared library for three designers and every module

Design System

Design System

Design System

SaaS

Collaboration

My process

01. Context & Role

02. Foundations

03. Components

04. Governance

05. Engineering

01. Context & Role

01. Context & Role

01. Context & Role

One rule from day one: the same names our developers use in code.

One rule from day one: the same names our developers use in code.

One rule from day one: the same names our developers use in code.

I started from a blank file and defined the structure, naming and rules the team still follows. I chose shadcn/ui and Tailwind, the same base as engineering, so Figma maps directly to code and every change happens once, in the library.

02. Foundations

02. Foundations

02. Foundations

AA

AA

AA

WCAG contrast in both themes

Dark-first: dark is the default theme, and light is its inversion.

Dark-first: dark is the default theme, and light is its inversion.

Dark-first: dark is the default theme, and light is its inversion.

The rules every screen inherits: responsive and working in both themes.

Neutral tones let content stand out, with a dedicated palette for buttons and AI. Tokens have three levels:

  • Base: raw colors on a 0–1000 scale.

  • Semantic: meaning, like error, success or AI.

  • Specification: the only level used in screens, like color-button-bg-primary-default.

Screens are tied to meaning, not hex codes, and developers get the names they already use.

03. Components

03. Components

03. Components

Components cover real cases without multiplying.

Components cover real cases without multiplying.

Components cover real cases without multiplying.

Components adapt through sizes, variants, states and slots instead of being duplicated, and carry a status (in construction, in review, in production, discarded) so anyone knows what’s safe to use.

  • 3 sizes, S to L.

  • 5 variants, including brand for AI.

  • 6 states, including keyboard focus.

04. Governance

04. Governance

04. Governance

3

3

3

versions of the same date picker, before the new habits

Independence had a cost: every module ended up with its own date picker.

Independence had a cost: every module ended up with its own date picker.

Independence had a cost: every module ended up with its own date picker.

Working separately, we ended up with duplicates for engineering and slightly different experiences for users. So we agreed on a few habits:

Weekly design system call

Each designer shows what they added, so we reuse before creating.

Every module from day one

New components consider Nodo, the Dashboard and App Studio first.

Slots over free-form

Easy to adapt, hard to misuse.

One library, reviewed

One shared Figma library; new components are reviewed before they go in.

05. Engineering

05. Engineering

05. Engineering

Designers vibe code with Claude on the same components developers use.

Designers vibe code with Claude on the same components developers use.

Designers vibe code with Claude on the same components developers use.

Every feature brief points to the library: reuse components, use semantic tokens, check contrast and test both themes. The system lives in three places:

Figma

The source of truth for tokens and specs, with every component’s states, scenarios and annotations.

Storybook

React components consumed as @kobe/platform-ds, one story each, with live Controls and a dark/light theme switcher.

GitHub

The source code, issues and pull requests.

Outcome

A system the whole team builds on, not just a library.

A system the whole team builds on, not just a library.

A system the whole team builds on, not just a library.

  • Faster handoff: fewer design QA issues and shorter merge cycles.

  • Consistent flows across every module.

  • Edge cases caught earlier, because designers prototype in code.

A design system isn’t finished when the library ships: the agreements around it are what turn three designers in parallel into one team.

In constant

motion

© 2026