I design design systems. Ever since generative models found their way into design tools, I've spent most of my time on a single question: what does an AI actually understand about a design system, and what do you need to write down so it generates on-system the first time?
What I do
Three things, in this order. I audit a design system and score it: what a model understands of it today, and what it's missing. I encode the judgment of the team — the intents, the variants, the composition rules, everything that lives in people's heads and never in the tokens. Then I plug it all into the tools through an MCP connector, so generation starts from the system instead of making it up.
The full three-step method is on the home page.
Who I've worked with
42, Semji, Sextant Properties, Acumen Patrimoine. Product teams that already had a design system — and the same question when it came time to hand it to an AI.
I write down what I learn
Every engagement leaves a lesson. I publish it on LinkedIn, and I republish it here so you can read it without an account or an algorithm.
Get in touch
| Role | Product & design-systems designer, founder of Axolo |
| Company | A.MORVAN (SASU) — SIRET 978 484 095 00010 |
| Talk | Book a slot |
Your design system becomes your design tool. Axolo is in private beta.
Join the waitlist