52 lines
2.4 KiB
Markdown
52 lines
2.4 KiB
Markdown
# GPT Image 2 Advisor Prompt Quality Investigation
|
|
|
|
## Purpose
|
|
|
|
This investigation tests a workflow premise before any GPT / video-workbench restructuring:
|
|
|
|
> If Codex uses the `gpt-image-2` skill in Advisor mode and combines it with the accepted GPT director knowledge, the resulting image prompts should be stronger than ordinary GPT direct prompts.
|
|
|
|
This is a prompt-text quality test only. It does not validate final image quality because no image generation is performed.
|
|
|
|
## Scope
|
|
|
|
The test compares two prompt styles across five representative video-workbench scenes:
|
|
|
|
1. Direct prompt: a normal prompt written without consulting `gpt-image-2` templates.
|
|
2. Advisor prompt: a prompt rendered after reading the relevant `gpt-image-2` skill guidance and templates.
|
|
|
|
The current environment was checked with the skill's mode detector. It returned `B-or-C`, with Garden disabled and no local API key. This investigation forces Mode C / Advisor: save and compare prompts only.
|
|
|
|
## Skill References Read
|
|
|
|
- `gpt-image-2/SKILL.md`
|
|
- `references/prompt-writing.md`
|
|
- `references/portraits-and-characters/professional-portrait.md`
|
|
- `references/portraits-and-characters/character-sheet.md`
|
|
- `references/portraits-and-characters/pose-reference-sheet.md`
|
|
- `references/storyboards-and-sequences/cinematic-storyboard-grid.md`
|
|
- `references/scenes-and-illustrations/concept-scene.md`
|
|
- `references/slides-and-visual-docs/dense-explainer-slides.md`
|
|
|
|
## Files
|
|
|
|
- `mode-check.json`: local mode detection result.
|
|
- `cases.md`: test cases and expected prompt risks.
|
|
- `outputs/direct-prompts.md`: baseline direct prompts.
|
|
- `outputs/advisor-prompts.md`: Advisor-style prompts.
|
|
- `comparison.md`: rubric, scores, and conclusion.
|
|
|
|
## Directory Decision For Future Work
|
|
|
|
This investigation uses a root-level `investigations/` directory because it is validating an assumption, not running a production project or automated test suite.
|
|
|
|
If this premise is accepted, stable workflow documentation should move into `docs/`. Project-specific outputs should remain under `projects/<project-id>/`.
|
|
|
|
For projects with recurring human character imagery, this investigation supports adding:
|
|
|
|
```text
|
|
projects/<project-id>/makeup-still/
|
|
```
|
|
|
|
Use it only when a project has a character / human identity package. It should hold makeup-still prompts, generated or externally produced makeup-still images, reference-role notes, and acceptance records. Projects without visible characters do not need this folder.
|