creativeclaw-generate-image

Generate Image

For each Creative Claw tool call that exposes it, pass the optional skills_used array with creativeclaw-generate-image, any other Creative Claw skills actually followed, and guide entries in the form <skill-name>/<relative-guide-path> (for example, creativeclaw-generate-image/references/workflow-basics.md). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.

Not connected yet? If no Creative Claw tools (such as list_models or generate_image) are available, the plugin is installed but the server is not connected. Stop and tell the user to open the plugin's Connectors tab in their app (or the MCP server list in a terminal client), connect Creative Claw, sign in, and ask again. Do not substitute other tools or describe a result that was not generated.

Read shared execution guidance once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.

Turn a brief and optional references into a finished image. This is the primary skill for a clear, general image-generation or image-editing request; the selected packaged model reference supplies deeper prompting advice. If the user explicitly requests HTML/CSS rendering or a deterministic code-based PNG, use creativeclaw-render-html instead.

Workflow

1. Establish the subject, intended use, aspect ratio, style, text requirements, and which details must remain exact.
2. Use search_assets for likely reusable references. Import attachments or local files with the platform upload flow before generation.
3. When the user asks for examples, inspiration, styles, or a close starting point, or an open brief would benefit from concrete choices, call search_examples for a small filtered set, then load only the chosen example with search_examples({ id }). Do not search automatically for an already precise brief.
4. For branded work, call get_theme and carry the relevant colors, typography, logo treatment, and visual rules into the prompt.
5. Use list_models({ category: "image" }) when selection is unresolved; for a known choice, use get_model_params directly and reuse its current-task schema.
6. Generate one direction unless several were requested. Estimate with operation: "image" only for user-requested cost/budget help.
7. Call generate_image. If a downstream tool needs a queued result URL, use check_job; otherwise let the inline viewer monitor it.
8. Inspect the result against the non-negotiables, revise the smallest failing element, and tag the approved asset.

Model routing

• Default to image/nano-banana-2 (Nano Banana 2) for most generation and editing, including targeted corrections that should preserve the existing scene. Keep the source aspect ratio unless reframing is requested and inspect the result for unintended changes. Exact preservation outside the edited region requires compositing that region back into the original.
• Use image/nano-banana-pro when maximum fidelity, demanding typography, or a complex composite justifies the premium.
• Use image/gpt-image-2.5-flare for fast, high-quality everyday OpenAI image generation and editing.
• Use image/gpt-image-2.5-sunburst for instruction-heavy editing, precise transformations, typography, or strong world knowledge.
• Use image/seedream-5-pro when the user explicitly requests Seedream. Do not proactively recommend it for precise local edits. After a model moderation refusal, Seedream may also be offered as the tool's suggested alternative, with user confirmation before another paid generation; it applies its own safety checks and may still reject the request.
• For a transparent background, use GPT Image 2.5 (Flare or Sunburst) with extras.background: "transparent", or remove_background for an existing image.
• Honor an explicit model choice. Read the selected image model guide for exact prompting and reference syntax.

Use other image models only when the user asks for them.

Prompt and reference contract

Build prompts in this order: deliverable and subject; composition; must-preserve facts; environment; lighting and camera; material detail; aesthetic; required text; exclusions.

Work in the user's language. Keep supplied visible copy verbatim, including spelling, punctuation, and script direction; verify the selected model's typography and language support when text accuracy matters.

• image_url is the primary reference. Additional reference support is model-specific, so inspect get_model_params instead of assuming a fixed count.
• Set the output shape with aspect_ratio; size is legacy.
• Use a character_id for a saved Character. With an explicit image_url, the Character image is not added automatically; put it in extras.image_urls yourself.
• Video keyframes: use the same image model as the rest of the project, aspect_ratio = the video's ratio, anchors in image_url + extras.image_urls with roles named, one full-bleed frame with no text, grid or labels.
• Preserve exact quoted copy, reference labels, dialogue, timecodes, colors, and approved layout or edit constraints in the prompt.
• Never invent unsupported parameters. Use only fields returned by the tool schema and selected model.

Completion standard

Confirm that subject identity or product geometry, composition, text, crop, and brand rules match the brief. A job ID is not a finished image. Name and tag approved outputs so later video or campaign work can retrieve them.