AI UX frameworks
Decision frameworks for AI products. Shared structure when a single pattern isn’t enough.
Framework
Agentic UX
Use when the product can take actions (send, spend, edit, delete) and you need to decide how much authority is safe.
ReadFramework
Chat UX
Use when the product is a conversation: composing turns, streaming answers, remembering context, and recovering when a turn fails.
ReadFramework
Trust Scaffolding
Use when people must decide whether to believe or rely on the system, from first run through evidence, control, and long-term use.
Read
Frequently asked questions
What is an AI UX framework on this site?
A framework is a versioned, opinionated reference for a territory of AI UX. It introduces named patterns, anti-patterns, and open problems, not just tags on the main catalog. Use frameworks when you need shared vocabulary for specs, design reviews, and agent scoping.
Which frameworks are available today?
There are 3 live frameworks: Agentic UX and Chat UX and Trust Scaffolding. Each has a version number, cover art, territories or chapters, and links into related patterns in the main catalog. Roadmap frameworks stay in the data layer until content is complete, then join this hub as live entries.
What does the Agentic UX framework cover?
Agentic UX (2.0) defines 36 patterns across seven territories: permission, reversibility, autonomy, cost, cross-app handoffs, ambient and voice, and trust. It answers what an agent may touch, how to undo actions, and how users verify what happened.
What does the Chat UX framework cover?
Chat UX covers composer, streaming, memory, and repair patterns for conversational AI surfaces.
When should I use a framework versus browsing patterns?
Use a framework when you are scoping a new surface or aligning a team on vocabulary (for example before writing an agent PRD). Use the pattern grid when you know the interaction you need and want demos, anti-patterns, and product examples for that specific UI convention.
How are framework versions maintained?
Each framework page shows a version and last-updated date. Territories and pattern lists evolve as the field matures; linked catalog patterns may gain demos or new examples without changing the framework version until the editorial structure changes.