PharmaGuide AI-Powered Design System
CASE STUDY · PHARMAGUIDE · 2026

One AI-powered design system for six product lines
Role Lead Product / UI-UX Designer, design system owner
Company PharmaGuide · 2026
Tools Figma · Vuetify 4 PRO UI Kit · Claude
Scope Tokens, components, patterns, templates, accessibility, docs and dev handoff

Overview

I've built design systems before, at LCBO and OLG, but this one is different. PharmaGuide runs six product lines (PharmaGuide, PHOX, PHANTOM, PYTHON, PHALCON and PHOENIX) and 30 sub-product apps, all built by developers in Vuetify. I took the official Vuetify 4 PRO UI Kit, rebuilt and restyled it in PharmaGuide's brand, then used Claude to turn it into a living, AI-powered design system: one that generates its own tokens and components, checks its own contrast, documents every decision and tells other AI agents exactly how to build with it.

The challenge

Every app looked like a cousin, not a sibling. Hub, Book and Dash each used a different blue. There were three different switch designs, a custom light sidebar with its own fonts, monospace small-caps labels, and per-app stat cards and badges.

Developers build in Vuetify first and design enhances after, so a system that lived only in Figma would always be one step behind. And any edit made directly in the purchased kit was wiped every time Vuetify pushed an update.
Start from Vuetify, speak PharmaGuide

I kept the purchased kit untouched and themed on top of it, so vendor updates can never overwrite our work. Every value comes from the kit itself: 69,007 Figma nodes, 1,380 variables in 19 collections and 401 Material Design icons.

On that structure I set PharmaGuide's voice: Montserrat for headings, navigation, buttons and labels; Roboto for body text and tables; pill-shaped controls, inset switches, 4px fields, no uppercase labels and a 12px minimum text size. I re-picked the teal ramp so white text passes WCAG AA, while the logos keep their original colour.
One system, six product lines

Colour is the only thing that changes between lines. Each line is a theme class, and every sub-product inherits it from its name: PHOXBook gets PHOX blue, PHANTOMAi gets PHANTOM purple. Nobody invents a palette again. The same buttons, the same two-tier top navigation and the same page structure ship in all six colours.
Accessibility, proven not promised

Contrast isn't a one-time check. The system computes its contrast tables live from the shipped hex values, so if a future palette change breaks AA, the table flags it straight away. Every line's primary colour and selected state passes with white text.
Patterns, not pages

Beyond the 579 themed Vuetify components, I designed a PharmaGuide pattern set: PgTopNav (a 96px identity band plus a 50px tab tier), PgSideNav, PgAppCard and PgAppGrid launchers, PgStatCard, PgStatusBadge, PgFilterChips and PgPageHeader. Four page templates give every new screen its starting shell.

Tables got the most care: one pattern, every state. Loading, couldn't load, refreshing, empty per filter, success and failure. A table isn't done until every state is built; only the columns, status words and empty-state copy change per app.
Making it AI-powered

This is where it goes beyond my previous systems. Claude works as the design system's engineer. It read the Figma kit, generated the tokens, built 178 live React components with their previews, and maintains the documentation. I make the design decisions; Claude applies them across tokens, components and docs, re-runs the contrast and parity checks, and records each ruling in a versioned changelog.

The README is written as binding rules with a Definition of Done. Any AI agent building a PharmaGuide screen reads it first and composes only from system parts, so AI-generated work stays on-brand by default, not by review.
Reflection

At LCBO and OLG, the design system was something people had to remember to use. Here, it is the starting point for every person and every agent that builds a PharmaGuide screen. The biggest shift wasn't the tooling; it was treating the rules themselves as the product.
↑Back to Top