Image Generation Skill

Generates or edits images for the current project (for example website assets, game assets, UI mockups, product mockups, wireframes, logo design, photorealistic images, or infographics).

Top-level modes and rules

This skill has exactly two top-level modes:

• Default built-in tool mode (preferred): built-in image_gen tool for image generation, editing, and transparent-image requests. Does not require OPENAI_API_KEY.
• Fallback CLI mode: scripts/image_gen.py CLI. Use when the user explicitly asks for or confirms the CLI/API/model path. Requires OPENAI_API_KEY.

Within CLI fallback, the CLI exposes three subcommands:

• generate
• edit
• generate-batch

Rules:

• Use the built-in image_gen tool by default for normal image generation and editing requests.
• Do not switch to CLI fallback for ordinary quality, size, or file-path control.
• For transparent images, ask built-in image_gen for a transparent background and preserve the generated alpha.
• Never silently switch from built-in image_gen or CLI gpt-image-2 to CLI gpt-image-1.5; ask the user first unless they explicitly requested gpt-image-1.5.
• The word batch by itself does not mean CLI fallback. If the user asks for many assets or says to batch-generate assets without explicitly asking for CLI/API/model controls, stay on the built-in path and issue one built-in call per requested asset or variant.
• If the built-in tool fails or is unavailable, tell the user the CLI fallback exists and that it requires OPENAI_API_KEY. Proceed only if the user explicitly asks for that fallback.
• If the user explicitly asks for CLI mode, use the bundled scripts/image_gen.py workflow. Do not create one-off SDK runners.
• Use the bundled CLI for requested CLI workflows. Modify its code only when the user asks to repair or extend that implementation; a missing feature is not permission to expand the task.

Built-in save-path policy:

• In built-in tool mode, Codex saves generated images under $CODEX_HOME/* by default.
• Do not describe or rely on OS temp as the default built-in destination.
• Do not describe or rely on a destination-path argument (if any) on the built-in image_gen tool. If a specific location is needed, generate first and then move or copy the selected output from $CODEX_HOME/generated_images/....
• Save-path precedence in built-in mode:
  1. If the user names a destination, move or copy the selected output there.
  2. If the image is meant for the current project, move or copy the final selected image into the workspace before finishing.
  3. If the image is only for preview or brainstorming, render it inline; the underlying file can remain at the default $CODEX_HOME/* path.
• Never leave a project-referenced asset only at the default $CODEX_HOME/* path.
• Use the requested output name or a descriptive filename without a version suffix. Verify the destination before an authorized replacement and keep any rollback copy outside final deliverables. For an unrequested replacement, save to a separate output directory or choose a distinct descriptive name; never overwrite an unrelated asset.

Shared prompt guidance for both modes lives in references/prompting.md and references/sample-prompts.md.

Fallback-only docs/resources for CLI mode:

• references/cli.md
• references/image-api.md
• references/codex-network.md
• scripts/image_gen.py

When to use

• Generate a new image (concept art, product shot, cover, website hero)
• Generate a new image using one or more reference images for style, composition, or mood
• Edit an existing image (inpainting, lighting or weather transformations, background replacement, object removal, compositing, transparent background)
• Produce many assets or variants for one task

When not to use

• Extending or matching an existing SVG/vector icon set, logo system, or illustration library inside the repo
• Creating simple shapes, diagrams, wireframes, or icons that are better produced directly in SVG, HTML/CSS, or canvas
• Making a small project-local asset edit when the source file already exists in an editable native format
• Any task where the user clearly wants deterministic code-native output instead of a generated bitmap

Decision tree

Think about two separate questions:

1. Intent: is this a new image or an edit of an existing image?
2. Execution strategy: is this one asset or many assets/variants?

Intent:

• If the user wants to modify an existing image while preserving parts of it, treat the request as edit.
• If the user provides images only as references for style, composition, mood, or subject guidance, treat the request as generate.
• If the user provides no images, treat the request as generate.

Built-in edit inputs:

• Inspect local edit targets with view_image before editing.
• Follow the currently exposed tool schema. When every target has a local path and the tool supports referenced_image_paths, use those paths. Otherwise use the smallest recent-image count that includes all targets if num_last_images_to_include is supported. Never set both mechanisms.
• Ask for a missing image only when neither supported mechanism can include it. File paths alone do not require switching to the paid API/CLI workflow.
• Preserve the requested invariants and save a new version unless replacement is authorized.

Execution strategy:

• In the built-in default path, produce many assets or variants by issuing one image_gen call per requested asset or variant.
• In the CLI fallback path, use the CLI generate-batch subcommand only when the user explicitly chose CLI mode and needs many prompts/assets.
• For many distinct assets, do not use n as a substitute for separate prompts. n is for variants of one prompt; distinct assets need distinct built-in calls or distinct CLI generate-batch jobs.

Assume the user wants a new image unless they clearly ask to change an existing one.

Complete the requested image work

• Use the built-in tool by default. Use CLI/API mode only when the user requested or authorized it; keep its credential and model requirements separate.
• Identify the edit target and reference roles, exact text, and visual constraints from the request. Clarify only missing information that blocks the result.
• Write a prompt that preserves the user's scope, generate or edit, inspect the result, and make targeted corrections when needed.
• For project assets, copy the selected tool-returned output into the workspace and update consuming references as required. For previews, display the generated image inline. Preserve all requested final batch assets.
• Follow the tool's required delivery format. Report saved project paths when applicable; include prompts or internal mode details only when requested or useful to reproduce the result.

Transparent image requests

Ask built-in image_gen for a genuinely transparent background and preserve its alpha.

Prompt augmentation

Reformat user prompts into a structured, production-oriented spec. Make the user's goal clearer and more actionable, but do not blindly add detail.

Treat this as prompt-shaping guidance, not a closed schema. Use only the lines that help, and add a short extra labeled line when it materially improves clarity.

Specificity policy

Use the user's prompt specificity to decide how much augmentation is appropriate:

• If the prompt is already specific and detailed, preserve that specificity and only normalize/structure it.
• If the prompt is generic, you may add tasteful augmentation when it will materially improve the result.

Allowed augmentations:

• composition or framing hints
• polish level or intended-use hints
• practical layout guidance
• reasonable scene concreteness that supports the stated request

Not allowed augmentations:

• extra characters or objects that are not implied by the request
• brand names, slogans, palettes, or narrative beats that are not implied
• arbitrary side-specific placement unless the surrounding layout supports it

For complex compositing, exact-text layouts, or batch prompt specifications, see optional prompt specs. Simple requests do not need that template.

Prompting best practices

• Structure prompt as scene/backdrop -> subject -> details -> constraints.
• Include intended use (ad, UI mock, infographic) to set the mode and polish level.
• Use camera/composition language for photorealism.
• Only use SVG/vector stand-ins when the user explicitly asked for vector output or a non-image placeholder.
• Quote exact text and specify typography + placement.
• For tricky words, spell them letter-by-letter and require verbatim rendering.
• For multi-image inputs, reference images by index and describe how they should be used.
• For edits, repeat invariants every iteration to reduce drift.
• Iterate with single-change follow-ups.
• If the prompt is generic, add only the extra detail that will materially help.
• If the prompt is already detailed, normalize it instead of expanding it.
• For CLI fallback only, see references/cli.md and references/image-api.md for model, quality, input_fidelity, masks, output format, and output-path guidance.
• For transparent images, ask built-in image_gen for actual transparency and preserve its alpha.

More principles shared by both modes: references/prompting.md. Copy/paste specs shared by both modes: references/sample-prompts.md.

Guidance by asset type

Asset-type templates (website assets, game assets, wireframes, logo) are consolidated in references/sample-prompts.md.

gpt-image-2 guidance for CLI fallback

The fallback CLI defaults to gpt-image-2.

• Use gpt-image-2 for new CLI/API workflows unless the user confirms a different model.
• CLI gpt-image-2 does not support background=transparent; ask before using gpt-image-1.5 unless the user explicitly requested that model.
• gpt-image-2 always uses high fidelity for image inputs; do not set input_fidelity with this model.
• gpt-image-2 supports quality values low, medium, high, and auto.
• Use quality low for fast drafts, thumbnails, and quick iterations. Use medium, high, or auto for final assets, dense text, diagrams, identity-sensitive edits, or high-resolution outputs.
• Square images are typically fastest to generate. Use 1024x1024 for fast square drafts.
• If the user asks for 4K-style output, use 3840x2160 for landscape or 2160x3840 for portrait.
• gpt-image-2 size may be auto or WIDTHxHEIGHT if all constraints hold: max edge <= 3840px, both edges multiples of 16px, long-to-short ratio <= 3:1, total pixels between 655,360 and 8,294,400.

Popular gpt-image-2 sizes:

• 1024x1024 square
• 1536x1024 landscape
• 1024x1536 portrait
• 2048x2048 2K square
• 2048x1152 2K landscape
• 3840x2160 4K landscape
• 2160x3840 4K portrait
• auto

Fallback CLI mode only

Temp and output conventions

These conventions apply only to the CLI fallback. They do not describe built-in image_gen output behavior.

• Follow the current workspace intermediate/output directories. If none are specified, use work/imagegen/ for intermediate files and outputs/imagegen/ for final artifacts.
• Use --out or --out-dir to control output paths; keep filenames stable and descriptive.

Dependencies

Prefer uv for dependency management in this repo.

Required Python package:

uv pip install openai

Optional for image inspection and downscaling:

uv pip install pillow

Portability note:

• If you are using the installed skill outside this repo, install dependencies into that environment with its package manager.
• In uv-managed environments, uv pip install ... remains the preferred path.

Environment

• OPENAI_API_KEY must be set for live API calls.
• Do not ask the user for OPENAI_API_KEY when using the built-in image_gen tool.
• Never ask the user to paste the full key in chat. Ask them to set it locally and confirm when ready.

If the key is missing, give the user these steps:

1. Create an API key in the OpenAI platform UI: https://platform.openai.com/api-keys
2. Set OPENAI_API_KEY as an environment variable in their system.
3. Offer to guide them through setting the environment variable for their OS/shell if needed.

If installation is not possible in this environment, tell the user which dependency is missing and how to install it into their active environment.

Script-mode notes

• CLI commands + examples: references/cli.md
• API parameter quick reference: references/image-api.md
• Network approvals / sandbox settings for CLI mode: references/codex-network.md

Reference map

• references/prompting.md: shared prompting principles for both modes.
• references/sample-prompts.md: shared copy/paste prompt recipes for both modes.
• references/cli.md: fallback-only CLI usage via scripts/image_gen.py.
• references/image-api.md: fallback-only API/CLI parameter reference.
• references/codex-network.md: fallback-only network/sandbox troubleshooting for CLI mode.
• scripts/image_gen.py: fallback-only CLI implementation. Use only when the user explicitly chooses or confirms CLI mode.