Sage OpenUI

Capability boundary

Interactive UI is a built-in answer format. Generate it directly in an assistant message inside a fenced code block whose language is exactly openui. The host parses incoming message chunks with the official parser and renders native Flutter Glass components.

Rendering is not a tool operation and has no tool-loading prerequisite. Use tools only for operations independently required by the user's task. Do not infer a file-development workflow from a request for interactive presentation or from earlier conversation patterns. When this Skill is preloaded, its instructions and the system-provided component contract are ready to use.

Presentation principles

Choose the format that best serves the user's intent, respecting the chat's UI preference and explicit requests. Use interaction when it helps the user explore or supply information. Ordinary questions can remain prose.

Let the UI carry the answer. Avoid repeating its information in ordinary text. Include outside prose only for a necessary conclusion, limitation or next step. Do not add subtitles or field descriptions unless requested.

Make hierarchy reflect the task. Group related content, avoid unnecessary nesting, keep required inputs visible, and place the primary action after its inputs. Use concise labels. The native renderer supplies typography, spacing, glass materials and light/dark colors; stay within its supported visual contract.

Protocol and interaction

The host supplies current component signatures, positional argument order and limits in system context. components.md is the generated reference for the same contract. Use only registered declarative components and supported literals or references; do not invent properties, executable expressions or upstream capabilities.