image-generation

Original：🇺🇸 English

Translated

Control image generation requests before execution. Use this when the user wants text-to-image, image edit, reference-image generation, product image, persona image, banner, thumbnail, storyboard image, or image batch variants and the skill must identify inputs, classify the task, choose model/reference rules, then hand off to image-batch-runner.

11installs

Sourcepostplusai/postplus-skills

Added on2026-05-28

NPX Install

npx skill4agent add postplusai/postplus-skills image-generation

SKILL.md Content

View Translation Comparison →

Image Generation

Use When

The desired final asset is an image or image batch.
The request may include text prompts, uploaded images, previous outputs, product URLs, research handoffs, product images, persona images, banners, thumbnails, storyboard panels, or batch variants.
The next decision is task class, model/reference policy, and runner handoff.

Do Not Use When

The final asset is video, audio, subtitles, transcripts, or an edit plan.
The image request is already normalized and ready to execute. Use
```
image-batch-runner
```
.
The user needs hook decoding or reference boundaries first. Use
```
reference-decode
```
or
```
reference-contract-builder
```
.

Core Boundary

This is the image generation controller. It does not submit jobs.

It must:

identify the input type,
classify the image task,
select model and reference rules,
create the handoff for
```
image-batch-runner
```
.

Task Classes

Task class	Typical input	Handoff
`text_to_image`	prompt only	write normalized image brief for `image-batch-runner`
`image_edit`	uploaded image plus change request	bind edit image and preserve/alter rules
`reference_image`	benchmark frame or style board	use `reference-contract-builder` before runner
`product_image`	product photo, URL, or product facts	bind product identity and forbid invented claims
`banner_thumbnail`	offer, hook, platform	require aspect ratio and text/UI policy
`storyboard_image`	panel plan or board spec	hand storyboard panels to `image-batch-runner`
`batch_variant`	many variants or personas	preserve shared rules and vary only declared fields

Model And Reference Rules

Text-only drafts may use a text-to-image endpoint.
Edits require a bound source image and an edit-capable endpoint.
Persona, product, and brand identity are
```
binding
```
references unless the user explicitly marks them inspiration-only.
Benchmark clips, mood boards, and competitor references are inspiration-only unless the contract says otherwise.
Excluded references must not enter the runner request.

Routing Table

If not image-generation	Send to
Needs media understanding first	`media-router`
Needs reference meaning decoded	`reference-decode`
Needs binding/inspiration/excluded contract	`reference-contract-builder`
Needs storyboard panels	`storyboard-grid-writer`
Needs execution with normalized request	`image-batch-runner`
Final output is video	`video-generation`
Final output is audio	`audio-generation`

Output Shape

Return:

```
taskClass
```
```
inputType
```
```
modelRule
```
```
referencePolicy
```
```
requiredRunnerInputs
```
```
handoffSkill
```
```
mustNotDo
```

Fail Fast

Stop if source images, edit targets, product identity, aspect ratio, text/UI policy, or reference ownership is missing and would change the output.
Do not submit, poll, upload, or choose private provider routes.
Do not let
```
image-batch-runner
```
make creative classification decisions.

Public Command Boundary

Check readiness first:

postplus doctor --skill image-generation

.

This public skill is instruction-driven. Produce the controller handoff artifact directly from the available evidence.
Do not call private provider/runtime paths or unpublished local tools.
If the CLI returns a quote-confirmation challenge, run
```
postplus quote confirm --json --challenge-file <challenge.json>
```
and retry with the returned token.