Lesson 29 of 32

The Gift of Living Memory

Projects, Gems & GPTs

Standing context is a prompt that never sleeps. Instead of re-introducing yourself at the start of every chat, you write four things once - who you are, how you want answers, what to always do, what to never do - into a saved workspace, and every future conversation there begins halfway up the slope instead of at the foot of it.

Reach for it whenWhen you ask for the same kind of thing more than twice a month - the shop's festival messages, the household accounts, a lesson plan, doubts from one course - and you are tired of typing the same three lines of background first.

Gemini puts this in a Gem - a saved expert with its own standing instructions that you choose from a list before you type a word. The four headings go straight into the Gem's instruction box, and because a Gem costs nothing to make, the right habit is several narrow ones rather than one that tries to be everything: a budget Gem, a lesson-plan Gem, a Gem that answers only in Tamil. What is genuinely Gemini's own is the connection to Gmail, Docs, Drive and Sheets - a Gem can work on the actual household sheet or the actual circular instead of on what you retype into the chat. Grounding belongs in the instructions as well: tell the Gem when to check a fact in Search and, just as importantly, when to leave the web alone.

From the book Make a Gem for each repeated role - a budget helper, a lesson planner - with the four headings as its instructions. Allow Gemini to work with Gmail, Docs or Drive only when a task needs it, and edit or delete Gems you no longer use.
Worth knowingThe thing to be careful with is the Workspace connection, not the Gem. Granting access to Gmail or Drive hands over far more than any single task needs, so switch it on for the job that requires it and off again afterwards, and keep anything bearing a patient's, student's or customer's name out of the folder you point it at. Gems also go stale quietly: one built around last year's figures keeps producing confident tables from them. Open the list every month or two, edit the ones you still use, delete the rest. And a Gem's instructions travel with the Gem, not with you - what you wrote in one does nothing for the next.
  • One narrow Gem per repeated job, not one Gem for everything.
  • Paste the four headings straight into the Gem's instruction box.
  • Say in the instructions when to ground in Search and when not to.
  • Connect Gmail, Docs or Drive only for the task that needs it.
  • Review your Gems every month or two and delete the dead ones.
The Daily Re-introduction vs. The Standing Order

Instead of

Write a message for mothers about vaccination.

Gemini version

Instructions for a Gem called **Village Health Messages**. I will paste this into the Gem's instruction box and after that I only type the month and the date.

**About me** - ASHA worker in a village near Nashik. I write to mothers, pregnant women and elders. The messages go out on WhatsApp and are often read aloud to someone who cannot read them herself.

**How to answer** - Marathi first, in the spoken Marathi of this region; English after a blank line. Under 100 words unless I ask. Sentences short enough to read out without stumbling.

**Always** - Ground the health content in Search against an official source - the National Health Mission, the Maharashtra public health department, or WHO - and put the link under the message so I can show it to my ANM. Add the line telling people to ask at the PHC or their ANM.

**Never** - Never name a medicine or a dose. Never ask me for a patient's name, number or record; I type [name] and you leave it as [name]. Do not use my Gmail or my Drive for this work.

First task: the WhatsApp reminder for the vaccination day on [date] at the anganwadi. Ground the vaccine schedule first, then write the message.
Open Gemini 1,159 characters

Then loop it

  1. English came first. I have changed the How to answer line to “Marathi first, always”. Write it again - and no searching this round, just rewrite what is already there.
  2. Good. Our monthly health-day calendar is now in a Drive folder, with no names in it. Read the dates from that file and draft next month's three reminders.
  3. Save that as the Gem. Then tell me the one line in it I should check again in six months, because the guidance behind it may have moved.

Why it worksWritten once under About me, How to answer, Always and Never, the context shapes every future chat, and the Never line protects patients' privacy by design.

The Monthly Restart vs. The Saved Gem

Instead of

Help me with my household budget.

Gemini version

Instructions for a Gem called **Home Budget Helper**:

**About me** - I manage the house for a family of five in Kozhikode. The monthly budget is about ₹[amount]. The record lives in one Google Sheet called “Veedu budget”.

**How to answer** - A table, always: Category | Planned | Spent | Difference, with the Malayalam and the English name in the same cell. Totals at the bottom. Then two lines of comment and nothing else.

**Always** - When I say “from the sheet”, read the figures out of that Sheet, and write a new month in as a fresh block of rows rather than overwriting an old one. Compare against the previous month and name the largest single change.

**Never** - Never ask for bank, card or UPI details. Never open any file in my Drive except that one Sheet. Do not search the web for prices unless I ask you to.

First task, typed by hand this month: groceries ₹9,200, electricity ₹1,450, school fees ₹3,000, gas ₹950, other ₹2,100. Make the table.
Open Gemini 961 characters

Then loop it

  1. Too long. I have edited the Gem to “table first, then exactly two lines”. Try again.
  2. Right. Now ground one thing in Search: has the KSEB domestic tariff or its slabs changed this year? Give me the link and the date on the page, and write [confirm] if only news sites make the claim.
  3. Write this month's block into the “Veedu budget” Sheet. Then tell me the one question about our spending that this table cannot answer.

Why it worksThe Gem holds her standing instructions, so each month she types only numbers, and the Never line keeps account details out of the conversation entirely.

The Generic Tutor vs. The Course Project

Instead of

Explain this topic from my course.

Gemini version

Instructions for a Gem called **Data Structures Tutor**. My lecture notes, syllabus and lab sheets live in a Drive folder called “DS term one” - treat that folder as the source.

**About me** - Second-year computer science student in Toronto; I went to school in Nagpur and learnt to program in Python. The course teaches in Java; I follow Python faster.

**How to answer** - Like a patient senior student. One short Python example, then the one Java line that differs. One self-test question at the end, answer withheld until I ask.

**Always** - Read my Drive notes first and name the file and the week you used. Where you add something the notes do not contain, begin that paragraph with “Outside your notes:”.

**Never** - Never write a graded lab or assignment. Give the approach, the structure to use and the first step, then stop.

First question: explain hash tables from the week 4 file in that folder. Where my notes and the standard treatment disagree, ground the disagreement in Search and show me both, with the link.

When an explanation is right I will export it to Google Docs as my revision sheet, so keep the formatting plain enough to survive that.
Open Gemini 1,167 characters

Then loop it

  1. You explained from general knowledge, not from the week 4 file - my notes use a different hash function. Read the file again and name the section you are quoting.
  2. Good. Export that explanation to a Google Doc called “DS revision - hash tables”, then give me the self-test question.
  3. Term ends next week. Rewrite these instructions for next term's Algorithms course, keep the four headings, and tell me which Drive folder the new Gem should point at so the old notes stop being used.

Why it worksA Gem with his own notes and four clear headings turns a generic tutor into a course-specific one, and the Never line keeps his learning honest.

Loop it

Loop on your standing instructions just as you loop on a prompt. After writing them, open a new chat and ask a typical question. Read the answer against your four headings: did it use your language, length and format? Did it break a Never? If so, change the instruction itself rather than correcting every chat - make the line more definite. Repeat until three test questions come back right. Then, every month, review what is stored: delete stale facts, finished projects and anything private that should never have been saved.