Prompt Claude better than 99% of people

10 Dec 2025 · 17 min · 11 chapters

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

How to prompt Anthropic’s Claude Code and Claude Opus 4.5 to get better results, using 10 specific prompting techniques with real examples.

Guests

No guests mentioned; the host presents the episode solo.

Key claims

Anthropic has shared these prompting ideas in docs/blog/X over 12 months, but lacked a full guide; following the 10 rules yields “10x more” useful output and avoids generic “AI slop.”

Notable examples

Replacing vague requests (e.g., “fix this grammar”) with architected briefs; generating 10 blog titles for city officials/real estate developers; writing a 500-word Raymond Chandler-style story with constraints (robot detective on Mars, no word “cyber”); “draft, plan, then act” for a four-day workweek report; structured tables for Apollo missions; “think step by step,” “critique your own response,” and “divide and conquer” workflows (blueprint then section-by-section then synthesis).

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Chapters

Tap a time to open that second in VO

Tip 1: Tone of Collaboration

0:47 to 2:16

Using a friendly and clear tone improves AI response quality.

“So the first tip is, I know this is going to upset a few people, but the tone of collaboration is really important.”

Tip 2: Principle of Explicitness

2:16 to 4:19

Clear action-oriented commands yield better AI results.

“Rule two of 10 is the principle of explicit explicitness.”

Tip 3: Draft, Plan, Then Act

4:19 to 5:41

Use AI for outlines before finalizing to improve output quality.

“I know that, you know, it's kind of measure twice and cut once, but you will get more if you define the boundaries.”

Tip 4: Demand Structured Output

6:40 to 8:01

Request structured formats to enhance data presentation.

“Rule number five is demand structured output.”

Tip 5: Explaining the Why

8:01 to 11:12

Providing context helps AI generate more relevant output.

“So the golden rule here is explaining the why behind an instruction helps the AI understand your true intent.”

Tip 6: Control Output Length

11:12 to 12:39

Specify verbosity to tailor responses to your needs.

“And just by saying this, the structure and style, it helps.”

Tip 7: Providing a Scaffold

12:39 to 13:46

Use templates to guide AI's structure and style in responses.

“Create a detailed table of contents for a business plan for a new specialty coffee shop.”

Tip 8: Speak the Language

13:46 to 14:00

Using specific terminology can enhance AI performance.

“What might even be helpful here is like literally taking out a pen and paper and being like, okay, if I want a business plan, what are the 10 things I need?”

Effective Prompting Techniques for Claude

14:00 to 14:34

Learn how to prompt Claude effectively to enhance AI responses.

“This is going to be helpful for you to get the most out of it.”

Crafting a Better Prompt Example

14:34 to 16:15

Discover how to structure a prompt for better AI output using specific examples.

“Because you've included the persona in there.”
Show all 11 chapters

Maximizing AI Utility in Your Projects

16:15 to 16:43

Understand the importance of precise prompting to create valuable content.

“and why it matters is because we're all trying to get the most out of it.”
Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00How can you get more out of Claude Code and Claude Opus 4.5? Well, I've got good news from you. Anthropic has actually, over the last 12 months, have been posting in their docs, blog posts, kind of teasing on X about how you can prompt these products to really get the most out of it. But the thing is, people haven't put it in a full guide. So I did the hard work to make it easy on everyone. By the end of this episode, you will learn 10 techniques or how to prompt Claude to get the most out of it. Super simple techniques anyone can learn. I'm going to show you real examples, easy to understand, and frameworks to help you crush it with Claude code in Opus 4.5.

0:46Let's get right into it.

0:55So the first tip is, I know this is going to upset a few people, but the tone of collaboration is really important. You're going to want a friendly and clear and firm tone because that yields better results and more direct results. So what's an example? A vague request might be something like, fix this grammar in this now, you know, but the problem with that is, you know, it leads to overly cautious, pre-canned, or basically just less helpful responses as the model tries to de-escalate. politeness can sometimes result in chatty less direct answers now if you do you know an architected brief and this is what the folks at anthropic suggest you do do something like please review the following text for grammatical errors and suggest corrections my goal is to make it sound more professional and confident this is direct this is respectful and it provides context which is what Anthropic needs in order to get you the result, you know, that you want.

1:58So really important. I know some of us are just kind of mean to our LLMs. I've been there, you know, but treat it like a teammate, right? You would never want to be mean to a teammate, especially if you want to get them to produce. So rule one of 10 is the tone of collaboration. Rule two of 10 is the principle of explicit explicitness. So state your request as a clear action oriented command with all the necessary details. So I used to do this, actually, I would I would do like a vague request, like I need a bunch of blog post ideas. But the problem is it's passive. It's not specific. And then you just get this generic AI slot.

2:43architected brief what's the difference okay generate 10 blog post titles about the impact of remote work on urban planning the title should be engaging for an audience of city officials and real estate developers this prompt uses an action verb generate you're gonna you're gonna want to you know use action verbs a lot it specifies the quantity 10 and target audience those are the three things that you're going to need. An action verb, the quantity, and a target audience. Every highlighted phrase adds a layer of useful constraint. This works extremely well. Three on 10. The rule here is a well-defined box produces a more creative result than an empty field.

3:30So a vague request would be something like write a short story about a detective in the future. Problem is the possibilities are infinite and that leads to cliche AI slop on focus output. Architected brief. What's the difference? Write a short story. No more than 500 words in the style of Raymond Chandler. You can even do like in the style of Ernest Hemingway meets Raymond Chandler. Or you can even put three or four or five different people. The story must feature a robot detective investigating a data theft on Mars. Do not use the word cyber. So you've added constraints on length, constraints on style, constraints on character, constraints on settings, and even specific words to force the AI into more creative and specific solution.

4:17I know this takes more time. I know that, you know, it's kind of measure twice and cut once, but you will get more if you define the boundaries. Number four, the rule is draft, plan, then act. Use the AI to generate an outline or roughed version first. So don't try to get a perfect final product in one go. I know we all want to one prompt it and just it feels so good to one prompt it. I've been there. But, you know, the reality is working with the AI to create and then refine a plan or outline is a way more reliable path to a high quality result. And that's what we're out for. This lets you course correct early.

4:59So think of it like this. The initial prompt might be, I need to write a report on the benefits of a four-day workweek. Ask for a plan, step one. First, propose an outline for this report. Then refine the plan, step two. That's a good start. In section two, please add a sub-point about employee retention. Step three, you can do, you know, step three is the execution layer. Excellent. Now, write the full report based on this revised outline. So, you know, it takes longer, but it takes longer. It feels like it takes longer, but it's actually going to save you time because you're going to get a better outcome and you're not going to have to reprompt and reprompt and reprompt.

5:40If you have a business that's doing at least$50 ,000 a month in revenue, I've got something interesting for you. It's called offline mode. It's a two day event that me and my team are putting on at a 20 ,000 plus foot square foot mansion. Yes, this is what it looks like on January 23rd and January 24th in Fort Lauderdale, Florida. I'll include a link in the description if you're interested in coming. But it's basically for people who have a business that's kind of cranking, but they really want to put it in rocket ship mode. They want to create a set of businesses that generate tons of money, tons of cash flow, tons of product market fit, tons of impact.

6:19But they're not just quite there yet. It's also about making your business AI first, how you can actually build not just one product, but multiple products. And you're going to leave with tactical answers to your questions. So if that's you and this sounds interesting, I'll see you there. Rule number five is demand structured output. The AI is fluent in many formats beyond pros. So, you know, a vague request might be something like list the last three Apollo missions and some facts about them. So you're going to it's it's it's basically going to give you a simple unstructured paragraph and that's going to be hard to parse.

7:01Now, an architected brief might be something like provide the list of the last three Apollo missions, 15, 16 and 17 for each mission, include the launch date, the crew members and a key specific achievement. Present this information in a markdown formatted table. So what you might have to do is go to something like perplexity and do a prompt there to understand a little more about what you want an architected brief to look like. But you're going to end up getting a way better output here. You can just see this markdown file if you're on YouTube. Also, like and comment if you're liking this sort of stuff.

7:39I'll do more of it. So look at this markdown. it's just way better than what you'd get if you did something else and just went like a simple vague sort of thing. So it might take you more time a little bit initially but again, you're going to have better output. Six, explaining the why. So the golden rule here is explaining the why behind an instruction helps the AI understand your true intent. So instead of saying, give me five marketing slogans for a brand new coffee where the AI basically has no context, doesn't know the brand values, it doesn't know your audience, your community, who you're going after, it doesn't know your unique selling proposition.

8:24Do something like this. Give me five marketing slogans for a new brand of coffee. The key is that our beans are ethically sourced from small independent farms and our target audience, really important you put this in here, is environmentally conscious millennials. By the way, it's not just that you put our target audience as millennials. You have to define it even more. Go niche and then go even nichere. You'll get better results. The slogan should reflect quality and sustainability. So by providing the why, basically ethically sourced for conscious millennials, the AI can generate far more relevant and target slogans than you get at getting better results.

9:05Seven on ten, the art of brevity and verbosity. So the rule here is explicitly command the AI to be more or less verbose to match your needs. So you're in control of the output length. Use simple direct phrases to guide the AI. So let's just show some different examples. So maybe you want the expert here. Explain photosynthesis in detail for a college biology student. Think step by step to ensure accuracy. Boom. Look at how expert this looks like. I mean, it's throwing me back to my biology and chemistry days, just seeing stuff like this when I was in school. Maybe you want something that's brief.

9:54Explain photosynthesis. Be concise and use bullet points. Sometimes here I'll say, like, explain like I'm five. Explain like I'm 13. Explain like I'm 17. and then you can see the bullet points and then here oh here the simplifier explain photosynthesis like like i'm five years old so these are three options the expert the brief the simplifier the point here is that you are in control of your output length and it is important that you include that in the prompt eight on ten providing a scaffold the rule here is you want to give the AI, you want to give Claude a template or example to guide its structure and style.

10:32So let's, the vague request would be something like, summarize this article. But, you know, this is way better. Look at this in the architected brief section. Summarize the following article using this format. Main thesis, one sentence, AI fills this in. Key supporting points, three bullet points, the AI fills this in, and concluding insight, AI fills this in, and then paste the text here. So now you have this rigid structure ensuring the summary is not only accurate, but is also formatted exactly as needed.

11:10Really, we want the best results. We want the best final results. And just by saying this, the structure and style, it helps. A little bit of scaffolding goes a long way. Nine on ten, speaking the language. So using advanced prompting terms can trigger more sophisticated modes of operation. So models are trained on a vast amount of text about AI itself. So using terms from the field activates specific powerful behaviors. This is like cheat codes. So let's talk about a few power phrases that Anthropic has literally told us to use that most of us are not even using. Think step by step. So what's the use case?

11:54Force the model to lay out the reasoning process, often leading to more accurate results on complex problems. So you're going to want to remember that one. Critique your own response. Use case. Ask the model to perform self-correction. Find flaws in its initial draft and improve it. Adopt the persona of an expert in field. Use case primes the model to response with a deeper, more domain-specific vocabulary and framework. These are magic words. You might want to screenshot this. This will help you get the most out of it. And finally, we have the divide number 10, the divide and conquer strategy.

12:34So the rule here is for a complex task, act as the conductor. prompt for each part separately then prompt for the synthesis so don't ask for a 10-page report in a single prompt break it down into logical subtasks that you manage step by step so if you listen to this startup ideas podcast you know i love ideas you know i have a business idea browser.com that gives away ideas um and uh you know so you know i like building businesses And you can see that it's easy to throw in, hey, build a business plan as the one prompt, but this is a way better to do it. Step one, the blueprint. Create a detailed table of contents for a business plan for a new specialty coffee shop.

13:21Step two, section by section. Write the executive summary based on our plan. Now write the market analysis section. And then the A dotted line indicates more steps. And step three, the synthesis, review the complete business plan, ensure consistent tone, and check for any contradictions. So this is the project workflow, you know, doing it section by section, synthesizing, having the blueprint. You know, you're dividing and conquering. You're breaking into logical subtasks. What might even be helpful here is like literally taking out a pen and paper and being like, okay, if I want a business plan, what are the 10 things I need?

13:56If I want to create a deck, a fundraising deck, what are the 10 things I need? If I want to create a software product, what are the 10 different features I need? This is going to be helpful for you to get the most out of it. So there you have it. I've given you the 10 rules of how you can prompt Claude to get literally 10x more of it. This is the simple tools and techniques that you can use that have literally been shared by the people from Anthropic themselves. We talked about the tone of collaboration. definition we talked about uh which is using friendly clear and firm tone we talked about the principle of explicitness we talked about the defining the boundaries we talked about the exploratory draft we talked about specifying the details we talked about explaining the why we talked about how important brevity is why you can put a should put a little scrap scaffolding how how important it is to speak the language and we talked about the divide and conquer strategy so what does that look like when you put it all together this is you know when you came into this episode you might have prompted or maybe not but you might have prompted claude saying something like tell me about stoicism by the way i call it claude but for you i'll call it claude because people get angry and mad at the in the comment section about that let's talk about now now that you know the tools of how to prompt claude better let's let's let's see it at work instead of saying tell me about stoicism, you're going to say, act as a university professor of philosophy.

15:27Why? Because you've included the persona in there. You're going to say, I'm preparing a one-hour intro lecture for students with no prior knowledge. That's going to explain the why. You're going to say, first create a lecture outline with three main sections, the divide and conquer. The outline should have a clear introduction and body. You've now constrained the scope. And conclusion, please format this as a nested, bolted list, rich output. For each major point, include a key stoic figure, example, Seneca, explicitness, and one of their core ideas. Your tone should be accessible and engaging.

16:08Tone. So you've included that all in there. And then the output is just way better. So these are little things to help you get the most out of these LLMs. and why it matters is because we're all trying to get the most out of it. We're all trying to create products that people love. We're all trying to create content that people love. We're all trying to do things that people love. And a lot of the times we get AI slot. And this is going to help you not get AI slot. And that's why I put the time to scour the internet for you so you can get the most out of this product. So, so powerful. I have no affiliation with Anthropic.

16:50But I want to see you not just like, comments, and subscribe on this, but actually go and build something great with this stuff. So I'm rooting for you. Have a creative day, and I'll see you next time.

From the publisher

In this solo episode, I walk through 10 concrete rules to get way more out of Claude Code and Claude Opus 4.5, based directly on tips Anthropic has shared in their docs and blog posts. I show how to move from vague prompts to architected briefs that use tone, constraints, structure, and power phrases to avoid “AI slop.” I demo examples across writing, research, teaching, and planning so you can see exactly how to apply each rule. By the end, you have a practical playbook for prompting Claude like a teammate and using it as a true thinking partner in your work.

Timestamps

00:00 – Intro

00:56 – Rule #1: Tone of collaboration

02:16 – Rule #2: Principle of explicitness (action verbs, quantity, audience)

03:20 – Rule #3: Define the boundaries with clear constraints

04:26 – Rule #4: Draft, plan, then act (outline → refine → execute)

06:39 – Rule #5: Demand structured output (tables, formats, schemas)

08:00 – Rule #6: Explain the “why” behind your request

09:05 – Rule #7: Control brevity vs. verbosity (expert, brief, simplifier)

10:21 – Rule #8: Provide a scaffold and templates

11:21 – Rule #9: Use “power phrases” and expert personas

12:28 – Rule #10: Divide and conquer complex projects

14:09 – Putting it all together with an example

For founders doing $50k+ MRR+: https://startup-ideas-pod.link/offline-mode

Key Points

I share 10 specific prompting rules that come directly from how Anthropic suggests people use Claude.

I show how friendly, clear, and firm prompts beat either vague or overly polite requests.

I demonstrate how explicit constraints (length, style, audience, banned words) create more creative and focused outputs.

I use outlines, scaffolds, and structured formats to turn Claude into a planning and synthesis engine instead of a random text generator.

I introduce “power phrases” like “think step by step” and “critique your own response” to unlock more advanced reasoning.

I wrap everything into a final Stoicism lecture prompt that combines persona, context, constraints, structure, and tone.

The #1 tool to find startup ideas/trends - https://www.ideabrowser.com

LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/

The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: thevibemarketer.com

Startup Empire - get your free builders toolkit to build cashflowing business - https://startup-ideas-pod.link/startup-empire-toolkit

Become a member - https://startup-ideas-pod.link/startup-empire

FIND ME ON SOCIAL

X/Twitter: https://twitter.com/gregisenberg

Instagram: https://instagram.com/gregisenberg/

LinkedIn: https://www.linkedin.com/in/gisenberg/

More from The Startup Ideas Podcast

All 140 episodes
Prompt Claude better than 99% of peopleThe Startup Ideas Podcast · 17 min
Listen in VO