Quick test for you: ask your AI to make a brochure, then ask yourself how many times it actually looked at the result. Probably zero. It wrote the thing and walked away. Captain YAR says that’s like a painter who never steps back from the canvas. Painters step back constantly. They squint, they tilt their head, they notice the left corner is too busy. Your AI never gets that moment unless you build it into the brief.
🧭 The 60-Second Challenge
A Reddit post in r/PromptEngineering pointed at something Ant Ling described for its new Ling-3.2-flash. Business materials become brochures, and a visual preview guides changes to layout and spacing. The model doesn’t just produce a document. It opens a preview and revises what it sees.
The prompt from the post:
Turn these business materials into a brochure. Open a visual preview of the result, check the layout and spacing, and revise before returning it.
Try it on whatever tool you use for document work. It takes about a minute to set up, and the comparison afterward is the fun part. You are not testing whether the AI can write. You are testing whether it can notice what its own writing looks like on a page.
🛠️ How to Run It
- Grab some real material: a services list, a product sheet, an about page, a pile of messy notes. Messy is actually better. Tidy input hides the layout problems you are trying to catch.
- Paste it in with the prompt above.
- Check whether your tool can actually render a preview. If it can’t, the preview step has nothing to run on. A chat window with no rendering or code execution is a good example of a setup that will just pretend.
- Look at the first draft you get back, then ask for the same job again without the preview line. Use a fresh conversation for this so the first result doesn’t leak into the second.
- Compare the two side by side. Zoom out until you can’t read the words anymore and judge the shapes. Is there breathing room? Does one block dominate? Does anything crash into the edge?
🔍 What the Results Mean
If the preview version has cleaner spacing, fewer cramped blocks and less text spilling over, the inspection step is doing real work. The task now contains both the deliverable and a check on how it looks. You will often see small things first: a heading that no longer sits glued to the paragraph above it, a contact block that finally has room, a list that stopped running off the bottom.
If both versions look the same, your setup probably can’t see its own output. Then “open a preview” is just a polite sentence and nothing more. Good to know before you build a workflow on it. It’s also worth checking whether the tool changed the text at all between drafts. A real revision usually shows some difference, even a tiny one.
💡 Extra Tips
- Make the visual check concrete. One commenter on the thread suggested spelling out what to inspect: margins and overflow, contrast at the intended viewing size, and whether the hierarchy fits the brochure’s purpose. Otherwise “revise before returning” can turn into a vague pass that changes nothing.
- Name the viewing context. A brochure read on a phone and one printed on paper need different checks. Phone readers need bigger text and tighter copy. Print readers forgive denser layouts but notice margins that sit too close to the fold.
- Cap the loop. Say how many revision passes you want. Two is usually enough, and it keeps the agent from fiddling forever. Without a cap, some tools keep nudging a margin by one pixel and call it progress.
- Ask for a short change list. Have it tell you what it fixed after looking. That shows you whether it really inspected anything. If the list says “improved overall layout” and nothing specific, treat that as a warning sign.
- Feed it a reference. If you have a brochure you love, describe what makes it work, like generous whitespace or one strong headline. Give the AI a target to compare its preview against, not just a rulebook.
🎯 Prompt of the Day
Turn these notes into a one-page brochure. Open a visual preview. Check margins, text overflow, contrast at phone size, and whether the headline is the first thing the eye lands on. Revise once, then list what you changed.
The point carries well beyond brochures. Any time your AI produces something meant to be looked at, put the looking in the brief. Slides, flyers, landing pages, reports: same idea. Write the check into the request the same way you would hand a junior designer a checklist before they send anything to a client.
🏴☠ Your Move
Run both versions today and see which one you would actually send to a client. Tell me what the preview step caught in yours!
Frequently Asked Questions
Q: What should the visual check actually look for?
Start with three concrete checks: margins and overflow (does any text or image run past the edge?), contrast at the size people will actually read it, and whether the headline, subheads, and body text order match what the brochure is for. Run each check against the preview and note what you changed. That keeps the revision pass from turning into cosmetic tweaks.
Q: Why not just ask for ‘open a preview and revise’?
Without criteria, the revision pass can spend its time nudging colors and fonts while real problems stay put, like text too small to read or a layout that buries the call to action. Naming the checks up front gives the revision step something to test against. Also say which viewing size you mean, since a brochure that looks sharp on a big monitor can fail on a phone.
Q: Does Ling-3.2-flash come with built-in layout criteria?
The post doesn’t say, and a commenter asked the same question, so treat it as open for now. Until the docs confirm it, put your own checklist in the prompt. The margins, contrast, and hierarchy checks make a good starting point, and you can add brand rules like a minimum font size.
Ling-3.2-flash’s brochure workflow includes opening a visual preview before revising
by u/Hot_Librarian264 in PromptEngineering