Skip to content

Magic · Case study

Three AI tools, three different looks, one design system.

A guest-services team on a cruise line gets three AI tools: a chat assistant for crew, a gateway that meters every request, and a tracing tool that records every answer. Each is good at its job. Each looks like a different company made it, because a different company did. And none of them tells a team lead the one thing that matters: is the assistant telling crew the truth?

Magic is my answer, built end to end as concept work. One token file themes all three tools from the outside, without forking any of them. The view nobody shipped, AI Health, I designed in Figma and then built in React, wired to live evaluation data.

  1. 01Three screens, one system
  2. 02Six steps from tokens to running code
  3. 03Evidence that shaped the decisions
The Magic AI Platform cover: one visual language across Open WebUI, the LiteLLM Admin UI and Arize Phoenix, for a cruise guest-services team.

The brief I set myself

No forks, no budget, and a real stack underneath.

Role
Product design, design system and front end
Timeline
Two days, November 2026
Stack
Figma variables, React and TypeScript, Open WebUI, LiteLLM, Arize Phoenix, Ollama
Brand
Magic, a fictional cruise line made for this concept
  1. 01Theme the tools, don’t fork themeach of the three ships its own releases, and a fork is a second product to maintain. So every change had to live outside the tool, in CSS and configuration, and survive the next upgrade.
  2. 02One source of trutha single tokens file feeds the Figma variables and generates the CSS for all three tools and the React app. Changing a colour is one edit, not four.
  3. 03Real answers at zero costtwo small Llama models run locally behind the gateway, with simulated per-token pricing so the spend screens have something honest to show.
  4. 04Accessible in both modesWCAG AA contrast in light and dark, keyboard paths through every control, and charts with a text alternative.

The product

Three screens, one system.

Screen 01

Guest Services Assistant

Open WebUI, themed with Magic tokens. Crew ask in plain language and get an answer drawn from the Guest Services Handbook, with the policy it came from attached.

The Guest Services Assistant in a themed Open WebUI: a crew member asks for the adults-only dinner cutoff on a port day, and the answer cites the Dining Reservations Policy and the Port Day Schedule.
  • Every answer cites its source documents, so crew can check before they promise a guest anything
  • Suggested follow-ups for the next likely question: draft a reply, show the waitlist, what if they miss all-aboard
  • Navy sidebar and cyan actions from the same tokens as every other screen
  • A standing reminder to check important details against the handbook

How it was built

Six steps from tokens to running code.

Chapter 01

Start from the token file

Before a single screen, one tokens file: primitives for raw values, semantic tokens for intent, Light and Dark modes. It became the Figma variables, and the brand cyan failed its first test there: 2.9:1 with white text, so primary actions moved to a darker cyan.

Colour primitives: navy for structure, cyan for identity, a neutral scale, and success, warning and danger ramps, each swatch labelled with its hex value.

Evidence

Data that changed the decisions.

What I learned, and what’s next

Designing for tools you don’t own means designing the adapters.

Every surface here belongs to someone else’s release schedule. So the design system is more than a Figma library: it is a token file, a build script and a small adapter per tool that maps that tool’s own variables onto Magic. When a release renames a class, the theme survives, because it targets variables and stable ids instead.

The fragile part is known and named. LiteLLM’s chart colours are hard-coded in its JavaScript, so the theme matches each value. If a release changes that list, the charts fall back to stock colours without breaking anything else.

Next: a larger golden set built from real human reviews in Phoenix, where every thumbs-down with a reason becomes a ready-made calibration case for the judge. Evals on a schedule, so new answers are scored as they arrive. And dark-mode screens in Figma, to match the dark mode already running in code.