15 posts found
An agent is a loop, not a personality
Strip away the branding and an agent is a small loop: call the model, run the tool it asked for, feed the result back, r...
Tool calling is an API contract the model can read
A tool definition is documentation with a schema attached. Write it for a capable colleague who has never seen your syst...
Why agents fail on long tasks
An agent that handles five steps beautifully can fall apart at twenty. The reason is rarely reasoning — it is that the c...
Giving an agent memory without giving it amnesia
Memory is not a feature you enable. It is a set of decisions about what to keep, what to summarise and what to let go —...
When a workflow beats an agent
If you already know the steps, do not ask a model to rediscover them on every request. A fixed pipeline with model calls...
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...