Outputs AI UX patterns

Output patterns for formatting, comparison, refinement, sharing, and history of model-generated results.

Start here

Core patterns for outputs UX.

17 patterns

Frequently asked questions

How do output patterns help iteration?

They shorten the loop between first draft and shippable work—refine menus, diffs, version history, and export paths users expect from creative and doc tools.

When should I offer output comparison?

When users choose among models, prompts, or settings and need side-by-side diff—not for every reply, which adds noise to simple Q&A.

What belongs in output history versus chat history?

Output history indexes artifacts (images, code files, slides) with metadata; chat history indexes turns. Split them when artifacts outlive the thread.

How should refinement controls be scoped?

Apply refine actions to selections or blocks, show preview, and preserve undo. Global “make it better” without scope frustrates users editing long documents.

Do output patterns cover sharing and export?

Yes—sharing links, format selection, and analytics appear here. Align permissions with trust patterns when outputs contain sensitive data.

Which patterns pair with codegen products?

Smart diff, output comparison, and regen carousels map well to code and copy workflows; see examples on individual pattern pages.