DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to keep one character consistent across new scenes with GPT Image Skill

Reuse a character reference file to place the same person or mascot into several new scenes.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forA children's book author, game artist, or brand designer who needs one recurring character shown in many settings.

The problemDescribing a character in text drifts between images, while the same reference file keeps identity more stable.

The outcomeA set of PNG scenes featuring the same reference character, each in its own file.

What you need first

  • A ChatGPT or Codex plan that permits image generation (the README says Codex image generation is not available on the Free plan)
  • Node.js 22 or newer
  • Git, for installing from GitHub
  • Codex CLI signed in with ChatGPT, or a host that provides subscription-native image_gen

Steps

  1. Save the character reference as a PNG, JPEG, or WebP file inside the project, for example at references/character.png.
  2. Ask for a scene with /gpt-image Use @references/character.png as the character reference and place it in a rainy city, 9:16, high quality. in Claude Code.
  3. Repeat the request for each scene, keeping the same reference path in every job.
  4. Check that each returned PATH shows the same character before you use the set.

Prompt for your agent

Using GPT Image Skill in <repo path>, generate <number> scenes using <character reference path> as the reference in each job, with the scene descriptions <scene list>. Expect one PNG per scene under /generated-images. Verify the reference file is attached in every job, not replaced by a text description.

Caveat. The README says a host-attached image is not automatically inherited by the nested codex exec process, so the reference must be a readable file in the project.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page