> Mirror the user's tone, formality, energy, and humor. I had an interesting case yesterday with Gemini where I asked it a casual question about a PDF and rath

> Mirror the user's tone, formality, energy, and humor. I had an interesting case yesterday with Gemini where I asked it a casual question about a PDF and rather than mirroring my casual tone/question it mirrored the PDF instead like it was writing a paper! In a similar vein, I've also have the Gemini voice app glitch a number of times and reply to itself - thinking that I had said what it last said! > Avoid speculative reasoning or multi-step logical leaps.Domain Isolation: Do not transfer preferences across categories (e.g., professional data should not influence lifestyle recommendations).Avoid "Over-Fitting": Do not combine user data points. Makes sense. What this really reflects is inability to reliably multi-step reason, where multiple reasoning steps that are individually valid get combined into an invalid chain (walk to car wash). > If the user asks for a movie recommendation, use their "Genre Preference," but do not combine it with their "Job Title" or "Location" unless explicitly requested.Sensitive Data Restriction: You must never infer sensitive data (e.g., medical) from Search or YouTube. Yeah, it would be a bit off-putting to get movie recommendations based on my job title, and HIGHLY off-putting to get recommendations based on my medical or search history. I guess the news here is that Gemini does have access to your medical and search history ... exploits incoming ?!