10 posts found
What an AI agent can actually do with a design system
Given a real design system, a model stops inventing interfaces and starts assembling them. The difference is not the mod...
Design tokens are the interface AI needs
A token that only names a hex value has saved you nothing. A token that names a job tells a model which decision it is m...
Generating layouts that respect a grid
Generated layouts usually look almost right, and "almost" is where the eye catches. Most of the fix is stating the rules...
Why component names matter more with AI in the loop
A human reads a bad component name and opens the file. A model reads it and guesses. Naming quietly became an interface...
Reviewing AI-generated UI: a checklist
Generated interfaces fail in a predictable set of places. Knowing which ones turns review from a vague unease into a lis...
How to evaluate an AI feature before you ship it
You cannot unit test "is this a good answer", but you can build a set of real cases with known-good outputs. An afternoo...
The cost model of an AI feature
Per-token pricing looks trivial until you multiply by retries, conversation history and the context you resend on every...
Writing prompts your team can maintain
Prompts are code with none of the tooling. Treat them like code anyway — version them, review them, test them, and expla...
What to tell users when the model is wrong
Your AI feature will be confidently wrong in front of a user. What the interface does in that moment decides whether the...
AI adoption without a rewrite
The best first AI feature is small, measurable and easy to switch off. Start where a wrong answer is cheap and the value...