Specialists

Generating images

Make and refine images from the terminal, stored in the project with their revision history.

Code

/image generate a spot illustration of a paper aeroplane, warm ink on ivory
/image refine latest make the line weight lighter
/images                      the gallery

CtrlO opens the gallery too.

Where files go

Under generated-images/ in your project, alongside a receipt for each revision — the prompt, what changed, and which image it came from. So an asset six weeks old still knows how it was made.

Refining rather than rerolling

Code

/image refine latest crop tighter, more space at the top
/image refine <id> same composition, cooler palette

Refinement keeps the lineage. Generating again from scratch loses it.

The commands

Command	What it does
`/image generate <description>`	Make one
`/image refine latest <instruction>`	Iterate on the most recent
`/image view <id>`	Show it in the pane
`/image open <id>`	Open in your system viewer
`/image list`	Everything generated for this project
`/image where`	The directory on disk

Cost

Generating and refining use ContextStream credits at the image service's rate. Browsing, viewing, and opening are local and free.

Design work can reach for it

When bespoke imagery is genuinely justified, the design specialist can generate it — gated behind your approval, with the same provenance. See Designing an interface.

If it doesn't work

Generation refused. Content policy, or an empty balance. /usage tells you which.

It doesn't match the description. Refine rather than regenerate — smaller, more concrete instructions land better than a rewritten prompt.

I can't find the file. /image where prints the directory.