Ask for a document
- “Turn the findings in this conversation into a visual report for leadership.”
- “Make an architecture overview of this repository.”
- “Create a slide deck for the launch review.”
- “Show this implementation plan as visual HTML.”
Tell the agent who will read it, what it should help them understand or decide, and which source material to use.
The agent selects a template, uses available project design guidance, and checks accessibility and document quality. You receive a self-contained HTML file to open and review.
Apply a theme
Choose a design-system reference to change the document's typography, colors, spacing, surfaces, and components:
Apply Editorial to this report. Replace the project's visual styling for this
artifact only; keep its logo, content, section order, and behavior.
The project's styling applies unless you approve an exception for this document. Applying a theme does not update DESIGN.md, PRODUCT.md, or project tokens.
Compare designs
Creation proposes one structure before writing HTML. If you want alternatives, use Artifact Explore to compare layouts, styles, or both. You can start from source material without an existing layout or design file.
Explore keeps the original file unchanged until you choose a direction and ask to apply it. It does not create a project design system.
Generate an image
Generated imagery is optional. When it is essential, the agent checks the supported image-generation options and asks you to select one. If none is available, it stops with setup instructions.
The agent sends your prompt and approved reference images to the selected provider. It saves one PNG or JPEG in the approved project directory and opens it for visual inspection before use. The result includes the method used and output details, with no separate metadata file.
visualize preserves the provider's image bytes and metadata. It does not add prompt data to the image or publish it automatically. See troubleshooting for API keys and failed requests.