DEV Community: Gedianming Jeremy

A Reference-First Workflow for More Reliable AI Product Images

Gedianming Jeremy — Tue, 01 Sep 2026 05:23:28 +0000

AI product images are quick to generate and easy to misjudge. A polished result can still change a product's proportions, material, label, included parts, or apparent use. The safer workflow is to treat generation as one step in a visual production process, not as the final approval.

This reference-first workflow is for creators, small teams, and product marketers who need usable visual drafts without losing track of what the original product actually looked like.

Start with one visual job

The first decision is not which style words to add to a prompt. It is what the image needs to do.

Choose one primary job:

Listing hero: show the product clearly with enough quiet space around it.
Detail view: make one material, control, texture, or construction detail easy to inspect.
Lifestyle scene: place the product in one believable context without hiding its important parts.
Campaign visual: create a strong composition with reserved space for copy added later.

One image can support a secondary purpose, but it should have one review standard. A lifestyle scene that also tries to be a technical diagram usually makes both jobs harder.

Build a product reference checklist

Before writing a prompt, record the visible facts that must remain recognizable. Use a source image you are allowed to upload, and treat it as a reference rather than a guarantee of exact reproduction.

Your checklist can include:

Silhouette, proportions, and orientation.
Material, finish, and main colors.
Logos, labels, packaging, and visible text.
Functional parts or accessories that belong to the product.
The camera angle and crop that should stay comparable.

This list gives you something concrete to review later. It also prevents a prompt from replacing product facts with vague style language.

Write a prompt contract

Useful prompts separate constraints from visual direction. A short prompt contract is easier to compare across iterations than a paragraph of disconnected adjectives.

Use the supplied product reference as the visual source.

Visual job: [listing hero / detail view / lifestyle scene / campaign visual]
Subject: [what must remain the focus]
Preserve: [silhouette, material, color, labels, and other visible details]
Framing: [camera angle, crop, aspect ratio, and negative space]
Scene: [background and context]
Lighting: [simple lighting direction]
Review boundary: do not invent a feature, accessory, price, or product claim.

The source image already provides much of the scene. The prompt is most valuable when it states what may change, what must remain stable, and where the output will be used.

Choose the workflow that matches the input

Different visual jobs need different inputs. Text-to-image is useful when the concept is still open. Reference-guided generation is more appropriate when identity, product details, or an existing composition needs to carry through. Image-to-video is a separate handoff: the still image becomes the source for a controlled motion direction.

The available controls and supported inputs can vary by model and service. Check the selected workspace before generating, and avoid promising an exact feature match when the workflow does not provide that control.

For a practical workspace that keeps prompt-led image and video tasks together, see Lunalisa. The product supports image creation, reference-led workflows, and short-form video drafts, while the output still needs human review before publication.

Review the output as product content

Do not approve an image because its lighting or composition looks professional. Compare it with the approved source at the size where people will see it.

Use this review order:

Compare the silhouette, proportions, color, and material.
Inspect labels, logos, lettering, packaging, and controls.
Check whether a new accessory or visual detail implies an unsupported feature.
Confirm that the crop and background fit the intended placement.
Add exact price, date, legal copy, and campaign claims outside the generation step.

If a purchasing-relevant detail cannot be verified, reject the variation even when the overall image is attractive. Generated text is especially unsuitable for exact product claims.

Iterate one variable at a time

When the output needs another pass, change one decision. Keep the reference and the product checklist fixed while adjusting only the camera distance, background, lighting, or movement.

Single-variable iteration makes comparisons meaningful. It also creates a reusable record: you can explain why a version was accepted and reproduce the useful direction later.

FAQ

Can AI product images replace product photography?

They can help with concepts, variations, and campaign drafts, but they do not remove the need to verify product facts. Use approved reference material and review every visible detail before publishing.

Should exact text be generated inside the image?

No. Add prices, dates, legal wording, and other exact copy in the final design workflow so the text can be checked independently.

What is the biggest prompt mistake?

Asking one short prompt to solve too many visual jobs. Define the primary job first, then describe the constraints and the review boundary.

Conclusion

A reliable AI product image workflow starts with a permitted reference and ends with a human review, not with a style preset. Define the visual job, record the product facts that matter, choose inputs that match the task, and change one variable at a time. That process makes generated images easier to evaluate and safer to use in real product work.

Disclosure: Lunalisa is my project. This article makes no performance, ranking, or conversion claim, and it does not treat generated imagery as proof of a product feature.

A Practical Workflow for Prompt-Led Product Images with AI

Gedianming Jeremy — Sat, 29 Aug 2026 08:27:32 +0000

Why the brief matters more than the effect list

When an AI-generated product image misses the mark, the problem is often the brief rather than the model. A reliable workflow starts by separating five things:

The subject
The composition
The lighting
The output use case
The details that must remain recognizable

For an ecommerce image, a useful brief might specify the product angle, the amount of negative space for copy, the background material, the light direction, and the intended crop. For a poster, define the message hierarchy first and describe where the empty space should remain.

A repeatable iteration loop

Write a short visual brief before writing a long prompt.
Generate a small set of composition variations.
Compare the results at thumbnail size.
Inspect edges, text, materials, and recognizable product details.
Refine only the strongest direction.
Save the prompt and settings with the final image.

Reference images can clarify framing, material, or styling, but use only media you are permitted to use. When the subject is a real person, consent and usage rights matter just as much as image quality.

Keep prompts structured

A practical prompt structure is:

Subject and purpose
Composition and camera direction
Lighting and environment
Material and detail requirements
Text or branding constraints
Aspect ratio and output context

This structure makes revisions explainable. If the result is too busy, adjust the environment. If the product shape drifts, strengthen the subject and reference constraints. If the image does not work in a listing card, revise the crop and negative space instead of adding more adjectives.

A focused workspace

Lunalisa is an AI image generator for product images, posters, portraits, and other prompt-led visual work. It supports permitted reference media, image model controls, output settings, and free starter credits.

Explore the workspace: https://luna-lisa.art/

The goal is not to remove creative judgment. It is to make each iteration easier to compare, explain, and improve.

Disclosure: This article was prepared with AI assistance and reviewed for accuracy before publication.

Reference Images Don't Preserve Identity by Default

Gedianming Jeremy — Sat, 15 Aug 2026 08:13:36 +0000

A practical identity contract for product, character, and brand-led AI image workflows.

A reference image gives an image model a visual starting point. It does not tell the model which details are untouchable.

That distinction is easy to miss. An output can keep the broad idea of a product while changing its proportions. It can preserve a character's clothing and lose the face. It can borrow a package shape but invent a label. The image may still look polished, yet be unusable for the job that prompted it.

The fix starts before generation. Treat identity as an explicit contract: name the details that must survive, assign each reference a role, and review the result in passes instead of asking whether it simply "looks right."

Identity is a list of protected details

"Keep it consistent" is not a useful review standard. Consistent with what?

For a physical product, identity might include silhouette, dimensions, material, color, visible construction, packaging, and the relationship between parts. For a recurring character, it may include face shape, hair, age range, body proportions, clothing, and a small set of recognizable accessories. A brand-led image may depend on an approved palette, product family, type treatment, or composition rule.

Write those details down before choosing a style or scene. Separate them into three groups:

Protected: details that must remain recognizable.
Flexible: details the generation may reinterpret.
Manually verified: logos, labels, prices, dates, legal copy, and other information that should never be trusted only because it appears in an image.

This turns a vague creative preference into something a reviewer can actually check.

Give every reference one job

Multiple references are useful only when each one adds a distinct instruction. Five unlabeled images can create five competing centers of gravity.

A clearer brief assigns one role to each source. One image defines the subject. Another provides composition. A third contributes material or palette. An environment reference should guide the setting without quietly replacing the subject.

You can write the assignment as a small piece of structured text:

reference_1:
  role: subject identity
  preserve: silhouette, proportions, material, primary color

reference_2:
  role: composition
  borrow: camera angle, negative space, subject scale

reference_3:
  role: environment
  borrow: lighting direction, background context
  avoid: changing the subject design

This is a briefing pattern, not a special API format. Its value is that it forces the author to decide what each image controls.

The Pixonara multi-reference workflow follows the same principle: choose a compatible model based on the sources the job needs, then give those sources defined roles in the visual brief.

Separate preservation from transformation

A useful image-to-image prompt contains two instructions that are often mixed together: what should stay, and what should change.

Suppose the source is an approved product photo and the new output is a campaign image. The protected side of the brief might include the product's form, cap, material, and color. The transformation side might specify a low camera angle, dramatic side light, a wet studio surface, and clear space for final copy.

That can be written directly:

Use the supplied image as the source product.

Preserve the product silhouette, proportions, cap construction, material,
and primary color. Change the camera angle, lighting, background, and crop
to create a 4:5 campaign image. Leave the upper third visually quiet for
copy that will be added during final design.

Treat visible label text as a review item, not a guaranteed fact.

When one main source is being transformed, a focused image-to-image workflow is usually easier to reason about than a larger reference set. Add more sources only when the job truly has more visual roles.

Review the result in passes

A single overall judgment hides small failures. A better review moves from large structural details to smaller visible facts.

Start with silhouette and proportions. If the subject no longer reads as the approved product or character, there is little value in inspecting the lighting. Next check material, color, construction, and any distinctive parts. Then inspect labels, logos, generated text, hands, faces, and edges at full size.

Finish with composition and source interaction:

Did the subject reference control the subject?
Did the composition reference change framing without replacing identity?
Did material or environment references leak unwanted objects into the result?
Is the delivery crop usable in the intended channel?
Which visible details still need replacement or manual verification?

Keep the original sources beside the output during this review. Memory is a poor comparison tool, especially after several attractive variations.

The Pixonara model directory documents current model-specific inputs and output controls. Those controls define what can be attempted; the identity checklist defines what can be approved.

Rejection is part of the workflow

Some outputs should not be repaired with a longer prompt.

If a protected shape has changed, a product variant has been invented, or several references have blended into the wrong subject, reject the image and simplify the brief. Remove unnecessary references. Reduce the number of protected details competing in one pass. Generate the core subject first, then build the environment in a later step when the workflow allows it.

Other failures belong in final design rather than regeneration. Exact campaign copy, legal language, prices, dates, and small packaging text are usually better added and verified outside the generator. The right question is not whether the model can produce something that resembles text. It is whether the final asset can be checked and approved with confidence.

A reference-led workflow succeeds when every important decision has an owner: the source image establishes direction, the brief defines the allowed change, and the reviewer decides whether the result is fit to publish.

A Reproducible AI Product Photo Workflow: Reference, Prompt, Review

Gedianming Jeremy — Fri, 14 Aug 2026 10:08:52 +0000

AI product images are easy to generate and surprisingly hard to review.

A result can look polished while quietly changing the product shape, label,
material, included accessories, or scale. That makes a long, decorative prompt
less useful than a short workflow with clear inputs and a repeatable review
gate.

This article describes a reference-first process for creating product visuals.
It does not assume that an AI-generated image is accurate, marketplace-ready,
or evidence of a product feature.

1. Start with an approved product reference

Use a source image you have permission to upload. Before generating anything,
write down the visible details that must remain recognizable:

Product silhouette and proportions
Material and color
Logo or label placement
Functional parts a customer needs to inspect
Packaging, accessories, and bundle boundaries

This list becomes the review standard. Without it, the only success criterion
is whether the output looks attractive.

2. Give each image one job

A single image should not try to be a listing hero, detail close-up, lifestyle
scene, and campaign poster at the same time.

Choose one visual role first:

Role	Primary objective	Review focus
Listing hero	Show the product clearly against a quiet background	Shape, color, labels
Detail view	Highlight one material or construction detail	Texture, edges, hardware
Lifestyle scene	Place the product in one believable use context	Scale, placement, added props
Campaign visual	Create a strong composition with space for final copy	Brand treatment and generated text

One job gives the prompt a clear priority and gives the reviewer a concrete
definition of success.

3. Write a prompt contract, not a pile of style words

The useful parts of a prompt are the facts to preserve, the role of the image,
the framing, and the review boundary.

Use the supplied product reference as the visual source.

Create a [listing hero / detail view / lifestyle scene / campaign visual]
for [placement or audience]. Preserve the recognizable [material, color,
silhouette, and visible product details]. Place the product [composition and
camera framing]. Use [lighting and scene direction]. Keep the visual focus on
[the product feature or message]. Leave [position and amount] of clean space
for final copy if needed.

Decorative style terms can come last. They should not replace the details that
make the product identifiable.

4. Review the output as product content

Do not approve a result only because it looks professional. Compare it with the
source image at the size customers will actually see.

Use this review order:

Compare silhouette, proportions, color, and material with the source.
Inspect labels, logos, generated lettering, and packaging.
Check whether the image added an accessory or implied an unsupported feature.
Confirm that the crop and background fit the intended placement.
Reject the image when a purchasing-relevant detail cannot be verified.

Exact prices, promotion dates, legal copy, and product claims should be added
in the final design workflow, not trusted to generated lettering.

5. Change one variable at a time

When a result needs another attempt, change one instruction rather than
rewriting the entire prompt. For example:

Keep the product unchanged and simplify the background.
Keep the scene unchanged and adjust only the camera distance.
Keep the composition unchanged and remove unnecessary props.

This makes the next result easier to compare and turns iteration into a process
rather than guesswork.

What this workflow can and cannot establish

This process can make inputs, decisions, and review criteria more consistent.
It cannot guarantee that every generated detail is accurate or that an image
meets the rules of a particular marketplace. Those checks remain a human
publishing responsibility.

I am building this reference-first workflow into Pixonara. You can try the
AI product photo generator
and evaluate the output against your own approved source material.

Disclosure: Pixonara is my project. This article contains no sponsored claim,
benchmark result, or conversion statistic. Any future performance data from
this post will be measured separately from the product workflow itself.

A Better Way to Write GPT Image Prompts: Start With the Visual Job

Gedianming Jeremy — Wed, 12 Aug 2026 06:20:13 +0000

Most prompt advice starts with a pile of style keywords. In practice, I get more consistent results when I write a GPT Image prompt like a short visual brief: define the job, describe the subject, set the composition, and call out the details that cannot change.

I wrote a longer, example-heavy guide here:
https://pixonara.com/blog/how-to-write-gpt-image-prompts

Here is the condensed workflow.

1. Start with the image's job

Say what the image is for before describing how it should look.

Compare:

Create a beautiful image of a watch.

with:

Create a square ecommerce hero image for a stainless steel field watch.

The second version gives the model a use case and a framing constraint. The prompt can then describe the subject without trying to solve every possible image goal at once.

2. Describe what must remain recognizable

For a product, mention the silhouette, material, color, finish, label placement, and any functional detail a customer needs to inspect. For a reference-guided edit, separate what stays from what changes.

For example:

Use the supplied backpack photograph as the visual reference. Preserve the olive canvas,
pocket layout, straps, stitching, and proportions. Change only the setting to a bright
entryway with a wooden chair and soft morning light.

This is more useful than adding another five adjectives about quality.

3. Give the frame a hierarchy

A good prompt tells the viewer where to look. Use concrete composition language such as:

centered subject
three-quarter view
close-up detail
subject on the right third
clean negative space in the upper-left
softly blurred background

Choose one primary focal point. If the subject, typography, background, and lighting are all described as dramatic, the result often becomes visually noisy.

4. Add lighting after composition

Lighting directions are usually easier to act on than broad style labels:

soft window light from the left
hard midday shadows
cool rim light against a dark background
warm sunrise haze

Then add one restrained style cue if it helps: editorial product photography, hand-painted poster, documentary street photography, or cinematic landscape.

5. Treat text as a separate design step

Generated lettering is still something I review carefully. For exact campaign copy, prices, labels, legal wording, or logos, I ask for a calm area of negative space and add the final text afterward.

Leave the upper half low-detail for final event text. Do not render words, dates, logos,
or decorative borders.

This keeps the generated image useful even when typography needs to be precise.

A reusable prompt skeleton

Create a [image type] of [main subject] [action or state].
Place it in [setting]. Use [composition and viewpoint], with [lighting].
Make [key detail] the focal point. Preserve [constraints].
Leave [position] clear for [optional copy].

When the output misses the target, revise one variable at a time. If the subject is right but the framing is wrong, change only the composition sentence. If the material is wrong, make the material and its lighting more explicit. Controlled iteration makes it easier to learn which wording actually helps.

A final review checklist

Before using the image in a listing, campaign, or public post, check:

Is the subject recognizable and accurate?
Are the object count, proportions, labels, and visible text correct?
Does the composition leave room for the final layout?
Did the model introduce an unverified feature, accessory, or claim?
Is the image appropriate for the channel where it will appear?

The goal is not the longest prompt. It is a prompt that makes the visual intention and the important constraints easy to understand. The full guide includes five complete examples for products, portraits, travel scenes, posters, and reference-guided variations.

A Prompt Is Not a Spec: A Structured Input Pattern for Image Generation

Gedianming Jeremy — Tue, 11 Aug 2026 09:28:13 +0000

If an image model keeps making attractive but unusable assets, the issue is often not the model. The prompt is being asked to behave like a full production specification without any structure.

For repeatable visual work, use five fields before you write prose:

SUBJECT: What must remain identifiable?
JOB: What business or editorial task must the image perform?
SCENE: Where is it, and what is happening?
COMPOSITION: Camera, crop, aspect ratio, and copy-safe space.
GUARDRAILS: Things that must not appear or change.

Here is a compact example for a product campaign:

SUBJECT: matte-black insulated water bottle, exact cylindrical silhouette
JOB: launch visual for a premium hydration product
SCENE: quiet sunlit kitchen, pale stone counter, one folded linen napkin
COMPOSITION: three-quarter view, bottle on right third, empty upper-left area for a headline, vertical 4:5 crop
GUARDRAILS: no hands, no extra labels, no warped cap, no readable generated text

The JOB line is the key. Without it, there is no reason for the generator to preserve empty space instead of adding more visual detail. It also tells reviewers what matters: an asset can be attractive and still fail its job.

I separate two constraint types:

Identity constraints protect the product or reference subject.
Layout constraints protect the downstream use of the image.

Identity drift is obvious. Layout drift is just as expensive: no room for a CTA, a crop that breaks on mobile, or a focal point hidden behind UI.

Run the same structured input through several visual directions. Keep subject and job fixed; vary the scene or lighting. That creates a meaningful comparison rather than a collection of unrelated generations.

Pixonara brings prompt discovery, reference-driven generation, image and video creation, and output history into one workspace. The practical goal is not “ask for an image.” It is to build, test, and review a visual specification.

Building Better AI Product Visual Workflows with Prompts, References, and Review

Gedianming Jeremy — Mon, 10 Aug 2026 04:23:01 +0000

AI image generation is most useful when it is treated as a repeatable workflow instead of a one-shot prompt box.

Here are three practices that make a meaningful difference for product and marketing visuals.

1. Start with a visible brief

Write down the subject, composition, lighting, intended frame, and the one detail that must not change. A concrete brief gives the model a direction that can be checked afterwards.

2. Use references only when they are permitted

Reference images can preserve product shape, brand details, or visual mood. They work best when the instruction explains exactly what the reference should guide and what may change. Keeping source permission explicit is just as important as the generation settings.

3. Make review part of the workflow

Before publishing an output, check readable text, product accuracy, crops, background artifacts, and whether the result is suitable for the actual channel. This turns generation from a novelty into a production step.

These ideas are the basis of Pixonara, a browser-based workspace for exploring GPT Image and Nano Banana prompts and creating reference-guided product images, white-background shots, posters, and short videos.

What review checks do you use before shipping AI-generated product visuals?

I Curated 1,500+ AI Product Photography Prompts. Here's What Actually Works

Gedianming Jeremy — Sun, 09 Aug 2026 09:10:51 +0000

Over the past few months I've been building an AI image workspace, and part of that work meant reviewing a lot of product photography prompts — over 1,500 of them, across GPT Image, Nano Banana (Gemini), and Midjourney. Most were mediocre. A few patterns consistently produced commercial-grade results.

I open-sourced the best templates and 122 image+prompt pairs here: awesome-ai-product-photography-prompts (CC0, free to use commercially).

This post is the distilled version: the five patterns that separate usable product shots from AI-looking junk.

1. Product truth first, style words last

The single biggest quality difference. Weak prompts front-load atmosphere ("cinematic, 8k, award-winning...") and mention the product as an afterthought. Strong prompts pin the product's physical facts before anything else:

Ultra-realistic minimalist product photography of a small transparent
glass facial oil dropper bottle with a black rubber pipette top...

Material, container type, closure, color — stated explicitly. The model can't hallucinate what you've pinned down.

2. Fictional branding beats no branding

Counterintuitive: prompts that invent a brand name ("NOIR BREW coffee", "VOLT RUSH energy drink") produce dramatically more convincing packaging than prompts that avoid labels entirely. The model composes a full label design around the name — typography, hierarchy, the works.

Two rules:

Invent the name. Never use a real brand (trademark trouble, and the model will just clone the real trade dress).
Quote it in the prompt: labeled "HUNSET" — quotation marks strongly improve text rendering accuracy.

3. One image, one job

The prompts that fail hardest try to do everything: hero shot + lifestyle context + ingredients + text overlay space. Every strong prompt in my collection has exactly one job:

Packshot: product centered, seamless background, even light
Detail: macro on one material or feature
Lifestyle: one believable moment, product stays the focal point
Campaign: dramatic single concept with negative space for copy

Same taxonomy works for image-to-video: one main motion, one supporting motion, explicit camera behavior.

4. Describe light like a photographer, not an adjective machine

"Beautiful lighting" does nothing. What works is naming the setup:

...warm sunlight filtering through wheat stalks from behind, creating
glowing translucency inside the honey and soft halo edges around the jar,
shallow depth of field, shot on 90mm macro lens, f/2.2

Direction, quality, and what the light does to the product. Lens and aperture references reliably shift the output toward commercial photography conventions.

5. Never generate your claims

The one rule with real-world consequences: AI lettering is a mood, not a source of truth. Prices, product names, dates, legal text — add them in your design tool after generation. Every "AI product photo fail" screenshot you've seen is someone violating this.

Browse the full collection

All 122 examples with their complete prompts are in the GitHub repo — organized into product photography, food & drink, and poster design. Each image links to a live page where you can run the prompt against your own product.

The underlying gallery (1,500+ prompts with generated results) is free to browse at Pixonara — no signup needed to view prompts.

If you've found prompt structures that consistently work for product content, I'd genuinely like to see them — PRs to the repo are welcome.