Aestheria.design . Aestheria.design/docs

Why I started

Every prompt gave me back a different product. The agent would return a screen in seconds — new spacing, a button that had never existed, a card shaped nothing like the last one — and I would spend the afternoon putting it back. The speed was real. So was the cleanup.

It was not the model’s fault. Everything it needed to know lived somewhere it could not read: a Figma file, a doc, a component library, a decision someone made in Slack six months ago. Design systems were written for people to interpret, and agents do not interpret. They need the thing itself.

So I started building what I wanted to hand an agent before it wrote a line.

What makes it different, and how it works

Aestheria is a design context layer. It sits between a product team and its coding agents, and it gives both the same source of truth.

It is served over MCP, so an agent does not read documentation — it asks. Behind that sit over a hundred components, patterns, visualizations and page templates, each with its anatomy, its states and its rules. Themes carry their whole character in a single attribute on the root, light or dark, so a page is never wired to a brand: set the attribute and every token re-resolves. And a set of agent skills directs the work rather than leaving the agent to browse — so what it gets is a method, not a parts bin.

The part I care about most is that it was built for AI-native products rather than retrofitted to them. The patterns are the ones these products actually need: a response that streams, an insight that carries its own confidence, a surface marked live or generative or explainable, so the interface tells the truth about where its content came from.

Nobody is replaced by it. Designers set the system, builders set the intent, and the agent works inside both. What changes is that all three are finally speaking the same language.

Where we are

Aestheria is live, and it is what I build with every day — my daily driver, not a deck. The components, patterns, visualizations and templates are shipping, the themes and skills with them, and it runs over MCP inside Claude Code and other agents. It is still early, and it grows every week from whatever I hit while building with it.

There is far more of it than a case study can hold. If you want to see it properly, it is all at aestheria.design, with the documentation at aestheria.design/docs.