Design system for speed, consistency and quality

Design System

Inconsistency and slow turnaround are two big risks in design work. I built this system to directly address both by creating a reusable foundation that cuts ramp-up time and ensures quality holds across every client project.

Role: UX/UI Designer and Owner

Duration: 3 months

Status: Published on Figma

Results: 120+ Usages, 800+ Views, 4+ Saves

Problem

As a designer, I could always pull foundations and components from past projects, but adapting them meant manually updating colors, typography, and styles every time.

 

I needed a system with linked variables, one where customizing for a new project takes minutes, not hours.

Research

I studied Material 3, Porsche Design System, and Figma's Simple Design System not to copy, but to understand what makes a system work.

 

Material 3 - informed how I structured my token hierarchy

Porsche's documentation style - influenced my do's and don'ts approach

Figma's system - reminded me to keep things simple

 

I carried all three principles into how I built and documented this system.

Design solution

The system is organized into 3 layers as demonstrated below;

Primitives

Primitives are the raw values (tokens); the base colors, numbers, and scales that everything else is built on top of.

primitives

Foundations

Foundations documents the core variables: color tokens, typescale, spacing, border radius, breakpoints, and themes, all built from the primitives.

Foundations

Components

Components are built on top of those foundations, inheriting their variables so any customization at the token level flows through automatically.

Image of component structure

Solution Illustration

Primitives, foundations, and components structure means customizing for a new project happens at the token level and cascades through automatically. No manual updates, no rebuilding from scratch, consistency all through.

Results

Since publishing the system on Figma Community, it has received 800+ views, 120+ usages, and 4 saves. Picked up by other designers without any promotion. However, with no comments or feedback so far, it's hard to know if users ran into friction.

 

My next step is to understand how designers are using the system and identify any pain points in their experience.

Click to explore the design system

Thanks for reading. Check out more of my work

Design Portfolio

Design system

Have a question, an idea, or just want to say hi? Let’s connect.

Email

LinkedIn

Resume

© 2026 Cathy Njoki

Design system for speed, consistency and quality

Design System

Inconsistency and slow turnaround are two big risks in design work. I built this system to directly address both by creating a reusable foundation that cuts ramp-up time and ensures quality holds across every client project.

Role: UX/UI Designer and Owner

Duration: 3 months

Status: Published on Figma

Results: 120+ Usages, 800+ Views, 4+ Saves

Problem

As a designer, I could always pull foundations and components from past projects, but adapting them meant manually updating colors, typography, and styles every time.

 

I needed a system with linked variables, one where customizing for a new project takes minutes, not hours.

Research

I studied Material 3, Porsche Design System, and Figma's Simple Design System not to copy, but to understand what makes a system work.

 

Material 3 - informed how I structured my token hierarchy

Porsche's documentation style - influenced my do's and don'ts approach

Figma's system - reminded me to keep things simple

 

I carried all three principles into how I built and documented this system.

Design solution

The system is organized into 3 layers as demonstrated below;

Primitives

Primitives are the raw values (tokens); the base colors, numbers, and scales that everything else is built on top of.

Base tokens

Foundations

Foundations documents the core variables: color tokens, typescale, spacing, border radius, breakpoints, and themes, all built from the primitives.

Foundations set-up

Components

Components are built on top of those foundations, inheriting their variables so any customization at the token level flows through automatically.

Components set-up

Solution Illustration

Primitives, foundations, and components structure means customizing for a new project happens at the token level and cascades through automatically. No manual updates, no rebuilding from scratch, consistency all through.

Results

Since publishing the system on Figma Community, it has received 800+ views, 120+ usages, and 4 saves. Picked up by other designers without any promotion. However, with no comments or feedback so far, it's hard to know if users ran into friction.

 

My next step is to understand how designers are using the system and identify any pain points in their experience.

Thanks for reading. Check out more of my work

Design Portfolio

Design system

Have a question, an idea, or just want to say hi? Let’s connect.

Email

LinkedIn

Resume

© 2026 Cathy Njoki

Design system for speed, consistency and quality

Design System

Inconsistency and slow turnaround are two big risks in design work. I built this system to directly address both by creating a reusable foundation that cuts ramp-up time and ensures quality holds across every client project.

Role: UX/UI Designer and Owner

Duration: 3 months

Status: Published on Figma

Results: 120+ Usages, 800+ Views, 4+ Saves

Problem

As a designer, I could always pull foundations and components from past projects, but adapting them meant manually updating colors, typography, and styles every time.

 

I needed a system with linked variables, one where customizing for a new project takes minutes, not hours.

Research

I studied Material 3, Porsche Design System, and Figma's Simple Design System not to copy, but to understand what makes a system work.

 

Material 3 - informed how I structured my token hierarchy

Porsche's documentation style - influenced my do's and don'ts approach

Figma's system - reminded me to keep things simple

 

I carried all three principles into how I built and documented this system.

Design solution

The system is organized into 3 layers as demonstrated below;

Primitives

Primitives are the raw values (tokens); the base colors, numbers, and scales that everything else is built on top of.

brand base tokens
grey base color tokens
radius base tokens

Foundations

Foundations documents the core variables: color tokens, typescale, spacing, border radius, breakpoints, and themes, all built from the primitives.

Foundations set-up
Foundation set-up

Components

Components are built on top of those foundations, inheriting their variables so any customization at the token level flows through automatically.

Components set-up

Solution Illustration

Primitives, foundations, and components structure means customizing for a new project happens at the token level and cascades through automatically. No manual updates, no rebuilding from scratch, consistency all through.

Results

Since publishing the system on Figma Community, it has received 800+ views, 120+ usages, and 4 saves. Picked up by other designers without any promotion. However, with no comments or feedback so far, it's hard to know if users ran into friction.

 

My next step is to understand how designers are using the system and identify any pain points in their experience.

Click to explore the design system

Thanks for reading. Check out more of my work

Design portfolio

Design system

Have a question, an idea, or just want to say hi? Let’s connect.

Email

LinkedIn

Resume

© 2026 Cathy Njoki