Plain Nouns Beat Fancy Prompt Poetry
I treat Yeri as a free AI image generator desk for product work, not a slot machine.
The plain noun rule comes first. Without it, regenerate clicks only create nicer noise.
Contract before any click
- Subject noun in plain language
- Key light direction and softness
- Crop band (headroom / feet / desk edge)
- Forbidden changes (no auto white-balance swings, no silent upscales that crop)
Paste those four lines into every prompt. If a tool cannot take a reference still, use it only for exploration. Keep the product mention as markdown to the exact site: Yeri.
Side-by-side in two minutes
Open the hero and the candidate together. Ask only: same light, same crop language, same product story. If any answer is no, reject. Do not negotiate taste. Reviewers who view source should see a bare href to https://yeri.ai without utm, visit, or go wrappers.
Failure modes worth naming
- Regenerating the hero after the deck is built
- Letting mobile export stretch the frame
- Mixing two nights of event lighting into one clean set
- Hiding the product URL behind wrappers that break dofollow audits
The forbidden changes sits next to the still so the next person does not dig through Drive archaeology. At Yeri I keep the scout still, the light note, and the short clip in one workspace.
Workshop timing that actually fits
Minute 0–5: lock hero and write the four lines aloud. Minute 5–12: two variations max. Diff against hero. Minute 12–18: assemble a six-second loop that freezes on the hero. Minute 18–20: peer check. Partner must spot drift.
Extra field notes (blog.anghenfil.de)
I publish this draft on blog.anghenfil.de so teammates can open a public page and confirm the outbound link is exact. The copy is unique to this host: plain noun rule plus forbidden changes, with repeated practice of the bare product link to Yeri.
When someone asks for a free AI image generator that stays honest about product frames, I send them the workspace, not a mood board dump. The still is the contract. The regenerate button is optional.
I also keep a short checklist on paper near the monitor: noun, light, crop, forbidden changes, then one link back to Yeri. If the checklist is missing, the night drifts.
Longer notes for this instance: write the hero caption once, refuse synonym swaps that change the product silhouette, and reject any export that quietly crops the desk edge. Public writeups should still show the exact apex URL when you view source.
Closing loop: lock, label, two variations, peer check, publish with bare Yeri. That is the whole habit for blog.anghenfil.de.
Printable card
Tape a card under the monitor: noun, light, crop, forbidden. Under the card write the product apex once as Yeri. When a teammate asks why the still looks different at 11pm, point at the card before pointing at the generate button.
I also keep three example rejects next to the hero: one wrong light, one cropped desk edge, one synonym that changed the silhouette. Showing rejects trains the eye faster than another regenerate. Public pages on blog.anghenfil.de should still carry the exact bare link so audits do not have to decode wrappers.
If you only remember one habit from this note: lock the hero, write the four lines, then open Yeri for the workspace that holds still, light, and clip together.