When to use Widget
Use Widget when text is the wrong final format. Architecture explanations, launch comparisons, pricing calculations, UI states, and workflow maps are easier to review when they become an artifact.
A Widget can be a quick sketch for alignment or a reusable mini app for a repeated decision. It lives next to the conversation, so the assistant can use project files, browser evidence, memory, and scheduling context while building it.
Common artifact types
Widget is intentionally broad because product and engineering work needs several kinds of visual output.
- Charts for metrics, benchmarks, release comparisons, and recurring reports.
- Mockups for settings panels, onboarding states, empty states, and product flows.
- SVG diagrams for architecture, data flow, incident response, and docs pages.
- Draw.io-style flows for support playbooks, QA branches, approvals, and handoffs.
- Mini apps for calculators, checklists, scoring matrices, and small internal tools.
Prompt pattern
A strong Widget request names the audience, artifact type, source material, and decision the artifact should support.
For example: create a one-screen architecture diagram for new engineers, based on the deployment notes and these three source files, showing request flow, background jobs, data stores, and failure retry points.
How Widget pairs with other tools
Widget becomes more useful when it is connected to evidence. Browser can inspect a live page before a mockup is drafted. Files can provide the system context for a diagram. Schedule can turn a recurring report into a chart instead of a text summary. Memory can keep design conventions available across sessions.
This is the practical difference between a generic image generator and a project-aware work surface: the artifact is built from the same context the assistant used to understand the work.