Cboe Global Markets · 2024–Present

Design system tools for Claude

Role: Led the project and authored the toolkit
Timeline: 2024–Present
Selected outcome: For some repeatable page types, work that took a day can now reach an 80% starting point in minutes.

I built a set of design system tools that teammates can import into Claude with one command. They help people apply our conventions, create documentation, and get to a useful first draft faster.

The ask

Make the tools portable, easy to update, and useful without taking design decisions away from the team.

Design system tools for Claude project overview

My role

Led the project and authored the toolkit
Connected Claude and Figma through MCP workflows
Created reusable design guidance and generated governance pages
Ran workshops, office hours, and internal adoption

What I used

Claude Code · Figma MCP · Docusaurus · Markdown · Workshops

What changed

For some repeatable page types, work that took a day can now reach an 80% starting point in minutes.

Governance documentation that took hours now takes roughly ten minutes for repeatable page types.

What got in the way

02-01

The challenge

People were cautious about adding unfamiliar technology to an established workflow.

What I did

I ran workshops where teammates could try the tools on their own work and ask questions.

02-02

The challenge

Claims about saving time did not mean much without proof.

What I did

I compared the old and new workflows with real examples, then held regular AI office hours.

A closer look

Claude using Figma to create governance documentation — 03-01
Claude can reference the Figma work directly instead of relying on someone to describe it in a prompt.

Generated governance documentation — 03-02
The tools produce a first draft. The team still reviews it and makes the final decisions.

Markdown design guidelines from the AI toolkit — 03-03
The design guidance is written in markdown so people and AI tools can use the same source.

What I’d do next

04-01Track adoption and time savings over a longer period.
04-02Create different onboarding for designers, engineers, and content teams.
04-03Flag uncertain output so it gets extra review.