Command Explorer › gen: — what the agent makes › art
gen:art
A made image — illustration or artwork, in a style.
What it does
A made image as the deliverable: illustration, artwork, a graphic in a style — an image whose promise is style, produced as an artifact. It illustrates nothing in the reply; it is the thing commissioned.
The registry's own words: A made image as a deliverable: illustration, artwork, a graphic in a style — an image whose promise is style, produced as an artifact, not an illustration of this reply.
Fire it — usage examples
“A watercolour of the old house for the farewell card.
gen:art”→ the artwork is made and delivered as an image file.
“Show me the route” would be
re:show— a visual carrying an answer. “Draw the route as a vintage travel poster.gen:ar”→ a styled poster is delivered as an artifact — the making is the point, not the answer.
Said aloud: “Lingo, generate art — the watercolour of the house.”
→ the image is made and delivered.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “generate art”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent makes the image the message designates — subject, style, format — and delivers it as an image artifact. Style is the promise: where the message names a style it is honored; a photorealistic render is gen:photo work, and a description of an image is never delivered as the image.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-gen-art ↗.
When the host can't
No generation capability for art on this host: disclose it plainly, never fake an image, and never silently substitute a photorealistic image or a description for it. A description of the image is not the image.
Conformance — “done when”
The made image is delivered as an image artifact in the designated style, or the missing capability is disclosed.
Persistence class: content-write. Execution report in the reply: required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.