Separate the decisions
A reference image may contain several ideas: a silhouette, a material, a lighting setup and a camera angle. Name the qualities you want to carry forward and those that should change.
For a character, specify which equipment and asymmetric details define its identity. For an environment, distinguish composition from color or atmosphere.
Keep the useful context available
Save project references with a purpose and guidance. Use exact approved asset versions when they should guide later work. Turn off references that no longer fit the direction.
Review feedback belongs beside the result. A specific rejection is more useful than asking for something to be “better”: describe the mismatch and the desired change.
Evaluate the result, not the instruction
A well-specified reference can still produce a result that misses the brief. Compare assets together at gameplay scale and inspect details across views or frames.
Approval is the point where you decide a version is useful. It should follow inspection, rather than simply follow a completed generation.
References and agent context