Design systems are trapped behind glass
Every design systems architect I know has been asked to wear many hats. Build the component library. Also design the conference booth. Also produce the pitch deck. Also do the social graphics. Also review the print spec for the brochure.
The design system helps with none of that. It lives in Figma and in code, it serves the product team, and it stops at the edge of the UI. Everything else is handled with whatever tool is closest to hand, by whoever has capacity, with whatever brand consistency they can manage.
This isn't a workflow problem. It's an architectural one. Traditional design systems are built to serve UI, and UI only. They're not structured to be consumed by anything outside a component renderer. The brand knowledge is in there — but it's locked in.
Agentic design systems change the lock. Not by adding features. By changing what the system is.
Every surface, one source
When a design system is machine-readable, every AI agent that can consume it becomes a delivery channel. The same brand constraints apply everywhere — not because someone enforced them, but because they're structural.
Applications & Websites
The original domain — but now the UI isn't hand-built, it's generated. Components, pages, entire apps assembled by agents that read the same tokens and context files. The design system doesn't just document the UI, it produces it.
Prototypes & Exploration
NorthStar prototypes, proof-of-concepts, speculative designs. The fastest way to explore a new direction is to let an agent build it from the existing system. Ten variations in an hour, all on-brand, all disposable.
Email & Notifications
Transactional emails, newsletters, push notifications. The brand voice and visual identity flow into every customer touchpoint — not just the product surface.
Documentation & Help
Product docs, onboarding guides, knowledge bases. Consistently branded, correctly voiced, structured from the same design decisions. Documentation stops being the thing nobody styles.
Brand Guidelines
Token values, colour rationale, typography hierarchy — generated directly from the system rather than maintained as a parallel document that drifts from code.
Marketing Collateral
Social cards, email templates, campaign banners. The brand constraints are already in the tokens. The agent reads them. The output is always on-brand, without a briefing.
Social Media
Correctly branded posts, sized for each platform, in the right voice. The design system carries the voice layer — not just colour and type, but tone, message hierarchy, the editorial stance.
Print & Packaging
Brochures, business cards, signage. The same spacing philosophy, the same typographic scale. Print becomes a downstream output of the same source, not a separate project.
Presentations
Slide decks in brand, automatically. Not a template the team ignores — a generator that produces compliant slides from structured content, every time.
TV / Audio-Visual
Motion design briefs, storyboards, ad frameworks — all generated with brand compliance baked in. The design system describes the brand at a level of abstraction that works for any medium.
VR / AR
Spatial design from the same primitives. Colour tokens don't care whether they're applied to a web component or a volumetric surface. The system travels.
Tokens + context + agents = any output format
The mechanism is straightforward once you see it. An agentic design system has three layers that traditional design systems lack:
Tokens are format-agnostic
A colour token is just a value and a semantic name. It doesn't know whether it's being applied to a React component, a print layout, or a motion design brief. Once you structure tokens as JSON or CSS custom properties, any agent can read them.
Context files carry the brand layer
This is the <N>in I<N>C — the Narrate layer. Not just colour values and spacing scales, but brand voice, visual principles, spacing philosophy, editorial stance, target audience, use cases. CLAUDE.md isn't a coding instruction file. It's a brand constitution that AI agents can consume directly.
Agents route to the right output format
You don't need one agent for everything. You need a design system structured so that any agent — the one writing React, the one generating social copy, the one producing a print brief — is working from the same source of truth. The routing is trivial once the system is machine-readable.
My portfolio already does this
This isn't theoretical. The site you're reading right now demonstrates the principle. One design system, one CLAUDE.md, multiple outputs — all consistent, all generated, none manually styled.
Every page generated by agents consuming the same system
Brand-consistent document, not a separate design artefact
Same brand voice, same positioning, different medium
Consistent thought leadership, generated not drafted
None of these outputs share a stylesheet or a template. They share a system. The consistency isn't maintained — it's structural.
Wearing many hats is a superpower, not a burden
The traditional framing: “design system team” — a group of specialists maintaining the product design infrastructure. It serves the product. It doesn't touch anything else. Everyone else builds their own brand collateral their own way.
The agentic framing: “design system as creative department”. The system doesn't serve one team. It serves every team that touches the brand. Marketing, communications, engineering, sales — they all consume from the same source. The design system architect becomes the keeper of the brand constitution, not just the component library.
I've been asked to wear many hats throughout my career. Build the product design system. Also the brand guidelines. Also the conference materials. Also the pitch decks. The traditional response is to treat this as scope creep. The agentic response is to build a system that makes every hat easy to wear.
One person with an agentic design system isn't one person doing the work of many. They're one person orchestrating the work of many — and the system maintains the brand integrity across all of it without anyone needing to check.
This is what I mean by the INC framework as an amplifier. It doesn't change what I can think. It changes what I can ship.
“The design system isn't the component library. It's the brand constitution. Once it's machine-readable, every channel becomes a downstream output.Beyond the Screen — the agentic expansion thesis
Ready to make your design system a creative department?
If you're building a design system that only serves your product UI, you're leaving most of its potential on the table. Let's talk about what the agentic expansion looks like for your brand.