Do AI agents need skills or infrastructure?

Both. Skills provide workflow choreography: step 1, step 2, step 3. Infrastructure provides design judgment: which color, what spacing, how much contrast. An agent with skills but no infrastructure follows instructions blindly. An agent with infrastructure but no skills has judgment but no workflow.

Can Figma skills replace expression infrastructure?

No. Figma skills teach agents how to work on the Figma canvas. Expression infrastructure encodes design judgment that agents resolve against at runtime. Skills say 'create a component.' Infrastructure says 'this is what a good component looks like for this brand, context, and audience.'

What does the full agent design stack look like?

Four layers: Tokens (the vocabulary, via designtoken.md), Skills (the workflow, via skill.design), Infrastructure (the judgment, via LESS MCP), Plugins (the product, via Prism and Sentinel). Each layer serves a different function. Together they form the complete design intelligence stack.

Skills vs Infrastructure: What AI Agents Actually Need

Skills tell agents what to do. Infrastructure gives them the judgment to do it well.

This distinction is foundational. Miss it and you end up with agents that either follow orders blindly or that have taste but no direction.

The complete system requires both layers working together. Understanding the difference between them is essential for building AI that designs well.

Side-by-side comparison

Aspect	Design Skill	Expression Infrastructure
Primary function	Workflow choreography	Design judgment
What it says	"Do step 1, then step 2, then step 3"	"When you face this choice, here is what right looks like"
Scope	Procedural, sequential	Contextual, deterministic
Format	Markdown instructions, open standard	Runtime API, deterministic resolution
Portability	Runs on any compatible agent	Serves any agent via MCP
Failure mode	Follows bad instructions	Returns wrong judgment

The four-layer stack

The complete design intelligence stack has four layers. Each serves a specific function. Together they enable agents to compose design with both workflow and wisdom.

1

Tokens — The Vocabulary

The atomic elements. Colors, typography, spacing, components. Not judgment, just vocabulary. designtoken.md is where tokens live and evolve.

2

Skills — The Workflow

Portable, open-standard instructions that teach agents how to accomplish design tasks. Orchestration. skill.design is the registry.

3

Infrastructure — The Judgment

Runtime resolution of design decisions. Which specific color, what relationship, how much contrast, for what context. LESS MCP serves this layer.

4

Plugins — The Product

Agents that consume all three layers. Prism generates visuals. Sentinel optimizes performance. LoomX resolves complex decisions. The orchestrators.

Why this matters

A brand that relies only on Figma skills is locked into the Figma ecosystem. A brand that has portable skills but no infrastructure produces consistent procedural output without judgment. A brand with full-stack coverage – tokens, skills, infrastructure, plugins – compounds its design quality across every surface an agent touches.

Skills without infrastructure is like following a recipe without knowing how to cook. Infrastructure without skills is like having good taste but no process. The agentic era demands both.