UX + AI

UX + AI

AI-ready Design Systems

A practical guide to making design systems work with AI: what good context looks like, and three ways to set it up using Claude with Figma MCP, Skills, and Claude Design.

Ileana's avatar
Ileana
May 05, 2026
∙ Paid

The most important part of using AI to design and build is making it look intentional, using your branding direction, and staying away from random AI aesthetics.

So what works today and what doesn’t?


Quick Clarification: Style Guide vs Design System

These two get used interchangeably and they’re not the same thing.

Style guide: defines how a brand should look and feel. It usually covers things like color, typography, logo usage, imagery, iconography, tone of voice, and brand principles.

Design system: the operational layer that helps you/teams apply those standards consistently in real products. It includes design tokens, reusable components, interaction patterns, accessibility rules, documentation, and often coded libraries shared by designers and developers.

In simple terms:
Style guides explain the brand.
Design systems help teams build with it at scale.

A style guide can be part of a design system, but a design system goes further by connecting design decisions to actual product implementation, maintenance, and governance.

This matters for AI work.

Most tools that help you generate design systems today produce the visual layer: tokens, components, type scale. The operational layer is still on you. Shared code libraries, accessibility patterns, team governance. Knowing the difference shapes what you can expect from the output, and what you'll need to build on top of it.


Stay in the loop! 💫 Subscribe to receive resources and practical insights on UX + AI.


AI-ready Design Systems

Today, your design system needs to be readable by humans and by AI tools.

SAP calls them Compositional Design Systems, some call them Agentic Design Systems, at Creative Glue Lab we call them AI-ready Design Systems.

Different terms for similar ideas.
A design system is no longer just a shared language between designers and developers.
It becomes a necessary infrastructure.

What AI gives you back depends on what resources and context you provide it with (Figma files and design systems, code, markdown files, skills, pdfs, text files, images), and how it uses it while building.

Whether you’re starting from scratch or refining what you already have, there are different ways to communicate your design direction to AI.

User's avatar

Continue reading this post for free, courtesy of Ileana.

Or purchase a paid subscription.
© 2026 Ileana Marcut · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture