Identity Reference, Moodboard, or Product Shot? Give Each Image One Job

Use an identity reference when a recurring person or character must remain recognizable. Use a moodboard or style example when the goal is to guide lighting, composition, texture, color, and overall visual character. Use a product shot or interface reference when the product itself must be depicted or checked against reality.

Those jobs are not interchangeable. A stylish portrait does not prove the shape of a product. A clean product screenshot does not define an entire campaign's visual taste. A moodboard featuring a person does not give permission to reproduce that person's identity or guarantee that a generated subject will remain consistent.

This guide uses the three terms as an editorial routing system. In AttentionClaw, product visuals and saved style direction can inform a slideshow draft, while creator-identity workflows depend on the configured profile and a compatible image setup. In every case, the generated image still needs human review.

Write the preservation target beside every uploaded image.

The matrix below is the smallest useful artifact for a visual brief. It separates the intended job, the details that deserve review, the details the image must not silently control, and the condition that should cause rejection.

A single source image may appear in more than one row only when the rights, intended uses, and preservation targets are explicit. Separate files are usually easier to review.

A reference pack for a recurring creator should be intentionally boring: clear views, current appearance, neutral lighting, and explicit permission. Its job is recognition, not art direction. Add style separately so a dramatic moodboard does not become the only evidence of what the person looks like.

Not every app carousel needs a creator. If the story is about an interface workflow, adding a person can create unnecessary identity risk and consume visual attention that should belong to the product. Write “no identity reference needed” in the brief rather than leaving the field ambiguous.

Reference handling depends on the selected image configuration. If the configured workflow cannot use the required identity inputs, stop and choose a compatible setup or change the concept. Do not continue with a generic substitute and present it as the approved person.

A useful moodboard contains a coherent visual argument. Label the features that matter: soft side light, restrained indigo and cream, one coral accent, quiet workspace surfaces, generous negative space, and close phone framing. Without those labels, reviewers may disagree about whether the intended reference was color, camera angle, wardrobe, or subject matter.

Moodboards should not carry unsupported product claims. A screenshot, testimonial, price, certification, or recognizable person that happens to appear in inspiration should not migrate into the draft. Describe the visual principle and remove incidental material that the campaign is not authorized to reproduce.

AttentionClaw's public maker workflow describes saved brand direction as part of the draft. That direction still needs a human-owned style definition and review. A moodboard can help communicate taste; it cannot approve itself.

1. 1

   Name the repeated visual rule

   Write what should recur across the sequence, such as quiet daylight, tight product crops, and one warm accent.

2. 2

   Name the allowed variation

   State what may change from slide to slide, such as setting, hand position, or background object.

3. 3

   Name the forbidden borrowing

   Exclude recognizable people, logos, copy, products, and distinctive compositions the campaign is not authorized to reproduce.

For an app, product evidence may be a current screenshot, a generic interface reference, or a documented workflow. For a physical item, it may be a neutral product shot plus detail views. Label the asset with the variant, screen state, date, and detail the draft is allowed to explain.

A product reference is not a guarantee of exact reproduction. If exact screen copy, pricing, controls, label text, packaging, or regulated detail matters, the reviewer should compare against the original and use the original asset in the final composition when regeneration would make the evidence less trustworthy.

The public AttentionClaw examples make this boundary visible. They identify generic interface references and fictional apps, then list the claims removed in review. That is a stronger pattern than presenting attractive demonstration art as proof of a live product or campaign result.

The fictional Focus Flow worked artifact below supplies a generic timer-interface reference and an indigo, cream, and coral visual direction. It does not need a recurring person. The correct routing therefore leaves the identity row empty instead of forcing every reference type into the project.

The completed worksheet below shows what each input can and cannot authorize.

Run this checklist before generation and again before approval. If the answer to any required question is unknown, stop and resolve the source pack rather than hoping the generated image will clarify it.

AttentionClaw can combine product context, product visuals, a brief, and saved brand direction into a reviewable slideshow or carousel draft. Its fictional examples expose the supplied inputs and human edits so the reader can inspect the production logic rather than infer campaign results.

The product does not grant rights to a reference, turn a moodboard into product proof, guarantee identity or product fidelity, or approve the final asset. The team must label every source, choose a compatible setup, review the generated result against the original, and use the current platform publisher as the final authority for the post.