DESIGN SYSTEMS

FIGMA PLUGIN

ACCESSIBILITY

PERSONAL PROJECT

Kit Tint - Figma Plugin

A self-initiated Figma plugin, from idea to Community launch, that themes Material 3 and Carbon from one brand color.

THE CONTEXT

Overview

A Figma plugin, with a companion web app, that takes 1–3 brand colors and themes the popular design system a designer picks (Material 3 or IBM Carbon in V1) into a complete, accessible, multi-mode theme, exported for Figma, code and AI agents.

ROLE

Solo designer & builder

TIMELINE

TBD

TOOLS

Figma, Figma Plugin API, Claude Code

THE CONTEXT

Why I built it

At BOK Financial I owned the design system behind three bank brands. Theming it meant mapping more than 300 color variables across four modes, and checking contrast pair by pair, by hand.

Kit Tint is the tool I wished I'd had: give it one brand color, and it themes a complete, production-grade kit in seconds.

THE PROBLEM

A palette isn't a theme

Picking a brand color is easy. Making a whole system work with it is not. Most tools stop at a palette and leave the hard parts to the designer.

Scales

One hex has to become a full tonal ramp that holds up in light, dark and high-contrast modes.

Mapping

Someone still decides which step becomes surface, text, border and action, in every mode, in every system's own token names.

Real contrast

Contrast gets checked per swatch, not per foreground and background pair that components actually use.

Awkward brands

Yellows, light teals and oranges can't carry white text, and red brands collide with error colors.

MY APPROACH

Building the system behind the screens

I owned 3.0 end to end, from token architecture to the guidelines that let product teams build independently.

Before touching a single component, I established shared naming conventions for color variables. Every brand's palette lived in one semantic structure, and every component inherited from those tokens instead of hardcoding brand values.

Tokens first, components second is what let two brands and four platforms converge on one system instead of three systems wearing the same components.

WHERE IT FITS

A gap in the tools designers already use

Several tools turn a color into a palette or a Material theme. None I found themes the official kits designers already work in, and none covers Carbon.

System Architecture

Tokens

Figma

Android

iOS

Web

React Native

iOS

Android

Web

React Native

iOS Design System

207

Components

2

Theme variants

The iOS system was built on Apple's Human Interface Guidelines, then themed with BOKF's brand colors and extended with the component variants our banking flows needed. The result: native components that felt genuinely native to iPhone, not a web UI wrapped in an app shell. While still carrying BOKF's identity.

Key Contributions

New 3.0 modernization

Light and dark mode color variables

Design documentation

CHANGING DIRECTION

From a web tool to a Figma plugin

I started with a web app that generated themes and exported tokens. Prototyping the Figma side made the real job clear: design system designers live in Figma, and the value is in the kit updating, not in a file to import.

The platform pushed the same way. Figma's public API can't create files and limits variable writes to Enterprise plans, but a plugin can write variables in any file the designer opens. The plugin became the product, and the web app became its front door.

KEY DECISIONS

How it works

01

One engine, one adapter per system

The engine builds scales and assigns neutral roles like "brand button fill" and "text on brand". Each adapter translates those roles into one system's names: primary in Material, $button-primary in Carbon. A new system is a new adapter, not a rebuild.

02

Scales built in a perceptual color space

Tonal ramps are built in OKLCH, so each step looks evenly spaced to the eye and keeps the brand's hue from light to dark.

03

Contrast is the gate

Every real text and background pair is checked against WCAG 2.2 in every mode. Failing pairs loop back to role assignment until they pass, and the plugin says what it changed.

04

Theme the kit people already have

Instead of publishing a kit of its own, Kit Tint detects the official Material 3 or Carbon kit in the open file and rewrites only its color variables. Carbon gets a one-click reset to its original blue.

THE HARD BRAND

When the brand can't carry text

A yellow like #ECBB51 is too light to use as a button color with readable text. Kit Tint keeps the hue but moves Primary to a deeper tone, saves the bright yellow for containers and accents, and lists every pair it fixed.

Red brands had the opposite problem: they looked like errors. The engine now keeps the error hue at least 30° away from the brand, so a warning never reads as a brand moment.

THE FRONT DOOR

A web app to try it first

The web app runs the same engine. Anyone can preview their brand across every mode, read the contrast report, and copy CSS variables, design tokens or an AI-agent spec, then follow the steps to theme their kit in Figma.

BUILDING WITH AI

A designer shipping code

I'm a designer, not an engineer. I built Kit Tint with Claude as my engineering partner: I owned the problem, the color decisions, the UX and the testing in real kits, and AI wrote and refactored the code.

RESULTS

What shipped

49

Material 3 color roles themed in 6 modes

20

Carbon brand tokens in 4 themes

1 click

From brand color to a themed kit

[#]

Installs in the first month

"[ TESTER QUOTE ]"

WHAT'S NEXT

Beyond color

Atlassian and Microsoft Fluent 2 support, one system at a time, then typography theming and an MCP server so AI agents can read a brand's rules directly.

Next Case Study

Republic Wireless - checkout experience

Conversion rate - 21%

FramerIt Website