The #1 move - the one Tucker uses on everything
1. Make Claude interview you before it answers
The single highest-leverage prompting habit. Before you let Claude write the memo, the email, the market map - tell it to ask you questions first. You'll get an output 3x better in half the back-and-forth, because the model now knows what "good" actually means to you.
Why it works: most weak Claude outputs aren't a model problem - they're a context problem. The model is guessing at your audience, your tone, your constraints, what "done" looks like. Forcing it to ask flips the dynamic: you become the source of truth and the model becomes the interviewer.
Drop this at the end of any non-trivial prompt
Before you respond, ask me 3-5 clarifying questions so you can produce a much better output. Wait for my answers before writing anything.
Tucker's #1 habitWorks in any Claude chatUse this in the demo
Power-up #2
Front-load a 3-line "about me" block
Open every fresh chat with 3-5 lines about who you are, who the output is for, and what "good" looks like - before the actual ask.
I'm Director of Plug and Play Indiana. Output is for a corporate partner meeting (Zimmer Biomet exec, allergic to fluff). Be direct, use numbers, skip caveats. Here's the task:
Lifts the FIRST output instead of forcing 4 rounds of "make it more X." per the-ai-corner.com
Power-up #3
Claude is not ChatGPT - one long prompt, not five short ones
ChatGPT trained everyone to iterate fast in short turns. That habit actively hurts Claude outputs. With Claude: front-load everything in one long prompt (context, examples, constraints, anti-examples) and let it cook.
Context: [3 paragraphs]
Examples of good output: [2]
Examples of what I DON'T want: [1]
Constraints: [bullets]
Task: [one clear ask]
Counter-intuitive but real. per Deb Szabo + r/ClaudeAI
Power-up #4
Show, don't tell - paste a good example + a bad example
Models pattern-match much better than they follow style adjectives. "Professional but not corporate" is fuzzy; two examples is concrete.
Here's an investor update I think is great: [paste].
Here's one I think is terrible: [paste].
Write mine in the style of the first, never the second.
Topic: Q1 portfolio performance.
Two examples beats two paragraphs of description. per Nicolas Cole on YouTube
Power-up #5
Make it grade its own draft before showing you
Forces a second reasoning pass. Catches the lazy first-draft answer that everyone else accepts and ships.
Before you show me the answer, grade your draft 1-10 on: (a) specificity, (b) whether a skeptical CFO would buy it, (c) whether it avoids generic AI hedging. If any score is below 8, rewrite. Only show me the final version.
Self-criticism beats user-criticism. per skillvolume.com
Power-up #6
"What would you need to know to do this 10x better?"
The inverted version of Power-up #1, and easier to remember. Append this line and Claude surfaces the gaps you didn't think to mention.
What would you need to know to do this 10x better? List 3-5 questions, then wait for my answers before writing anything.
Faster than "ask me questions first" because the model frames it around output quality, not interview vibe. per Zapier
Power-up #7
Save your wins - build a personal prompt library
When a prompt produces a great output, paste it into a running doc with a one-word name. Reuse next time instead of re-inventing. Power users don't write better prompts in the moment - they have a library of prompts that already worked.
[DEAL-MEMO] [LP-UPDATE] [PARTNER-PREP]
[COHORT-STANDUP] [FOUNDER-INTRO]
Compounds over weeks. per skillvolume.com + theMITmonk
Meta-pattern from the research
The shift: from clever prompts to lightweight personal systems
Across every power-user voice from the last 30 days - Skill Volume, The AI Corner, theMITmonk (1.6M views), Deb Szabo, Nicolas Cole, Zapier - the same meta-insight repeats: the difference between people getting amazing Claude outputs and people getting mediocre ones isn't prompt-craft. It's habit-craft. The winners aren't typing better in the moment - they have saved blocks, "about me" snippets, reusable prompt names, and a self-critique step baked into how they work. That's what compounds.
For the session: this slide is the soft pitch. Tucker can offer to help Brandon build his personal prompt library + identity block + critique loop as a 1-hour follow-up. It's the natural next step after the 90-minute demo.