gpt-image-prompt-master

SKILL.md

---
name: gpt-image-prompt-master
description: Route, write, improve, audit, or debug production prompts compatible with GPT Image 2 and GPT Image 2.5 across photography, cinematic scenes, posters, products, UI, information design, technical illustration, logos, illustration, 3D, architecture, and character assets. Use for prompt-only work involving new images, edits, reference-image roles, masks, exact in-image text, identity or product preservation, multi-panel continuity, and reusable visual systems. Does not generate images or recommend model and API parameters. Not for reverse-engineering an existing image into a text-only reconstruction prompt; use image2prompt for that task.
---

# GPT Image Prompt Master

Convert intent into an executable visual brief. Route by the artifact's dominant failure surface, then load only the method that changes the result. Do not make a weak idea sound stronger with adjectives; control the image through visible facts, hierarchy, relationships, geometry, material behavior, light, text, and preservation rules.

This Skill writes prompts only. It does not invoke an image tool, choose generation parameters, or perform image generation or editing. Those actions belong to a separate image-generation Skill, agent, or tool. The prompt methods here are compatible with GPT Image 2 and GPT Image 2.5, and are engineering heuristics rather than guarantees.

## 1. Select the operation

Choose one operation before selecting a visual route.

| Operation | Use when | Read |
|---|---|---|
| `create` | New prompt from an idea or brief | [Create and improve](references/operations/create-improve.md) |
| `improve` | Existing prompt should become clearer or more controllable | [Create and improve](references/operations/create-improve.md) |
| `debug` | A generated result or repeated failure is available | [Debug and iteration](references/operations/debug-iteration.md) |
| `edit` | Change an existing image, use reference images, or plan a mask | [Edit, references, and masks](references/operations/edit-reference-mask.md) |
| `system` | Build a reusable series, campaign, character, storyboard, or prompt family | [Systems and series](references/operations/system-series.md) |
| `explain/audit` | Explain methods, inspect this Skill, or critique without delivering a prompt | Answer directly; do not force the prompt output contract. |

`debug`, `edit`, and `system` still require a primary visual route. The operation defines what to do; the visual route defines what correctness means.

## 2. Select one primary visual route

Ask: **which class of error would make this artifact immediately unusable?** Choose exactly one primary route. Subject matter alone does not decide the route.

| Primary route | Dominant failure surface | Read |
|---|---|---|
| `photo-editorial` | Camera, anatomy, exposure, or physical space is not believable | [Photography](references/routes/photo-editorial.md) |
| `cinematic-scene` | The narrative beat, blocking, lens, or motivated lighting is incoherent | [Cinematic scene](references/routes/cinematic-scene.md) |
| `ad-poster-cover` | Hierarchy, typography, layout, or hero-visual relationship fails | [Advertising, poster, and cover](references/routes/ad-poster-cover.md) |
| `product-packaging` | Product geometry, label placement, material, or scale drifts | [Product and packaging](references/routes/product-packaging.md) |
| `ui-screen` | Layout tree, screen state, component count, or UI copy is wrong | [UI screen](references/routes/ui-screen.md) |
| `information-design` | Data, topology, labels, visual encoding, or reading order is wrong | [Information design](references/routes/information-design.md) |
| `technical-industrial` | Component order, cutaway/exploded logic, or annotations are implausible | [Technical and industrial](references/routes/technical-industrial.md) |
| `logo-brand-system` | Silhouette, negative space, wordmark, or system coherence fails | [Logo and brand system](references/routes/logo-brand-system.md) |
| `illustration-graphic` | Shape grammar, line, coloring, or medium trace drifts | [Illustration and graphic art](references/routes/illustration-graphic.md) |
| `3d-cg` | Geometry, thickness, material, projection, or light response conflicts | [3D and CG](references/routes/3d-cg.md) |
| `spatial-architecture` | Circulation, openings, scale, world map, or spatial continuity fails | [Spatial and architecture](references/routes/spatial-architecture.md) |
| `character-asset` | Identity, body proportions, wardrobe construction, or cross-view continuity fails | [Character asset](references/routes/character-asset.md) |

For mixed or ambiguous requests, read [Routing contract](references/core/routing-contract.md).

## 3. Add at most one auxiliary route

Use an auxiliary route only when a critical region uses a different medium or a second method is necessary. Bind it to that region; it must not replace the primary route's success criteria.

- Product advertising poster: `ad-poster-cover` + `product-packaging`.
- White-background product hero: `product-packaging` + `photo-editorial`.
- Poster with a 3D hero object: `ad-poster-cover` + `3d-cg`.
- Live-action character turnaround: `character-asset` + `photo-editorial`.
- Cinematic six-view environment board: `spatial-architecture` + `cinematic-scene`.
- Illustrated academic mechanism figure: `information-design` + `illustration-graphic`.

Do not load a third visual route. When three routes seem necessary, keep one primary, one auxiliary, and express the remaining need through a control module or a concrete visible fact.

## 4. Activate only triggered controls

Controls are cross-cutting and do not count as auxiliary routes.

| Trigger | Read |
|---|---|
| Exact copy, labels, data, brand names, or dense text | [Exact text](references/controls/exact-text.md) |
| Identity, product, packaging, logo, or legal copy must remain stable | [Identity and product lock](references/controls/identity-product-lock.md) |
| Fixed panel count, grid, world map, or multi-view continuity | [Layout and spatial continuity](references/controls/layout-spatial-continuity.md) |
| One or more reference images, source priority, or a reusable series | [Reference roles and series](references/controls/reference-roles.md) |

For a mask edit, the edit operation file is required even if a control file also applies.

## 5. Build and compile

For every prompt deliverable, read [Prompt compiler](references/core/prompt-compiler.md). It defines requirement priority, prompt order, copy inventory, minimum sufficient constraints, and bilingual fidelity.

Privately separate:

- **hard requirements** — exact copy, count, identity, product geometry, required layout, preservation rules;
- **preferences** — mood, palette, styling, lens character, decoration;
- **assumptions** — low-risk inferred details needed to finish the brief.

Resolve conflicts in that order. Ask one short question only when the answer changes the route or a hard requirement: exact copy, non-negotiable identity/brand rules, reference-image roles, platform/canvas, or a legal likeness requirement. Otherwise state a reasonable assumption and proceed.

## 6. Verify by route

Use the primary route's acceptance checklist before polishing. Check hard structure first:

1. artifact shape, count, hierarchy, layout, and crop;
2. identity, product geometry, information topology, or world map;
3. exact text and data;
4. medium, material, physical light, and capture behavior;
5. decorative detail.

For failures, preserve working clauses and change one main control variable per iteration. A prettier result is not an improvement if it damages hard structure.

## 7. Keep execution outside this Skill

Do not recommend or output model selection, dimensions, quality levels, file formats, compression, API fields, or tool configuration. Describe canvas shape, crop, visible background, and transparency only when they are part of the image brief itself. If the user also wants the image generated, finish the prompt deliverable and leave execution to the user's image-generation workflow.

## Output contract

For a normal prompt deliverable, default to:

```markdown
路由
- 操作：[operation]
- 主路由：[primary]
- 辅助：[none or one]
- 控制模块：[only activated controls]

中文 PROMPT
[faithful Chinese prompt; preserve quoted in-image copy]

English PROMPT
[faithful English prompt; preserve quoted in-image copy]

验收重点
- [one to three route-specific checks]

---
下一步：[one concrete handoff or verification action]
```

For debugging, add `问题诊断` before the prompts. For editing, add `参考图职责`, `Change only`, and `Preserve exactly`. Default to both Chinese and English prompts. Omit route disclosure if the user asks for only the copyable prompts. Honor an explicit user format over this default.