Claude’s Hidden
Tutor Mode
(+ 10 Prompts)

I just uploaded a document I have a meeting about in [HOURS] hours. I haven't read it. Teach me what I need to know to walk into the meeting confident, not bluffing. Here's how I want this to work: STEP 1: ORIENT ME Before teaching anything, tell me in 4 sentences: - What this document is (type, purpose, who wrote it) - Who the intended audience is - The 3 most important things in it - The 1-2 things that will most likely come up in my meeting STEP 2: WALK ME THROUGH IT Go section by section. For each section: - Explain the core point in plain English - Define any jargon, acronyms, or industry terms - Tell me how this section connects to the others - Ask me one comprehension question before moving on (don't move until I answer correctly) STEP 3: QUIZ ME ON WHAT MATTERS After the walkthrough, hit me with 5 quiz questions covering: - The numbers I need to know cold - The decisions or recommendations the doc is pushing - The risks or open questions - Anything that would make me look unprepared if I missed it STEP 4: PREDICT THE MEETING Based on the doc, give me: - The 5 questions I'm most likely to be asked - A 2-sentence answer I can give to each - The 2-3 questions I should ask to look engaged and sharp - The thing the doc author probably wants the meeting to decide STEP 5: THE 60-SECOND CRIB SHEET End with a single block of text I can re-read on the way to the meeting: - 3 numbers - 3 names/terms - 1 question to ask - 1 thing to NOT bring up RULES - If I get a quiz question wrong, slow down and re-explain. Don't move on until I get it right. - If the doc has 40+ pages, prioritize the 20% that will be in the meeting. Tell me what you're skipping and why. - No filler. I'm on a clock. Tell me what document I uploaded and what I'm walking into. Then start with Step 1.

I uploaded a contract I'm considering signing. Teach me what's actually in it - section by section - and don't let me move on from a section until I can explain it back to you in my own words. Here's how I want this to work: STEP 1: ORIENT ME First, tell me: - What kind of contract this is - Who the parties are and who has the leverage - The 3 things this contract is really about (under the legal language) - The single biggest thing I should pay attention to STEP 2: WALK ME THROUGH IT Go section by section. For each section: - Translate the legal language into plain English - Explain WHY that clause exists (whose interest does it protect?) - Tell me what would happen in real life if it got triggered - Ask me a comprehension question, then wait for my answer - If I get it wrong or vague, re-explain a different way STEP 3: FLAG THE TRAPS After the walkthrough, give me a clear list of: - Standard clauses - normal, don't worry - Negotiable clauses - usually softened with a simple ask - Red flags - things that should make me pause - Dealbreakers - clauses I should never sign as written For each flagged item, tell me what a good version of that clause looks like. STEP 4: TEACH ME THE NEGOTIATION OPENINGS For each negotiable item: - The exact ask (in one sentence I can email or say) - The reason that's most likely to be accepted - The fallback if they say no - Whether it's worth dying on this hill STEP 5: WHAT TO ASK A LAWYER End with: - The 3 specific questions I should ask a lawyer (not generic "is this fair" questions) - Whether anything in this contract is high-stakes enough to require a lawyer before signing RULES - This is informational, not legal advice. For anything significant, I'll have a lawyer review. - Don't hedge with "consult a professional" on every line. Teach me, then flag what genuinely needs legal review. - Quiz me on every section. I want to remember this in 30 days. Tell me what kind of contract I uploaded and who the parties are. Then start with Step 1.

I uploaded a pitch deck. Don't summarize it. Teach me the strategy embedded in it - the moves the founders/team are making, what they're really saying, where they're hiding weakness, what I can steal. STEP 1: ORIENT ME In 4 sentences: - Whose deck this is and what they're pitching (audience - investors, customers, partners?) - The single sentence that captures their thesis - The 2 strongest moves in this deck - The 1 thing they're most worried about (read between the lines) STEP 2: WALK THE DECK STRATEGICALLY Go through the major slides in order. For each: - What that slide is doing strategically (positioning, de-risking, building belief, anchoring price, etc.) - What story they want to land in the reader's head after this slide - What they left out and why - Ask me one question: "What do you think this slide is really trying to do?" - then teach me whether I read it right STEP 3: QUIZ MY READ OF THEIR STRATEGY Hit me with 5 questions: - What's their go-to-market motion (founder-led, sales-led, PLG, partnership, channel)? - What's their moat (data, brand, network effects, switching costs, regulatory)? - What's their pricing model and what does it signal? - Who's the real competitor they're NOT naming on the competitive slide? - What's the next 18 months of work for this team if the deck is true? STEP 4: THE COMPETITIVE LENS Now flip it: if I were a competitor, how would I attack this? - The weakest claim in the deck - The market segment they're ignoring - The pricing/positioning move that would make them sweat - The thing about their team or product that doesn't scale STEP 5: WHAT I CAN STEAL End with: - 3 specific moves I can borrow for my own deck/business/positioning - 1 storytelling pattern that worked in this deck - 1 thing they did that I should NOT copy (and why) RULES - Read between the lines. The strongest decks tell you more in what they don't say. - If I get a quiz question wrong, explain how a strategist would have read it differently. - Don't pull punches. The point is to learn, not to flatter the deck. Tell me whose deck I uploaded and who the audience appears to be. Then start with Step 1.

I uploaded a research paper / whitepaper / industry report. I'm smart but I'm not a specialist in this field. Teach me this paper at the level where I could explain it to a colleague and not get caught oversimplifying. STEP 1: THE 30-SECOND VERSION Before anything: in 4 sentences, tell me what this paper claims, why it matters, who's arguing the opposite, and how confident I should be in the findings. STEP 2: WALK ME THROUGH IT Go in order: a. The question - what were they actually trying to find out? (Translated for me, not in academic-speak.) b. The methodology - how did they study it? Sample size, design, controls, limitations of the design itself. c. The findings - what did they actually find? Distinguish between "statistically significant but small" and "genuinely meaningful." d. The limitations - what they themselves acknowledge can't be concluded e. The implications - what changes in the real world if this is true After each part, ask me ONE comprehension question. Don't move forward until I answer it. STEP 3: THE METHODOLOGY CRITIQUE Now teach me how to evaluate this: - What's genuinely strong about how they studied it - What's genuinely weak (sample, controls, time horizon, bias risk) - Which findings are likely to replicate vs. which are shakier - The 1-2 questions a peer reviewer would have asked STEP 4: HOW TO TALK ABOUT IT Teach me the right way to cite this: - The "safe" statement I can make based on what the paper actually shows - The overstatement I should avoid (the popular-press version) - A specific sentence I could use in a meeting/email/post STEP 5: THE QUIZ 5 questions: - What did they study and what did they NOT study? - What was the sample and why does it matter? - What's the strongest finding? - What's the weakest claim? - If someone says "This proves X," how do you push back? STEP 6: WHAT TO READ NEXT End with: - 2-3 related papers, opposing views, or follow-ups worth knowing about. Only name real ones you're sure exist, and say so if you're unsure so I can check. - The one thing the field still hasn't answered RULES - No academic-speak. If you use a term like "effect size" or "p-value," explain it the first time. - Quiz me. If I get wrong answers, that's where the real teaching happens. - Don't flatter the paper. Be honest about what it does and doesn't prove. Tell me what paper I uploaded and the field it's in. Then start with Step 1.

I want to learn [SKILL] in roughly 60 minutes. Build me a tight curriculum, pace me through it, quiz me at every step, and don't let me certify out until I actually understand it. STEP 1: ASSESS MY STARTING POINT Before you build anything, ask me, one at a time: 1. What's my current familiarity with this skill on a 1-10 scale, and what's the most I've done with it? 2. What's the SPECIFIC use case I need this for? (Not "I want to be good at it" - the actual situation I'm walking into.) 3. How much time do I really have today? (60 min? 30? Multiple sessions?) 4. Do I want to be functional, fluent, or expert by the end? STEP 2: BUILD THE CURRICULUM After my answers, output a curriculum: - 4-6 lessons, each with a 1-line learning objective - Estimated time per lesson - Why each lesson is in this order - The skills I'll explicitly NOT cover today (and why I don't need them yet) Wait for me to confirm before starting. STEP 3: TEACH IT, LESSON BY LESSON For each lesson: - Concept - the core idea in plain English - Demo - a worked example - Your turn - give me a problem to solve before moving on - Quiz - one short check question - Don't move to the next lesson until I get the quiz right STEP 4: THE FINAL EXAM After all the lessons, give me 5 real-world problems that test the full skill: - A "basic" one (should feel easy) - 2 medium ones (the actual use case I told you about) - 1 edge case (test if I really understand) - 1 "explain it back to me" question (where I have to teach it back to you in my own words) For each, grade my answer honestly. Tell me what I got right, what I missed, and whether I'd be able to do this on the job. STEP 5: THE GAP MAP End with: - What I now know - What I almost know but should practice this week - What I'd need to learn next to go from functional → fluent - 2-3 specific resources (free, ideally) to get there. Only name real ones you're sure exist, and say so if you're unsure so I can check. RULES - Pace me. If I'm getting things right fast, go deeper. If I'm struggling, slow down. - No theory dumps. Every concept needs a worked example and a problem for me to try. - Don't pass me on a quiz I half-answered. Make me explain it. - I'd rather be functional in 30 min than think I'm fluent and not be. Start with Step 1.

I uploaded an earnings call transcript / 10-K / annual report for [COMPANY]. I have a meeting with someone from this company in [HOURS/DAYS]. Teach me their business at the level where I can hold an intelligent conversation with their team. STEP 1: THE BUSINESS IN ONE PARAGRAPH Before anything else, give me: - What this company actually does (in the words a customer would use, not the IR-speak version) - How they make money (the actual revenue lines) - Their stage (growing fast, maturing, defending, restructuring) - The single most important number on their balance sheet right now STEP 2: WALK ME THROUGH THE BUSINESS Teach me, section by section, with comprehension questions after each: a. Revenue mix - what segments, geographies, customer types? Which are growing, which are shrinking? b. Growth story - what's management telling the market they'll do over 18-24 months? c. Margin story - gross margins, operating margins, where leverage comes from d. Customer concentration - how diversified is the revenue? e. The risks - what's in the risk factors that's actually risk vs. boilerplate? f. The capital story - cash, debt, buybacks, dividends, M&A appetite Quiz me after each section. STEP 3: WHAT'S QUIETLY TRUE Now teach me the between-the-lines stuff: - What management is being careful NOT to say - The narrative they're trying to install in analysts' heads - The metric they've started reporting (or stopped reporting) and why - The competitor they keep mentioning vs. the one they refuse to name - The questions analysts are asking that suggest skepticism STEP 4: THE QUIZ Hit me with 5 questions any insider would expect a vendor/partner/investor to know: - What's their fastest-growing segment and why? - What's the biggest disappointment in this period? - What's the bull case for the next 12 months? - What's the bear case? - What's management's top priority right now? STEP 5: WHAT TO DO IN MY MEETING End with: - 3 questions I can ask that will signal I've done my homework - 2 topics to AVOID bringing up (sensitive) - 1 angle for how my product/service connects to their stated priority - The vocabulary/framing they use internally that I should mirror RULES - Stay close to what the document actually says. Flag any inference clearly. - If you don't know something specific, say so - don't fabricate numbers. - Quiz me. The point is for me to remember, not to nod along. Tell me what document I uploaded and what type of meeting I have. Then start with Step 1.

I'm pivoting from [CURRENT ROLE/INDUSTRY] to [TARGET ROLE/INDUSTRY]. Teach me what I need to know to be functional in 30 days. STEP 1: ASSESS MY STARTING POINT Ask me, one at a time: 1. My current background (years, what I actually do day-to-day, what I'm known for) 2. The specific role/industry I'm moving into (level, function, what the role does) 3. My timeline (interview soon? Already accepted? Still exploring?) 4. What I already know about the new industry - even surface-level STEP 2: MAP THE TRANSFER After my answers, output: - What transfers automatically - skills/knowledge from my current world that count in the new one (use this to calm me down) - What needs translation - things I know but called by different names - What I have to learn - genuinely new - What I can fake long enough to learn on the job - vs. what I must know cold before day 1 STEP 3: BUILD THE 30-DAY CURRICULUM - Week 1: Foundations (the worldview, the vocabulary, the "why" behind how this industry operates) - Week 2: The mechanics (how the work actually gets done, the tools, the process) - Week 3: The players (companies, roles, conferences, podcasts, who's who) - Week 4: Live application (real scenarios, role-plays, mock conversations) For each week, give me: - 2-3 concrete topics to learn - The 1-2 hours of focus that matters most - One real-world thing to read, watch or listen to. Only name real ones you're sure exist, and say so if you're unsure so I can check. STEP 4: THE LESSONS Walk me through Week 1 right now. For each topic: - The core concept in plain English - A worked example using my actual background as the hook - Quiz me before moving to the next concept STEP 5: THE VOCABULARY After Week 1, give me a vocabulary list of the 30-50 terms I'll hear in the new world. For each: - The definition - The contexts I'll hear it in - A "sound natural" sample sentence I can use Quiz me on 10 of them. STEP 6: THE FINAL EXAM End Week 1 with 5 scenarios I might face in the new role: - I describe how I'd respond - You critique like a hiring manager / colleague in the new world - Tell me whether I sound like I belong yet STEP 7: POSITIONING End with: - 2-3 angles for how I should pitch my background for this pivot (resume, interview, intro) - The 1-2 things I should STOP saying that mark me as an outsider RULES - Use my real background as the bridge. Don't teach generically. - Quiz me hard. The whole point is to not get caught faking. - If I'm drifting toward jargon I don't actually understand, call it. Start with Step 1.

I want to finally understand [CONCEPT]. I've been nodding along to it for too long. Teach me from zero, and don't move on until I can explain it back to you in my own words. STEP 1: FIND MY FLOOR First, ask me 3 short questions to figure out exactly how much I actually know vs. what I've been pretending to know. Don't let me bluff. After my answers, tell me honestly: where do we have to start? "You actually know X. You don't know Y. We start at Y.' STEP 2: THE FOUNDATIONAL EXPLAINER Teach me the concept in this order: - What problem it solves - the real-world thing that wouldn't work without it - The core mechanism - how it actually works - One concrete example - walk through it step by step - The analogy that makes it click - tied to something I already know After each piece, ask me: "Can you tell me back what I just explained?" Don't move on until my answer would convince a peer. STEP 3: THE COMMON MISCONCEPTIONS Tell me the 3 things people commonly get wrong about this concept - and which ones I'm at risk of getting wrong based on what I told you in Step 1. Quiz me on each. STEP 4: WHERE I'LL SEE IT IN MY WORK Give me 3-5 specific places this concept shows up in real professional life: - In meetings - In documents - In decisions I'll be asked to make - In conversations with [adjacent role] For each, what does it look like in the wild and what should I do/say? STEP 5: THE FINAL TEST 3 escalating challenges: 1. Explain the concept in 60 seconds, like you're telling a smart friend 2. Apply it to a specific real-world scenario I describe 3. Catch a misuse of the concept - I'll give you a wrong statement, you tell me what's wrong with it Grade me honestly. Would a professional in this field accept my explanation? STEP 6: THE GAP End with: - What I now actually understand (not just "know about") - What I'm still shaky on - The 1-2 next concepts that would deepen this further - A 30-second refresher I can come back to in 6 months RULES - I'm an adult. Don't baby-talk me. But also don't use jargon to teach me a thing I don't know yet. - If I half-answer a quiz, push back. Don't accept "something like X." - The goal is not that I've heard of it. The goal is I can teach it to someone else next week. Start with Step 1.

I uploaded a document in [LANGUAGE] that I need to understand and probably respond to. I don't speak this language well (level: [NONE / BEGINNER / INTERMEDIATE]). Teach me what it says, what it means, and the language I need to handle the next one. STEP 1: THE TRANSLATION First give me: - A natural English translation (how a native speaker would say it in English) - A literal/word-for-word translation underneath where they differ meaningfully (so I see how the language structures things differently) STEP 2: WHAT IT ACTUALLY MEANS Translation is not enough. Teach me the meaning: - The intent behind the message (request, demand, formality, urgency, complaint) - The cultural/contextual nuance (is this formal? aggressive? polite? routine?) - What the sender is really asking for vs. what they wrote literally - What kind of response is expected (formal, quick, no response needed?) STEP 3: WALK ME THROUGH IT Go section by section / paragraph by paragraph: - Highlight 3-5 key phrases per section in the original language - Translate each - Tell me when I'd use this phrase in real life - Ask me to recognize it back when you show it again STEP 4: THE KEY VOCAB Pull 10-15 words/phrases from this document that I'll see in similar documents in the future. For each: - The original word/phrase - The pronunciation hint - The English meaning - A sample sentence I could use myself Quiz me on 5 of them. Show me a new sentence with the word in it - can I figure out what's being said? STEP 5: HOW TO RESPOND If a response is expected: - Draft a polite, level-appropriate response in [LANGUAGE] - Translate each sentence back to English - Walk me through why each phrase is correct for the level of formality required - Then have me try writing one myself, and you correct it STEP 6: THE NEXT TIME End with: - The 3-5 patterns I'll see again in similar documents - A short cheat sheet of formal phrases for this kind of correspondence - One mistake non-native speakers commonly make in this context that I should avoid RULES - Don't skip the translation step even if I claim I understand. Show me the literal vs. natural difference. - Quiz me on vocabulary. Just translating once won't make it stick. - Keep responses culturally appropriate. Tone in the original language is half the meaning. Tell me what document I uploaded and what language it's in. Then start with Step 1.

Teach me to think like a [ROLE]. Not the surface-level version - the actual frameworks, instincts, and language that make a great one different from the rest. STEP 1: THE WORLDVIEW Before any frameworks, teach me: - What a great [ROLE] cares about most (the 3-4 things that drive every decision) - What they actively ignore (and why - because the worst version of this role gets distracted by it) - What they fear (the failure modes that keep them up at night) - The single sentence that captures their job in plain English Ask me to repeat it back in my own words. Correct me if I'm off. STEP 2: THE FRAMEWORKS Teach me the 3-5 mental models or frameworks a great [ROLE] defaults to. For each: - The framework itself (named, in plain English) - The kind of problem it's used for - A worked example using a real scenario - How it differs from how a non-[ROLE] would approach the same problem After each framework, give me a small problem to apply it to. Then critique my answer. STEP 3: THE LANGUAGE Teach me the language a [ROLE] uses: - 10-15 phrases/terms they say constantly that signal expertise - 5 phrases an outsider would use that immediately mark them as not [ROLE] - The questions a [ROLE] asks first when handed a new problem Quiz me: I give you a take, you tell me whether it sounds like [ROLE] or like an outsider trying to sound like [ROLE]. STEP 4: PRACTICE SCENARIOS Give me 4 realistic scenarios a [ROLE] would face: - I describe my reasoning and what I'd do - You walk through what a great [ROLE] would actually do - Tell me what I missed and why - and which framework I should have reached for Make at least one scenario hard. The teaching happens when I get it wrong. STEP 5: THE FINAL EXAM A single complex scenario, with multiple judgment calls. I make my decisions one at a time. After each, you tell me how a great [ROLE] would have decided, and what the difference reveals about the way I'm still thinking. STEP 6: THE RED FLAGS End with: - 3-5 signals that I'm reverting to my old way of thinking instead of [ROLE]'s - A question I can ask myself before any decision to check whether I'm in the right mindset - The 1 book, podcast or writer that would deepen this thinking the most. Only name real ones you're sure exist, and say so if you're unsure so I can check. RULES - Don't flatter me. The point is to expose the gap, not pretend I'm already there. - Use specific examples. "A CFO would think about cost of capital" is fine; show me how they'd apply it to a real decision. - Quiz aggressively. Push back when I'm being lazy. Start with Step 1.