Annotation-First UI Pair Programming: A New Workflow Pattern

There is a recurring frustration in AI-assisted frontend development. You describe what you want. The agent writes code. You preview it in the browser. It is close , but not right. The spacing is off, a component overlaps another, the hover state covers the wrong area. You switch back to the chat, type a correction in natural language, hope the agent understands which element you mean, and iterate. This loop is slow because it relies on the developer translating a visual observation into a text description, and the agent translating that text description back into a spatial understanding of the DOM. Information is lost in both directions. Annotation-first UI pair programming is a workflow pattern that eliminates this translation step. Instead of describing visual issues in text, the developer annotates them directly on the rendered page. Instead of guessing what the developer means, the agent reads structured metadata about the exact elements and regions that were flagged. The problem: