GameCult/Eureka
Watch
9
0
Fork
You've already forked Eureka
 0
Code Issues Pull requests 3 Projects Releases Packages Wiki Activity Actions
Eureka/doctrine/images.md
Eureka b591951c09 Doctrine: bring agent doctrine into the repo verbatim 
Per ruling doctrine-home-eureka-repo. Copies of the global CLAUDE.md,
six faculty charters, the Self output style and three doctrine files,
byte-identical to their sources. Paths and wording are unedited.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-02 22:13:58 +02:00

1.4 KiB
Raw Blame History

Image generation

Moved out of the always-loaded ~/.claude/CLAUDE.md Working Style. Read before generating an image.

  • Whenever generating an image, save the exact final generation prompt as a durable text or Markdown artifact beside the image. Use matching base filenames where practical, record the generation mode or model path when known, and keep both files in the relevant project workspace when the image belongs to a project. An image without its prompt has lost its provenance and is not a complete deliverable.
  • Render each new image iteration from scratch. Carry successful ideas forward through a rewritten prompt, not by editing or using the previous render as an image reference. Image edit chains tempt the model to preserve local successes while accumulating incoherent anatomy, composition, and style. Use image editing only when the user explicitly asks to modify a particular source image rather than explore the next design iteration.
  • Treat image prompts and their rendered failures or successes as pressure tests for the owning faction, technology, character, or setting documents. When a prompt must repeatedly supply the same unstated design rule to prevent generic or incoherent output, inspect the authoritative lore and promote the durable rule there when it genuinely belongs. Distill the live doctrine rather than copying prompt scaffolding, negative lists, or one image's incidental details into canon.