Most kits die in the first hour because nobody picked the room.
Someone generates a warm bakery. Someone else generates a cream flat lay. Someone else generates dusk. All three go on the homepage. The loaf changes. The light changes. Visitors think it is three businesses.
A mood still is a direction, not a campaign. You try the light. You pick one look. Then every later file has to stay in that room.
The picture at the top is the morning look we kept: one unbranded loaf, window light, a real counter. It is not a logo. It is not a clip. It is the vote.
Three looks is research. Shipping all three is a new brand every scroll.
Generate the looks, not the kit
Use /image and a quick route. You are shopping for light, not finishing a product page.
Design a bakery counter hero, one unbranded loaf, morning window light, linen, cream walls. No readable text or logos.

Name what has to stay true in every option: the same loaf, the same shop, no readable text. Change only the look — product light, a flatter graphic set, dusk. If the loaf itself changes, you did not generate options. You generated three products.
Do not bake hours or a street number into a mood still. Those are facts you supply later, in type you can still edit. What AskGL is, in plain English is the same rule: the command shapes the file. It does not invent the Saturday hours.
A dusk still with a letter on the wall is not a direction. It is a new shop with a fake sign. Reject it. Keep the look that still has one loaf and no type in the pixels.
Pick one winner, then attach it
Once the morning still is the one you would actually print, stop rolling new bakeries. Name the accepted file. The next request inherits it.
Same accepted bakery world: one unbranded sourdough loaf on linen, morning window light. No readable text or logos.

@out:shop-dir-product is the mood still. You are not asking for a new loaf. You are asking for care on the room you already chose. That is How to take one AskGL result into the next step.
A hero is still /image, not /images. If you needed four views of the same loaf, say so after the lock. When to use /image instead of /images.
What the rest of the kit inherits
After the lock, the mark, the pictogram, and the clip all have to feel like this counter. If a later file looks like milk bread from another aisle, it is not in the kit. It is a stray.
The mark is /logo, paths, no letters. The pictogram is /icon attached to the accepted mark. Motion is /video attached to the accepted hero, with a duration. None of those jobs should invent a second shop.
Spaces can hold a moodboard later. Brand Moodboard is still an internal kit shape. This essay does not claim a public Space walkthrough. The living work is Ask, then Image Editor or Design Editor when you need to crop or set type.
If you need a proven starting point instead of folklore, browse Queries. Do not invent a /for-bakeries page. There is no fourth ranking family for a neighborhood loaf.
Lock, then stop shopping
Teams keep generating because it feels like progress. It is usually drift.
When the morning still is honest, write it down. Use @out: for the next file. If Ask blocks an illegal frame or a photograph-as-logo, rewrite the request. Do not spend the kit on a look you already rejected.
Then open Ask. Generate the looks. Pick one. Attach it. That is a brand mood, not a pile.
Frequently asked questions
How many looks should I generate?
Enough to choose. Three is a useful set: warm product light, a flatter graphic look, a dusk still. Pick one winner. Do not ship all three as the same shop.
Is a mood still the final hero?
Not always. A quick route is for the look. Attach the winner with @out: and ask for care if the object has to survive a product page.
Can I mix three styles on one homepage?
No. That is three shops. Lock one world, then inherit it.


