Members-Only
Recent Talks & Demos are for members only
You must be an AI Tinkerers active member to view these talks and demos.
Consistent UI at Scale
Learn how to use documentation and prompting to keep AI agents consistent with design system standards, reducing style violations and ensuring UI quality.
I’m a design systems lead. My team got dramatically faster with AI agents, but without guardrails the speed produced a mess with custom styles, one-off components, and inconsistent UX patterns. UI updates became disproportionately hard, and even though we shipped more, quality and consistency dropped, and with that, the user experience worsened.
I saw this pattern happening in our team, and on my personal projects, and as a designer, didn’t like it at all. I decided to find a way to guide agents to follow design system standards.
So I ran an experiment to figure out what kind of documentation and prompting actually keeps agents on-pattern. I used the same component library, same models, but three documentation conditions (none, CLAUDE.md + supporting markdown, and a custom Skill + JSDoc) crossed with three prompt styles.
One combination produced 95% fewer style violations against the none-documented version. Agents stopped reinventing components and started reusing them, which allowed the system to maintain itself effectively. New work began reinforcing existing patterns instead of eroding them. When new components or patterns were actually needed, agents started proposing them rather than building unique, one-off elements.