Developer Guides
How to Give an AI Assistant Context About Your Application UI
How to represent pages, UI elements, and workflows as useful, deliberate context for an AI assistant.
Published Aug 17, 2026 · Aven Team
The practical problem
UI context should name the pages, elements, and tasks you are prepared to support. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
How to approach it
Stable IDs and labels are more reliable than asking an assistant to infer meaning from arbitrary markup. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Implementation considerations
Keep context close to the product implementation so it changes with the interface. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Tradeoffs to keep in view
UI context should name the pages, elements, and tasks you are prepared to support. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Where Aven fits
Stable IDs and labels are more reliable than asking an assistant to infer meaning from arbitrary markup. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Build this with Aven
Aven uses developer-registered pages, elements, and workflows. The host application owns navigation, target readiness, and completion.