Keeping a Prompt Library That Stays Useful - Nano Banana 2

A prompt on its own is not a record. The minimum useful entry is the prompt plus the image it produced, stored together so you can see them at a glance. Add the seed if you have one, since a prompt with a seed is reproducible and a prompt without one is only a tendency.

Just as important is a note on reliability. There is a real difference between a prompt that gives you what you want most times you run it and one that gave you a single lucky frame out of thirty. Both look identical in a text file, and only one is worth reusing. A word or two — “consistent”, “one good take in twenty” — saves you from rebuilding an entire session on a fluke.

Within a job, keep one canonical prompt and treat everything else as a variant of it. Variants that differ by a single clause belong as annotations under the parent, not as separate entries. A library of two hundred flat entries is a pile; the same content as fifteen parents with notes underneath is something you can read.

The failure mode of a growing library is that it starts dictating your work. You reach for a saved prompt because it is there, not because it fits, and your images converge on whatever you happened to save first. Deleting is part of maintenance.