Your Brand Is in a Format AI Can't See

Your Brand Is in a Format AI Cannot See

Google just dropped something that I think is going to matter a lot for marketers.

It's called design.md.

The simple version: it gives AI agents a structured way to understand your brand’s visual identity. Your colors, fonts, layouts, creative rules, and design patterns can live in one markdown file that agents can read and reuse.

That sounds small until you realize the real problem.

Your brand is probably scattered across landing pages, ad files, decks, creative folders, old briefs, and random Figma links. Humans can sort through that mess. Agents usually cannot.

That is why AI-generated creative often feels close, but slightly off.

Why design.md matters

Google’s version of design.md is a format specification for describing visual identity to coding agents.

The bigger move is obvious. Google is trying to make its design.md format the default standard, the same way agents.md is becoming a common file for telling coding agents how to work inside a repo.

If this becomes normal, your brand guidelines stop being a PDF people ignore.

They become operating memory for agents.

I already started testing this with ClickFlow and Single Grain.

For ClickFlow, I can hand an agent the ClickFlow design.md and say: “Make a landing page. Make ads. Make a carousel. Follow this.”

That is useful because ClickFlow has its own visual language. Single Grain has a different one. If agents cannot see the difference, they will flatten everything into generic AI design.

The lock-in problem nobody talks about

I like using Claude design. I like what Anthropic is doing.

But I do not want my brand system trapped inside one company’s design tool, one model, one token system, or one proprietary format.

That is the lock-in problem.

A portable design.md file is different. You can put it in your repo, update it over time, and call it from whatever agent or workflow you are using.

This is why I keep coming back to Single Brain. The best agents need context. They need to know your business, your customers, your positioning, your assets, and your standards. A design.md file is one piece of that memory layer.

Without that memory, agents are fast but inconsistent.

With that memory, agents can start compounding.

The marketing use case is volume plus consistency

Marketing teams have a volume problem.

In the video, I talk about clients that want to ship 500 to 1,000 ads per month. Top ad accounts can ship hundreds of creatives a month. Most teams are nowhere near that.

The constraint is not only production speed. It is consistency.

One designer can keep the brand tight, but output is limited. A bigger design team can create more, but consistency gets harder. One operator with agents and a strong design.md file can produce more assets while keeping the brand system intact.

Your agent can look at what is performing in your ad library or ad accounts, generate more variations, and keep the creative aligned with the brand instead of drifting into generic templates.

Sales teams should pay attention too

The sales use case might be even more obvious.

Instead of waiting on a marketing queue for a custom deck, a rep could generate a deal-specific deck that still follows the brand.

Same with one-pagers, proposal pages, case studies, and follow-up assets.

If you already have high-converting decks, you can turn the design pattern into a reusable file and let agents recreate the structure for each deal.

That is where this gets interesting for agencies too.

If you manage multiple brands, each client can have a separate design.md file. Your agents can switch context without mixing brands together.

What I would do this week

Start simple.

Pick one brand or product. Create a design.md file from your site, landing pages, and best-performing creative. Then test it against one practical asset.

Ask an agent to build:

1. A landing page section

2. Three ad concepts

3. A short sales deck

4. A carousel outline

5. A case study page

Then compare the output against your current brand assets.

The question is not “did the agent create something pretty?”

The question is: did it create something that actually feels like your brand?

If yes, you just created a reusable brand memory file. If no, your brand system probably was not clear enough for a human team either.

That is the bigger lesson.

Design.md is one more step toward agents that can work inside your business instead of generating generic outputs from the outside.

Full breakdown here: https://www.youtube.com/watch?v=APExbYgQlZ8

To building brands agents can actually understand,

Eric Siu