codex-image-genlisted

# Codex Image Generation (delegation SOP) ## Positioning & the exception to the hard line `using-codex-collaboration` draws a hard line: "Codex reviews, never does." **Image asset generation is a whitelisted exception to that line**: an image is not a code implementation — it is a one-off deliverable, it never enters the code-review loop, and it does not amount to "Codex wrote feature code". The exception covers only the production of image files; code implementation, scripts that land in the repo, and feature development remain non-delegable, always. ## Workflow 1. **Locate/launch the Codex pane**: follow `using-codex-collaboration` Step 1 / 1b (send-keys discipline, ghost-text discipline, and background-polling discipline all apply). Image tasks aren't picky about the repo directory, but the deliverable's destination must be an absolute path in the brief. 2. **Send the brief**, which must include: - Purpose and content intent (one sentence, e.g. "app icon for X: dark background + brand-green database/pulse motif") - **Hard constraints**: exact dimensions (e.g. 1024×1024), format (PNG/JPG), alpha-channel requirements (App Store icons must have no alpha), color style - **Compliance constraints**: no third-party trademarks/logos — nominative use applies to words only; someone else's logo inside your graphic asset is infringement - **Absolute output path** (a scratch/asset directory you control, not some tool's temp directory) 3. **Poll and wait** (background po