01Choose the right kind of reference
Reference images can serve different purposes. Decide whether you need scene content and composition, an aesthetic direction, or a specific subject’s visible features. Keep those purposes distinct in your reference register. A style reference is not a subject-identity lock. In a current V8 workflow, subject references belong to the Edit Model route; an explicitly selected V7 comparison uses its own Omni Reference route. Mixing the tools without recording their roles makes consistency hard to diagnose.
02Build an aesthetic language with Style Reference
Choose a small set of descriptive anchors for the visual language: medium, palette, contrast, texture, and lighting character. Use the style-reference input for aesthetic influence while the text prompt describes the scene. Avoid adding so many style instructions that the reference and text compete. Compare the resulting images for coherent visual decisions rather than assuming one style reference makes every subject identical.
03Preserve a subject with the V8 Edit Model
For a current V8 subject-reference exercise, attach the reference images through the Edit Model workflow and describe the desired new scene or change. Identify which visible features matter most: silhouette, garment shape, a color block, or a distinctive accessory. References influence a generative result; they do not prove exact identity, geometry, or brand accuracy. Start with a simple scene so preservation errors can be seen before adding a complex interaction.
04Read older V7 Omni Reference workflows correctly
Older tutorials may use --oref and --ow. Treat them as a labeled V7 path rather than a universal reference recipe. Choose V7 explicitly for that exercise, use its supported Omni Reference input, and keep the result separate from a V8 Edit Model experiment. A compatibility note is part of a reusable prompt. The purpose of this lesson is to interpret and migrate an older workflow without silently mixing its tools into the default model.
05Keep products and environments coherent
Consistency includes more than a face or object. A product campaign needs a stable silhouette, scale story, materials, palette, and background language. An environment series needs a plausible layout and recurring landmarks. Build a short visual specification and inspect each candidate against it. When a generated view changes architecture or label text, record the mismatch rather than presenting it as a reliable alternate view of one real object.
06Audit consistency without promising perfection
Build a rubric that distinguishes identity, aesthetic coherence, composition, and technical suitability. Score each category separately and add a brief observation. A repeated seed, style code, or reference is a recordable input rather than a guarantee that every detail will match. Decide what must be repaired and what variation is acceptable for the intended project. A fictional editorial series can tolerate differences that a real product specification cannot.