Expression Infrastructure
Vibe design is just the beginning.
Here's what comes after the vibe.
Google calls it vibe design. We call it expression infrastructure. Describing intent instead of specifying components is how design will work in the agentic era. We agree. The question is: what happens when that intent needs to become deterministic, enforceable, and available at runtime?
What is vibe design?
Vibe design is the idea that you should be able to describe what you want — a feeling, an aesthetic, a business objective — and an AI generates design directions that match that intent. No wireframes. No component specs. Just creative direction in, visual output out.
Google introduced the term with Stitch's March 2026 update. It supports aesthetics like Bento Grids, Glassmorphism, and Y2K. You describe a vibe, and Stitch generates multiple screen directions.
This is a powerful idea. And it's where most tools stop.
From vibe to infrastructure
Vibe design answers the question: what should this look like? Expression infrastructure answers: how does this behave across every agent, every surface, every time?
01
Describe your brand
Use natural language to express your brand's personality, values, and aesthetic. This is the vibe. It's where vibe design starts, and where most tools stop.
02
Resolve into a design system
LESS takes your brand description and resolves it into a complete, production-ready design system: colors, typography, spacing, components, patterns, voice. Deterministically. Same input, same output.
03
Enforce via contracts
LESS tokens become enforceable design contracts with agentic guardrails. Not descriptive documentation but operational infrastructure that agents validate against at resolution time.
04
Serve at runtime
Your expression system is available via API at runtime. Any agent — Claude Code, Cursor, Lovable — resolves against it live. No copy-paste. No context windows. No degradation.
The design spectrum
Vibe
System
Infrastructure
Exploration
Production
Vibe is the creative spark: describing intent, exploring directions, generating possibilities. Google Stitch lives here.
System is the organized output: tokens, components, patterns arranged into a coherent design system. Traditional design tools live here.
Infrastructure is the operational layer: enforceable contracts, runtime APIs, agentic guardrails, deterministic resolution. LESS Studio lives here.
Vibe design vs vibe coding
Vibe Coding
Describe what to build
- Natural language to functional code
- Focus: behavior, logic, features
- Agents: Claude Code, Cursor, Lovable
- Output: working software
Vibe Design
Describe how it should feel
- Natural language to visual direction
- Focus: aesthetics, expression, brand
- Tools: Google Stitch, Figma AI
- Output: screens and prototypes
They're complementary. Vibe coding builds functionality. Vibe design defines expression. The gap between them is where expression infrastructure lives.
Without infrastructure, vibe coders generate code that works but looks generic. Vibe designers generate screens that look good but don't translate to code. LESS bridges the gap so your AI coding agents resolve against your brand's expression system at runtime, producing code that works and looks intentional.
Why infrastructure, not just a canvas
Canvas (Stitch)
Explore in a browser tab
- Open Stitch, type a prompt
- Get multiple screen directions
- Export as design.md or React
- Copy-paste into your workflow
- Non-deterministic: different every time
- 350 generations per month
Infrastructure (LESS)
Resolve in your workflow
- Describe your brand once
- Get a complete expression system
- Available via API at runtime
- Agents resolve against it natively
- Deterministic: same input, same output
- Unlimited resolution
Go beyond the vibe.
Describe your brand once. Get a deterministic expression system that every AI agent resolves against, at runtime, via API, with zero degradation.
Get Started
Compare with Google Stitch
Go deeper
Frequently asked questions
What is vibe design?
Vibe design is an approach to AI-native design where you describe a feeling, aesthetic, or business objective in natural language, and an AI generates design directions that match that intent. Google popularized the term with Stitch's March 2026 update. It replaces the wireframe-first workflow with intent-first design.
What is the difference between vibe design and vibe coding?
Vibe coding describes the intent of what you want to build and lets AI generate the code. Vibe design describes the intent of how you want it to look and feel. They are complementary. Expression infrastructure bridges them by making design systems that AI coding agents can resolve against at runtime.
What is expression infrastructure?
Expression infrastructure is the programmable layer that takes design intent and resolves it into deterministic, enforceable design contracts, available at runtime via API. It goes beyond generating screens by producing the underlying system that AI agents resolve against.
How does LESS Studio relate to vibe design?
LESS Studio is the infrastructure layer that makes vibe design production-ready. Where vibe design tools generate one-off screen designs from intent descriptions, LESS resolves that intent into a complete, deterministic expression system with enforceable contracts and runtime API access.
Can I use vibe design with AI coding agents?
Yes, but you need infrastructure, not just a canvas. LESS Studio provides a design system that AI coding agents (Claude Code, Cursor, Lovable) resolve against at runtime via the designless MCP server. Your vibe becomes deterministic infrastructure that agents use automatically.