Lesson 26 of 32

The Law of the Loop

Prompt, Read, Refine

The first prompt is the opening move, not the whole game. Work in a loop instead: decide what you want before you type, send a good-enough prompt, read the answer against that aim, then tell the model exactly what to keep, cut, add or change - and when the answer is finally right, save the prompt as a template so tomorrow you start where today you finished.

Reach for it whenAny time the first answer is close but not usable - a plan, a letter, a message, a table you will actually act on - and especially when you will need the same thing again next month.

The chapter was written here, so the loop itself needs no translation - what changes is where each step can live. The Read step gets help you do not have elsewhere: for anything with dates, fees or timings in it, ground the answer in Search and check the sources before you refine, because refining a wrong fact only polishes the error. The Prompt step can take a file rather than a paragraph - photograph your school timetable or the shop's rate card and upload it instead of typing it out. And Reuse has two homes: a Gem holds the winning prompt as a standing persona, and the finished plan exports to Google Docs, where it stops being a chat message you will lose and becomes a document you can share with your family or print.

From the book Refine in the same chat, and when a plan or draft is right, export it to Google Docs so the final version is safe. Turn a winning prompt into a Gem with standing instructions - the same prompt works on all three platforms, so your templates travel with you.
Worth knowingGrounding needs aiming rather than leaving on. On the Varanasi itinerary it is essential - timings and fares change. On the tailoring message it actively hurts: search the phrasing of a festival greeting and you get the generic marketing copy of a thousand other shops, which is the opposite of sounding like yourself. Say "do not search, write in my own voice" on the creative rounds. One more thing worth knowing: exporting to Docs ends the loop for that copy. Later refinements happen in the chat and do not flow into the exported document, so export when you are done, not halfway.
  • Ground anything with dates, fees or timings; check the links.
  • Say "do not search" on creative rounds - it flattens your voice.
  • Upload a photo of the timetable or rate card instead of typing it.
  • Export to Docs when the loop is finished, not midway.
  • Save the winning prompt as a Gem so templates travel with you.
The One-Shot Gamble vs. The Five-Step Loop

Instead of

Make me a study plan for science.

Gemini version

[Attach a photo of your school timetable, and one of the contents page of your Science textbook.]

I sit the CBSE Class 10 Science board paper in Patna on [exam date] - four weeks from today. School days give me two hours; Sundays, five. Chemical reactions and carbon compounds are where I lose marks. Biology I can already handle.

Ground this in Search before you plan anything: confirm from a CBSE page what this year's paper covers and whether any unit has been rationalised, and give me the link. If only coaching websites make the claim, say so rather than repeating it as fact.

Then work from my attached timetable. Build around the slots already taken by school tests, not around an imaginary free week.

Lay it out as a table - Week, Day, Topic, Task (read, practise or test) - with a full paper every Sunday and marking time that evening. Plain wording, nothing encouraging. Add one line saying how you split the hours between my weak and strong ground.

I will export the finished table to Google Docs to print, so keep the formatting simple enough to survive that.
Open Gemini 1,077 characters

Then loop it

  1. Hold the table and the Sunday papers as they are. Cut the loose Biology days in Week 1. Add 20 minutes of equation practice to every school day. Change Week 4 so it is revision and past papers only. No searching this round - just edit what is there.
  2. Done. Export that table to Google Docs so I can print it and show my father. Then write the whole thing up as standing instructions for a Gem called "Exam plan maker", with blanks for [subject], [weak topics] and [exam date], including the rule about grounding the syllabus in Search first.

Why it worksIt starts from a written aim, then uses keep, cut, add and change so every round moves the plan closer to that aim instead of starting again.

The Lost Victory vs. The Saved Template

Instead of

Write a message for my customers about Eid orders.

Gemini version

[Attach a photo of last year's festival message, or of your rate card, if you have one.]

Do not use Search for this one. I want the way I actually speak to my customers, not the phrasing every other shop uses.

I stitch ladies' suits in Aminabad, Lucknow, and the women on my list have been coming to me for years. Write the WhatsApp message I will send them about Eid orders. Four things have to get across: orders close on [date], stitching starts at Rs [price], anything urgent costs more, and they should bring along a suit that already fits them well as a sample.

Under 80 words, in everyday Devanagari Hindi, with English underneath. It should read as though I am talking to them across the counter - no advertisement, no "Dear Customer".

Match the voice in what I have attached. Then tell me in one line what you dropped to stay inside 80 words.
Open Gemini 855 characters

Then loop it

  1. Good. Leave the greeting alone. Cut the sentence about quality - they know my work. Add that the shop shuts at 1 pm on Fridays. Make the Hindi more spoken, less written.
  2. That is the one. Write it up as standing instructions for a Gem called "Shop message" - the 80-word limit, the Hindi-then-English rule, the instruction never to search, and blanks for [festival], [last date], [price] and [shop timings] - so Diwali and the wedding season take one minute instead of an evening.

Why it worksThe loop ends with Reuse: the winning message becomes a template, so the next festival begins from the finished version, not from zero.

The Endless Circle vs. The Fresh Start

Instead of

Plan a trip to Varanasi for us.

Gemini version

My wife and I are retired, in our late sixties, and we are going from Coimbatore to Varanasi for five days in [month]. We want somewhere calm to stay near the ghats, two outings a day at most, a rest after every lunch, and nothing that begins before sunrise. Darshan at Kashi Vishwanath, one Ganga aarti and one boat ride are the three things we actually care about. Sarnath we have already decided against, so leave it out completely.

Ground in Search everything that shifts with the year or the season - how we reach Varanasi from here and how long each route really takes, how darshan is being managed at present, when the evening aarti starts, and whether the river permits boats in [month]. Put the link beside each of those, and write [confirm] wherever you could not find a page you trust. Do not close a gap with something that merely sounds right.

Then the five days as a table - Day, Morning, Rest, Evening, Notes - and after it, what we must settle before we book.

Be blunt about the journey. If there is no sensible direct train for two people our age, say so and tell me what we should do instead. Once the plan settles I will export it to Google Docs, so my wife can read it and add her own notes.
Open Gemini 1,214 characters

Then loop it

  1. Four rounds and Sarnath keeps returning. Set the plan aside and list every preference I have given you in this chat, "no Sarnath" and "rest after lunch" among them.
  2. Turn that list into one complete new prompt I can paste into a fresh chat, keeping the Search instructions and the [confirm] rule.
  3. (New chat, prompt pasted.) Give me the five days as a table, then export it to Google Docs so both of us can read it before anything is booked.

Why it worksWhen the answers start circling, it gathers every lesson into a better first prompt and restarts in a clean chat instead of looping forever.

Loop it

After every answer, run the check from step three: read it against the aim you wrote before prompting - length, tone, facts, format. Then reply with precise levers - "Keep…, Cut…, Add…, Change…" - never just "make it better". Stay in the same chat while each round improves. If after three to five rounds the answers circle or old mistakes return, ask, "Summarise all my requirements into one improved prompt," and paste it into a new chat. When the answer finally fits its purpose, save that prompt as a template with blanks for the parts that change.