A production team cannot afford to re-roll a prompt twenty times chasing a lucky result. The process is now buildable because current-generation models such as Nano Banana Pro handle prompt adherence and text rendering. The remaining work is organizational—writing prompts as specifications, defining acceptance criteria, and versioning visual language like code. The fix is to treat prompts as documented, shared, versioned artifacts. A production prompt is a spec sheet with named fields: SUBJECT, STYLE TOKEN, COMPOSITION, LIGHTING, PALETTE, NEGATIVE, and RATIO. The style token is a frozen paragraph describing the house style that every team member pastes verbatim. Reference-image conditioning is the more reliable mechanism for style locking; the practical setup is a locked folder of three to five approved “golden” images that define the visual identity.