Luma’s “@style” Trick → Veo3Gen: Build a 10‑Shot On‑Brand Lookbook From One Reference (as of 2026-05-25)

Most teams don’t need more prompt theory. They need repeatable outputs: the same vibe, the same “camera language,” and the same brand feel—week after week—without re-inventing the prompt every time.

This post shows a practical mini lookbook method you can run in Veo3Gen: lock your aesthetic once (inspired by Luma’s guidance around Visual Reference + “@style”) and then generate 10 reliable shot types you’ll reuse forever.

Important note (as of 2026-05-25): Luma’s “@style” is a specific Dream Machine workflow for using an uploaded image as a visual reference. We’ll treat it as an idea you can port into Veo3Gen—not a claim that Veo3Gen has the same UI feature.

Why “style drift” happens (and why prompts alone don’t fix it)

Style drift usually isn’t because your prompt is “bad.” It’s because your prompt changes implicitly from shot to shot.

Common causes:

You describe the product differently each time.
You keep adding extra adjectives (“cinematic,” “editorial,” “film”) without defining what those mean.
You change locations/wardrobe/lighting and camera at the same time, so you can’t tell what actually affected the look.

Luma’s own best practices encourage using natural, detailed language and being specific about style, mood, lighting, or elements to get more accurate results. (https://lumalabs.ai/learning-hub/best-practices)

That’s helpful—but to stay on-brand, you also need something prompts rarely provide by default: a stable anchor.

What Luma means by “@style” (and the Veo3Gen equivalent mindset)

In Luma Dream Machine, Visual Reference is described as uploading an image and using “@style” followed by a prompt. (https://lumalabs.ai/learning-hub/best-practices)

Think of “@style” less as a magic token and more as a workflow pattern:

Pick one reference that already nails the brand look.
Use it consistently as the visual north star.
Write prompts that describe the scene without rewriting the entire style definition every time.

In Veo3Gen, you can apply the same mindset even if the mechanism differs: keep one style anchor block you paste into every prompt, and keep your shot prompts focused on what changes.

Step 1: Create your 1-page style anchor (the 7 fields to lock)

Your style anchor is a reusable block that stays short, repeatable, and brand-specific. It should communicate: palette, lighting, lens/camera vibe, textures, era, mood—and a little composition guidance.

Here are 7 fields to lock (copy this structure):

Brand palette: 2–4 colors + neutrals
Lighting recipe: soft/hard, direction, contrast level
Camera & lens vibe: e.g., handheld vs locked; wide vs portrait; lens “feel”
Materials/textures: e.g., matte paper, brushed metal, cozy knit
Era / references: “modern Scandinavian,” “early-2000s glossy ad,” etc.
Mood words: 3–5 adjectives max
Framing rules: negative space, center-weighted, rule-of-thirds, etc.

Example style anchor (pasteable)

Use this as a starting point and replace the details:

STYLE ANCHOR (paste into every prompt):

Palette: warm off-white + charcoal + one accent color (muted teal)
Lighting: soft key from camera-left, gentle falloff, clean highlights, minimal harsh shadows
Camera language: steady tripod feel, slow intentional moves, premium product-ad framing
Textures: matte ceramics, natural wood grain, subtle paper texture
Era: contemporary minimalist lifestyle commercial
Mood: calm, confident, approachable, clean
Framing: generous negative space for overlays, uncluttered backgrounds

Luma’s best practices specifically recommend being clear about style, mood, lighting in prompts. (https://lumalabs.ai/learning-hub/best-practices)

This is your shot menu: a fixed set of shot types you generate in the same style. You’ll reuse these across launches, weekly content, and new variants.

Hero product shot (clean “poster” composition)
Hands-in-frame demo (UGC-adjacent, tactile)
Lifestyle wide (context + environment)
Macro detail (texture, logo emboss, ingredient swirl)
Testimonial setup (talking-head background plate / “ready for VO”)
Pack shot turntable (slow orbit / rotating pedestal)
UI overlay shot (negative space for captions, hooks, CTAs)
Before/after (split-frame or match-cut concept)
Logo end card (simple, brand-safe finish)
Seasonal variant (same setup, seasonal prop swap)

If your team is small, this list becomes your content spine. The goal is not “10 random cool videos”—it’s 10 repeatable utilities.

Step 3: Generate in batches: base pass → variations pass → fix pass

This is where consistency becomes a system.

Base pass (generate all 10 with one anchor)

Paste the same style anchor into every prompt.
Only change the shot description.
Keep product name, packaging details, and hero props consistent.

If you’re coming from Luma: their best practices frame prompting as iterative—use tools like Modify to adjust visuals by describing specific changes (e.g., warmer colors, more trees). (https://lumalabs.ai/learning-hub/best-practices)

In Veo3Gen, treat revisions the same way: ask for specific deltas, not a brand-new prompt.

Variations pass (one variable per batch)

Now make controlled variations where only one variable changes per batch:

Batch A: change wardrobe only (same location, same lighting)
Batch B: change location only (same wardrobe, same time-of-day)
Batch C: change time-of-day only (same location, same wardrobe)

This is the fastest way to learn what your model responds to—and it prevents “mystery drift.”

Fix pass (surgical corrections)

Pick 2–3 shots that are almost right, then do a fix pass:

tighten palette (“less saturated, keep neutrals creamy”)
correct lighting direction (“key light from left”)
simplify props (“remove extra objects, keep one hero prop”)

If you’re using Luma, note they also describe Camera Motion options like Pan, Orbit, or Zoom—language you can borrow to be explicit about movement. (https://lumalabs.ai/learning-hub/best-practices)

Step 4: A/B check for consistency (a simple scorecard for small teams)

Don’t rely on vibes. Use a tiny scorecard so anyone on the team can QA.

Consistency scorecard (5 checks)

Rate each shot 1–5:

Color palette: does it stay within the brand colors?
Lighting direction: is the key light consistent (and plausible)?
Camera language: similar lens feel, movement style, framing rules?
Subject identity & props: product details consistent; no random extras?
Typography treatment (if any): placement, contrast, and “feel” consistent?

If a shot scores low, don’t rewrite everything—change one lever (lighting, palette, props, or camera).

Common failure modes (and what to change first)

1) You’re overusing negative prompting

Luma’s prompting guidance recommends a positive-only approach for optimal results, and defines negative prompting as instructing the AI to exclude elements. (https://lumaai-help.freshdesk.com/support/solutions/articles/151000219614-understanding-prompting-for-dream-machine-positive-vs-negative)

They also warn negative prompting can be counterproductive (e.g., telling it to exclude people can cause the system to add them and then try to remove them). (https://lumaai-help.freshdesk.com/support/solutions/articles/151000219614-understanding-prompting-for-dream-machine-positive-vs-negative)

Portable takeaway for Veo3Gen: describe what you want, clearly and consistently, before you start listing what you don’t want.

2) Your anchor is too long (and contradictory)

If your style anchor reads like a novel, you’ll accidentally introduce conflicts (“high contrast” + “flat soft light” + “no shadows”). Make it short.

3) On-screen text is fragile

Luma notes you can ask for text in generations by specifying the wording (example: a poster with text that reads “Dream Machine”). (https://lumalabs.ai/learning-hub/best-practices)

In practice (across tools), on-screen text can be finicky—so for brand work, consider:

Minimize text in-generation
Reserve text for end cards or editable overlays
If you must generate text, keep it short and high-contrast

4) You changed too many variables at once

Go back to the batch method: base → single-variable variations → fixes.

Copy-paste templates: 10 lookbook prompts + 3 variation prompts

Use these as prompt starters. Replace bracketed parts.

Your reusable style anchor (paste into every prompt)

STYLE ANCHOR: Palette: [brand colors]. Lighting: [direction + softness]. Camera: [steady/handheld + lens vibe + motion]. Textures: [2–3]. Era: [reference]. Mood: [3–5 words]. Framing: [negative space rules].

Hero product
- [STYLE ANCHOR] Clean hero shot of [product] on a simple surface, centered composition, subtle shadow, slow push-in, premium commercial feel.
Hands-in-frame demo
- [STYLE ANCHOR] Close shot: hands demonstrate [key action] with [product], tidy background, realistic motion, focus on tactile details.
Lifestyle wide
- [STYLE ANCHOR] Wide lifestyle scene: [product] in use in a [room type], minimal props, natural placement, slow pan, calm mood.
Macro detail
- [STYLE ANCHOR] Macro close-up of [feature: texture/logo/ingredient], shallow depth-of-field feel, slow micro-movement, clean highlights.
Testimonial setup (VO-ready plate)
- [STYLE ANCHOR] Medium shot framing of a person seated in a clean setting holding [product], neutral expression, space for captions, subtle background.
Pack shot turntable
- [STYLE ANCHOR] [Product packaging] on a pedestal, slow orbit/turntable motion, consistent lighting, crisp edges, uncluttered.
UI overlay shot (negative space)
- [STYLE ANCHOR] Product on one side of frame with large negative space on the other for UI overlays, gentle gradient background, minimal motion.
Before/after concept
- [STYLE ANCHOR] Before/after style shot showing [benefit] with a clear split or match-cut concept, consistent framing and lighting.
Logo end card
- [STYLE ANCHOR] Minimal end card scene with brand mark area centered, calm lighting, subtle texture background, 2-second hold.
Seasonal variant

[STYLE ANCHOR] Same hero setup as shot #1 but with seasonal prop swap: [seasonal element], keep palette consistent, minimal extra objects.

3 controlled variation prompts (only one variable changes)

Wardrobe-only variation
- Keep everything identical to shot #2. Change wardrobe to [wardrobe description]. No other changes.
Location-only variation
- Keep everything identical to shot #3. Change location to [location]. Same lighting direction and palette.
Time-of-day-only variation
- Keep everything identical to shot #1. Change time-of-day to [golden hour/overcast morning]. Same framing and props.

Quick checklist: run the lookbook in under 60 minutes

Pick one reference frame that matches your brand
Write a 7-field style anchor (keep it short)
Generate the 10-shot base pass
Run single-variable variations (wardrobe or location or time-of-day)
Score with the 5-point consistency scorecard and do a fix pass

FAQ

How many reference images should I use?

Start with one “hero” reference for the overall look. Add a second reference only if you keep failing the same constraint (e.g., product material feel).

Should I use negative prompting to stop unwanted artifacts?

Use it sparingly. Luma’s guidance recommends a positive-first approach and warns negative prompting can be counterproductive. (https://lumaai-help.freshdesk.com/support/solutions/articles/151000219614-understanding-prompting-for-dream-machine-positive-vs-negative)

Can I ask the model to add text on screen?

Some tools support prompting for exact wording; Luma’s best practices give an example of specifying text that reads a particular phrase. (https://lumalabs.ai/learning-hub/best-practices) For brand work, consider keeping text minimal and swapping end cards in editing.

What if one shot looks “off brand” while the others match?

Don’t rewrite your whole prompt set. Change one lever (palette, lighting direction, props, camera motion) and re-generate just that shot.

CTA: turn the lookbook into a repeatable pipeline

If you want this lookbook workflow to run as a dependable production pipeline (brief → batch generation → review → iterations), explore the Veo3Gen API at /api. When you’re ready to estimate cost for weekly content or multi-brand output, see plans at /pricing.

Luma’s “@style” Trick → Veo3Gen: Build a 10‑Shot On‑Brand Lookbook From One Reference (as of 2026-05-25)