Since July 21, readers on web and iOS can run any Substack post, note, comment, or reply longer than 100 words through Pangram and get a percentage back, with Android still coming. Some writers just are on the side of what would be technically correct, like an AI. I already wrote up how the scan works and how to switch it off. This is the other half.

What ZeroGPT Said About a Paragraph I Wrote Myself

Pangram’s own checker wants you to have an account before it scores anything, so I used ZeroGPT, which doesn’t. I ran the passages through ZeroGPT last week, I believe it was on Thursday. The first was textbook clean writing: hedged, generic, ending on an uplifting summary line, and it came back 100%.

The second was a first-person paragraph about my mornings, written in one pass. The score came up in its dashboard as 98%, and I immediately felt, “How the fuck is this 98% AI when I wrote it?” Then I started to think, “Maybe I write like AI.”

Does a Technical Writing Degree Read Like a Machine?

I do have a master’s in technical writing. Is that just AI writing? People have said that I write in a very clean, almost technical way, even when I’m trying to be entertaining or even to write in a fictional voice, not writing fictional stories. I thought, “Well, maybe I just sound like AI when I write.”

I can’t shake that theory, and the research doesn’t rule it out. By the way, if you’re new to Substack or just getting started with your writing career, be sure to check out my list of the writing rules you should know.

The Monetizer

25 Writing Rules Every Substack Creator Should Know

The best Substack writers are not the fanciest. They are the clearest. These 25 rules, inspired by The Elements of Style, will help you write better posts, sharper emails, and stronger paid newsletters…

Read more

4 months ago · 24 likes · Levi Chambers

Pangram’s False Positive Rate: 0%, 2%, or One in 10,000

It annoys the shit out of me that sometimes technically correct writing will flag as AI, even when it’s not. Three groups have tested Pangram independently and their numbers don’t agree. A peer-reviewed Vrije Universiteit Brussel paper scored it 97.5% on fully AI-generated academic papers, zero false positives across 160 documents. University of Chicago researchers Brian Jabarian and Alex Imas ran close to 4,000 texts and found Pangram “dominates the other detectors across all thresholds.”

It makes me think, “I’m sorry, do you think that humans don’t know what a fucking em dash is? Do you think that they don’t know what proper punctuation is?” A University of Maryland experiment landed at 2% false positives. Pangram CEO Max Spero puts it closer to one in 10,000.

I get it: a lot of people are terrible writers, and I’ll be honest. I happen to be a very good writer. Two percent of a platform this size is a lot of people getting told they didn’t write their own work. In fact, when I was in fifth grade, my substitute teacher (what was her name, Mrs. Drake?) read a short story that I wrote and then told me that I should be an author. It must have been pretty fucking good because I was like 12 years old impressing a 70 year old English teacher. It was in a small town, so maybe she wasn’t the best judge, but you get it.

Chris Best, Mack Collier, and the Witch Hunt Complaint

Best is upfront about the limit: Pangram “can only detect whether AI was used to make the text, not whether great human care went into creating it, nor whether AI tools were used as a source,” he wrote. His bigger argument: AI content “pollutes the commons.”

Writers pushed back inside a week. Mack Collier said he is “not going to apologize for using AI in the creation process.” Ghostwriting coach Alice Lemee called detectors “notoriously, wildly inaccurate.” Sam Illingworth, author of Slow AI, says Substack is asking a machine to vouch for a human. I think that there’s a scale that AI is using the detectors in terms of identifying AI content, and it is not always right.

How I Rewrite a n AI Draft Before Publishing

Usually, when I use AI to help me come up with the first draft of an article, I am almost always rewriting every sentence in my own words. Sometimes I’m even rearranging the paragraphs of the sentences because I think they flow better in a more human way. It may not be as technically correct as it would be if Claude created it or if ChatGPT created it, but I rearrange things in a way that I beleive is my voice and is human.

That last part is the trick. Swapping an em dash for a colon or deleting “delve” is a workaround, not a rewrite.

Rewriting the Morning Routine Paragraph, Line by Line

Here it is on an actual paragraph; a real example. I was trying to show the difference between how AI content and human content will sound, but I probably could have cleaned up the “after” a little bit more, although “before” does sound borderline AI.

The Falsely Accused AI version (Scored 98% AI):

Building a morning routine is one of the most effective ways to boost productivity and improve overall well-being. It is important to note that a consistent routine helps regulate your body’s internal clock, leading to better sleep quality and increased energy throughout the day.

It is very technically correct, whereas the “after” reads like it was written by a new writer.

My rewritten and dumbed down human version (scored 100% human):

My mornings used to be insane. Like every other human on this planet, I would get up, check my phone for 20 minutes, scroll on Instagram, and watch countless people fall down before I even got out of bed. Then I would spend the rest of the day feeling behind. I would need to go to the gym. I would need to let the dog out because I spent too much time scrolling. Now I do three things before I do anything: I get up and stretch for five minutes, not full-on yoga, but I do some stretches. I drink some water. I usually have coffee, but right after that, I write down the one thing I actually need to get done that day, sometimes even that morning.

I guess the dog-moment is the part no model can hand you? In the end, it seems that Pangram just scores clean writing as AI and messy writing as human. Given the bias, I think every human should fill out their “How I Make This” statement before Pangram scores their work as AI and the reader makes their own judgement.

What I Would Put in “How I Make This”

Substack gives you a field for this. My “How I Make This” line states that I do use AI for organizing thoughts, for coming up with outlines, but then I write the content, by and large. Obviously, I put everything through Grammarly. I don’t want to be publishing content that’s grammatically incorrect or has spelling errors. I am using the tools that are there to make me a better writer, but the thought, the organization, the content itself is mine.

Writing that down costs nothing, and you can also scan your own drafts before publishing and report a scan you believe is wrong.

Do Not Paste Confidential Drafts Into a Detector

One thing before you go check your archive: Pangram and ZeroGPT are third-party web forms, and you’re handing them unpublished work. Don’t paste unconfirmed interview quotes, financial figures that aren’t public, or anything under NDA. A percentage on a screen isn’t worth that.

If you write on Substack, fill in your "How I make this" field this week. Not because the scan is going to out you. Because your version of the sentence is better than whatever a reader invents when the field is blank.

Subscribe now

Read more

Substack’s CEO gave that gut-punch a name this month: claudefishing. And the platform just released a tool to help readers catch it.

What Is “Claudefishing”

Chris Best, Substack’s CEO, coined the term in a July 2026 post called “Against Claudefishing.” He defined it as a mismatch between what a reader expects and what they actually get, especially when they invest real attention in something with no human thought behind it.

Best made his own position clear in the same post.

The name riffs on catfishing, the old scam where someone fakes an identity to lure people in. Claudefishing does the same thing with words instead of photos and DMs. A post reads like a person poured themselves into it but in reality an AI actually wrote most of it, and no one disclosed that.

Best’s point isn’t that AI-assisted writing is bad. It’s that readers deserve to know what they’re getting, and right now, most can’t tell AI from human content.

Why Substack Built an AI Detector With Pangram

On July 21, 2026, Substack launched a detection feature built with Pangram, an AI-detection company. It scans posts, notes, comments, and replies and estimates how much of the text a human wrote versus how much came from AI.

A few things to know about how it’s scoped:

• The scan only works on content published on or after July 21, 2026, according to Substack’s help center.

• It can’t retroactively check your archive or someone else’s.

• Substack’s own documentation confirms shorter notes show a “not enough text” message rather than a score; multiple outlets covering the launch report that the practical cutoff is around 100 words, though Substack hasn’t published that exact figure itself.

• Results are visible only to the person who requests the scan.

• Nobody gets a public AI score badge slapped on their profile. It launched on web and iOS, with Android support still on the way.

Best has been direct that this isn’t a purity test: “It is not perfect, but independent research suggests that it detects AI-generated text with a high degree of accuracy,” he said. That’s Substack and Pangram’s own claim, worth noting as a claim, not an independently audited result.

How to Scan Any Post or Note for AI Text

Here’s exactly how to run a scan yourself:

On the web:

1. Open a post from your Subscriptions in the Substack reader.

2. Click the three dots in the top right corner.

3. Select “Scan for AI text.”

On a Note:

1. Click the three dots on the Note.

2. Select “Scan for AI text.”

On iOS:

1. Tap the post or Note you want to check.

2. Tap the three dots in the upper right corner.

3. Tap “Scan for AI text.”

You can also scan individual comments and replies inside a Notes thread the same way.

A few formats are off limits for now. Video and audio posts, standalone Substack sites on custom domains, and emails can’t be scanned.

How Writers Can Disclose AI Use or Turn Off Scanning

If you publish on Substack and use AI anywhere in your process, you have three tools worth setting up today.

1. Add a “How I make this” statement. Go to your publication’s Settings, then Details. Click “Edit” next to your statement, describe your actual process, and save it. Readers see this when they scan your work, so it’s your chance to explain your process in your own words instead of letting a percentage speak for you.

2. Scan your own drafts before you publish. Run the same “Scan for AI text” check on a draft to see how it reads before your subscribers do.

3. Disable detection if you want to. On the Publish page of a draft, click “Disable AI detection.” On a Note, open the three-dot menu after a scan appears and select “Disable detection.” Readers will see an “AI detection unavailable” message instead of a score.

If a scan result looks wrong, you can push back. Select “Report detection error” on the report and submit feedback, which Substack says goes toward improving the tool.

The Real Limits of Pangram’s Scores, According to Critics

Here’s the part worth taking seriously before you treat any AI score as gospel, in either direction.

Matteo Wong, writing in The Atlantic, reported that Pangram’s tool “does make mistakes, perhaps to a greater extent than is currently understood,” and warned that AI accusations “could very quickly spiral into a witch hunt.”

Developer Perry Metzger has argued that any AI detector can be circumvented through fine-tuning, which makes detection an inherently temporary fix rather than a permanent solution.

Researcher Mor Naaman has gone further, framing detection as an unwinnable race: once writers know they’re being scanned, some will simply learn to write around the scanner.

Independent Substack writer Sam Illingworth, who publishes “Slow AI,” ran his own test. One of his posts scored as fully AI-generated, then scored as fully human after he ran it through a free “humanizer” tool. His conclusion: the tool measures how text is phrased, not who actually wrote it or how much care went into it.

None of that means the tool is useless. It means a percentage on a screen is a signal, not a verdict. Substack itself has acknowledged the tool isn’t perfect, and no detector, from any company, catches everything or nothing.

What This Means If You Use Claude to Write

If you use Claude, or any AI tool, anywhere in your writing process, claudefishing isn’t a threat to you. It’s a nudge to be upfront about something you were probably already comfortable with.

Write your “How I make this” statement now, before a reader scans your work and wonders “was this written by AI?” and be truthful. Say plainly what you draft yourself, what Claude or ChatGPT helps you edit or research, and what stays entirely yours. That single paragraph builds more trust than any score ever will.

Use the scan on your own drafts as a reality check, not a grade. If a heavily AI-assisted draft comes back scored as mostly AI, that’s accurate, not a bug. The fix isn’t hiding it better. It’s deciding how much of the final piece should carry your own judgment, examples, and voice before you hit publish.

And don’t let a false flag rattle you either. If Substack’s scan misreads your fully human writing as AI-generated, use the “Report detection error” option and keep publishing. The tool is new, imperfect, and still learning. Your voice isn’t. And remember you are what makes your work younique.

How to use Claude smarter so you waste fewer messages, fewer tokens, and way less creative momentum.

There is nothing more annoying than hitting your Claude limit right when the work finally starts getting good. You are in the flow. Claude understands the assignment. The draft is sharper. The spreadsheet is almost there. The strategy is finally making sense. Then suddenly, the party is over.

Rude.

The first thing to know is this: Claude usage is not just about how many messages you send. Anthropic says usage depends on several factors, including message length, file attachment size, conversation length, tool usage, model choice, effort level, and artifact creation. That means one messy, file-heavy, tool-heavy chat can burn through your limit faster than several clean, focused conversations. (Claude Help Center)

So this is not really an article about “hacking” Claude. I do not want you thinking like a little AI coupon goblin. This is about building a cleaner workflow so Claude lasts longer, works better, and stops eating your usage before lunch.

You may still hit your limits on big workdays. That happens. But most people are not hitting limits because they are doing too much smart work. They are hitting limits because they are dragging too much junk into the room.

Let’s fix that.

What Actually Burns Through Claude Usage?

Claude is powerful because it can hold a lot of context, read files, use tools, create artifacts, reason deeply, and work across long conversations. That is the good news. The bad news is that all of those features have a cost.

Think of every Claude chat like a room. Every message, file, tool, and previous answer is something Claude may need to carry around. The more you bring into the room, the heavier the conversation gets. That does not mean you should avoid context. Context is what makes Claude useful. It means you should bring the right context.

Anthropic separates usage limits from length limits. Usage limits control how much you can use Claude over time, while length limits control how long or complex a single conversation can become. If you hit a usage limit, you may need to wait, upgrade, or use credits. If you hit a length limit, starting a new conversation or using Projects can help. (Claude Help Center)

That distinction matters. Sometimes your problem is not that you need a bigger plan. Sometimes your chat is just bloated. Other times, your setup is burning usage because you keep re-uploading the same files, sending tiny corrections, using Research for simple tasks, or asking Claude to build before you know what you want.

Claude is not punishing you for being ambitious. It is charging your limit for everything you make it process.

1. Shrink Your Files Before You Upload Them

This is the easiest win. Stop uploading giant PDFs, full slide decks, uncropped screenshots, and messy documents when Claude only needs a few sections.

File attachment size affects Claude usage. That means a huge PDF with 80 irrelevant pages is not harmless. Neither is a screenshot that includes your entire desktop when Claude only needs one chart. Smaller, cleaner files help Claude focus and help you waste less usage. (Claude Help Center)

Before uploading anything, ask yourself what Claude actually needs. Does it need the whole PDF, or just pages 3 through 7? Does it need the whole bank statement, or a cleaned list of categories and totals? Does it need a screenshot, or could you copy the text into a plain file?

My rule is simple: do not upload the whole haunted document if Claude only needs three paragraphs.

For recurring work, I would use plain text or markdown files whenever possible. They are clean, light, and easy for Claude to read. A file called brand-voice.md is usually more useful than a 47-page brand deck full of images Claude does not need for the task.

Use this prompt before uploading a giant source file:

I have source material for this task, but I do not want to upload more than necessary.

The task is: [describe task]

Tell me exactly what parts of the source material you need. Tell me what I can remove, summarize, crop, or paste as plain text before I upload anything.

This turns Claude into your context bouncer. Very chic. Very necessary.

2. Plan First, Build Last

Most people waste Claude usage by asking for the final asset too early. They start with “make me a spreadsheet,” “write the full article,” “create the presentation,” or “build the launch plan.” Then Claude creates something close, but not quite right. Then they spend ten messages fixing what could have been clarified upfront.

That is expensive.

The better move is to use Claude cheaply at the planning stage before asking it to generate the heavy output. First, define the goal. Then define the audience. Then define what “done” looks like. Then ask for the structure. Then approve the structure. Only after that should Claude build the file, artifact, spreadsheet, deck, or final draft.

Anthropic’s usage guidance recommends planning conversations before starting, combining related questions, and providing background upfront to reduce back-and-forth. That is exactly the workflow here. (Claude Help Center)

Think cheap. Build expensive.

Do not ask Claude to cook the whole meal before you know what you are eating.

Use this prompt:

Before creating anything, help me plan the task.

My goal is: [goal]
The final output should be: [output]
The audience is: [audience]
Success looks like: [success criteria]

Ask me any missing questions first. Then give me the simplest plan before you build.

This one prompt can save you a ridiculous amount of cleanup.

3. Make Claude Ask You Questions First

One of the fastest ways to waste usage is making Claude guess. Guessing creates generic output. Generic output creates corrections. Corrections create longer chats. Longer chats burn more usage.

So stop letting Claude guess.

Before any important task, tell Claude to interview you first. I use this all the time because it forces the tool to gather the missing context before it starts producing. It also makes you think more clearly about what you actually want.

Anthropic recommends clear, detailed instructions and relevant context because vague questions often require more clarification. So give Claude permission to clarify before it creates. (Claude Help Center)

Use this:

Before you start, ask me the 7 questions you need answered to do this well.

After I answer, summarize the plan and wait for my approval before creating the final output.

This feels slower for about two minutes. Then it saves the entire project.

Most people want AI to skip thinking. You want AI to extract your thinking. That is the difference between a messy chat and a useful one.

4. Edit the Old Prompt Instead of Sending Another Correction

Every “wait, actually…” makes the conversation heavier.

We have all done it. You send a prompt. Claude gives you something wrong. Then you send another message correcting it. Then another. Then another. Suddenly, your simple task has become a 19-message therapy session about a spreadsheet.

When possible, edit the original prompt instead. Fix the instruction at the source, regenerate, and avoid stacking correction after correction. Anthropic’s own guidance recommends reviewing and editing your prompt before sending to reduce follow-up messages. (Claude Help Center)

This is especially useful when your original prompt was missing something important. Maybe you forgot the audience. Maybe the tone was wrong. Maybe you asked for a full draft when you needed an outline. Fix that upstream.

Bad workflow:

Write this article.
No, make it more human.
No, not that human.
Actually, use paragraph format.
Wait, add SEO.
No, less repetitive.

Better workflow:

Write an SEO-optimized article for Academy of AI.

Use paragraph format. Avoid short, single-sentence paragraphs. Write in Levi Chambers voice: direct, warm, practical, human, and a little playful. Avoid generic AI phrasing, corporate language, and repetition.

Before drafting, give me the outline first.

Clean prompts save usage. They also save your sanity.

5. Start Fresh When the Chat Gets Too Heavy

Long chats can be useful, but they can also get expensive and weird. Claude remembers earlier context in a conversation, which is helpful until the conversation becomes a junk drawer.

If a chat has gone on for a while, start fresh. This is not quitting. This is cleaning the room.

Anthropic notes that current conversation length affects usage, and its length-limit guidance says that starting a new conversation can help when a chat becomes too long or complex. (Claude Help Center) (Claude Help Center)

My favorite move is the handoff summary. Before leaving a long chat, ask Claude to summarize only what matters. Then paste that summary into a fresh chat and keep moving without dragging every old detour behind you.

Use this:

Summarize this conversation so I can continue in a fresh chat.

Include:
1. The goal
2. Key decisions
3. Important context
4. Current draft or plan
5. Next steps
6. Anything Claude must not forget

Keep it concise and remove anything irrelevant.

Then start a new chat and paste:

Here is the handoff summary from my previous chat.

Use this as context and continue from here:
[paste summary]

Shorter chats are cleaner chats. Cleaner chats are cheaper chats.

6. Choose the Right Model and Effort Level

Not every task needs the most powerful model and highest effort setting. You do not need a bulldozer to plant a flower.

Claude lets users change the model, effort level, and thinking settings in supported plans. Anthropic says higher effort can produce more thorough responses, but it takes longer and uses more tokens, which means you can reach usage limits faster. It also says low and medium effort work well for routine tasks and stretch usage further. (Claude Help Center)

Use the lighter setup for quick rewrites, captions, simple summaries, formatting, brainstorming, and low-stakes tasks. Use stronger models or higher effort for hard strategy, coding, complex analysis, serious research, financial modeling, technical planning, and anything you cannot afford to get wrong.

This is not about being cheap. It is about matching the tool to the task.

Use this prompt before starting:

Before we begin, tell me what level of reasoning this task actually needs.

Should I use a faster model, stronger model, lower effort, higher effort, extended thinking, web search, Research, or no tools at all?

Explain the simplest setup that will get a good result without wasting usage.

Claude cannot change your settings for you in every context, but it can help you think through the right setup.

7. Use Projects for Anything You Reuse

If you upload the same file more than once, you probably need a Project.

Claude Projects are one of the best ways to stop wasting usage because they let you keep recurring context in one place. Anthropic says project content is cached, and when you reference uploaded project documents again, only new or uncached portions count against your limits. That means repeated use of the same project files can be more efficient than re-uploading them in every chat. (Claude Help Center)

This is huge for creators, founders, freelancers, educators, and anyone doing repeat work. Your brand voice, audience notes, product details, customer objections, SEO rules, article examples, offer docs, and templates should not be reintroduced every time. Put them in a Project once.

Use Projects for:

brand-voice.md
about-me.md
audience.md
offers.md
content-pillars.md
examples-i-love.md
examples-i-hate.md
customer-objections.md
seo-checklist.md
recurring-prompts.md

Upload once. Use forever.

That is the move.

8. Keep Project Files Clean

Projects help, but they are not an excuse to dump 400 files into Claude and call it context. That is not strategy. That is digital hoarding with a subscription.

Anthropic says Projects can use retrieval augmented generation, or RAG, to store and access significantly more knowledge. RAG retrieves relevant information from uploaded documents instead of loading everything at once, and Anthropic says it can expand project capacity by up to 10x when needed. (Claude Help Center)

That is powerful. It still needs clean inputs.

Use clear filenames. Group related content together. Remove old files you no longer use. Keep project instructions concise. Claude’s docs also recommend descriptive filenames and organized related content to help retrieval work better. (Claude Help Center)

Bad filenames:

final.pdf
notes2.md
stuff.md
new-version-REAL-final.docx

Good filenames:

academy-of-ai-voice-guide.md
substack-audience-notes.md
claude-limit-article-outline.md
seo-checklist-for-ai-articles.md
examples-i-love-ai-newsletters.md

Treat your project like a clean studio, not a garage where old files go to die.

9. Turn Off Tools You Do Not Need

Claude tools are amazing. They can also be expensive.

Web search, Research, connectors, extended thinking, and other tools are not decoration. They do extra work. Anthropic says tool usage affects limits, and its length-limit guidance specifically recommends disabling non-critical tools and connectors when they are not needed because tools and connectors are token-intensive. (Claude Help Center) (Claude Help Center)

Do not use web search for basic writing. Do not use Research when you just need a rewrite. Do not leave connectors on when you already pasted the relevant context. Do not use extended thinking for a caption. Please do not ask the AI to bring a forklift to move a napkin.

Research is especially useful, but it can use limits faster because Claude may retrieve multiple sources and produce comprehensive responses. Use it when the task deserves that depth. Do not use it because you are too lazy to decide what you need. (Claude Help Center)

Use this tool-control prompt:

Before starting, tell me which tools or settings this task actually needs.

If web search, Research, connectors, extended thinking, or artifact creation are not necessary, say so.

Use the simplest setup that can still produce a strong answer.

Only pay for what you are using right now. That is good AI hygiene.

10. Batch Your Work Instead of Dripping Tiny Requests

Tiny requests feel harmless. They are not always harmless.

If you send Claude three tiny related questions, that may be less efficient than one clean message with all three. Anthropic recommends batching similar requests in one message when possible. It also recommends providing all relevant data in a single, well-structured message for research and analysis. (Claude Help Center)

This does not mean you should send a monster prompt full of chaos. It means you should group related work.

Instead of this:

Give me 10 titles.
Now give me subtitles.
Now give me SEO descriptions.
Now give me tags.
Now give me social captions.

Try this:

For this article topic, give me:
1. 10 Substack titles
2. 10 subtitles
3. 3 SEO titles
4. 3 SEO descriptions
5. 10 tags
6. 5 Facebook captions

Keep everything in Academy of AI voice.

One clean message beats six scattered ones.

This also works for editing. Send the whole text in one message instead of pasting it section by section, unless the document is too large. Anthropic specifically recommends sending entire texts for editing in one message rather than breaking them up. (Claude Help Center)

11. Watch Your Usage Before You Hit the Wall

Do not wait until Claude cuts you off to learn how much usage you burned. Check your usage settings.

Anthropic says Pro, Max, Team, and seat-based Enterprise users can go to Settings > Usage to view progress bars for current five-hour session usage and weekly limits. That gives you a better sense of when to do heavy work and when to save the big tasks for later. (Claude Help Center)

This is especially useful if you use Claude for serious work. You can plan your day around heavier sessions. Do deep research, long file work, or high-effort strategy when you have room. Save simple rewrites and light prompts for lower-energy moments.

This is not glamorous. Neither is running out of Claude halfway through a launch plan.

Plan your AI time like it matters.

Because it does.

12. Build a Claude Limit Workflow

Here is the Academy of AI version. Screenshot this. Save it. Use it before your next serious Claude session.

1. Strip files down to what matters.
2. Start with the goal and success criteria.
3. Ask Claude to ask questions first.
4. Approve the plan before generating.
5. Use the right model, effort level, and tools.
6. Move recurring context into Projects.
7. Batch related requests into one clean message.
8. Summarize and restart when the chat gets heavy.

That is the whole workflow.

It is not complicated. It just requires a little discipline before you start asking Claude to do big things. Most AI waste happens before the first good prompt. It happens when the user has not decided what they want, what files matter, what tools are needed, or what success looks like.

Claude works better when you lead.

Copy-and-Paste Prompts to Save Claude Usage

Use these before big tasks. They are simple, but they can save you a lot of back-and-forth.

The Planning Prompt

Before creating anything, help me plan the task.

My goal is: [goal]
The final output should be: [output]
The audience is: [audience]
Success looks like: [success criteria]

Ask me any missing questions first. Then give me the simplest plan before you build.

The File-Shrinking Prompt

I have source material for this task, but I want to avoid uploading unnecessary files.

The task is: [task]

Tell me what information you actually need, what I can remove, what I should crop, what I should summarize, and what should be pasted as plain text.

The Fresh-Chat Handoff Prompt

Create a clean handoff summary so I can continue this work in a new Claude chat.

Include:
1. Goal
2. Audience
3. Important context
4. Decisions made
5. Current draft or plan
6. Next steps
7. Anything Claude must avoid

The Tool-Control Prompt

Before starting, tell me which tools or settings this task actually needs.

If web search, Research, connectors, extended thinking, high effort, or artifact creation are not necessary, tell me.

Use the simplest setup that can still produce a strong result.

The Project Setup Prompt

I do this task repeatedly and want to stop re-uploading context.

Help me turn it into a Claude Project.

Tell me:
1. What files to create
2. What instructions to add
3. What examples to upload
4. What recurring prompts to save
5. What workflow to follow each time

The Usage Audit Prompt

Review this Claude conversation and tell me where I wasted usage.

Look for:
1. Repeated context
2. Unnecessary tools
3. Vague prompts
4. Oversized files
5. Long-chat issues
6. Correction loops
7. Anything that should move into a Project

Then give me a cleaner workflow for next time.

That last prompt is a little humbling. Good. Humbling saves tokens.

Common Mistakes That Burn Claude Usage

The biggest mistake is uploading every file “just in case.” That sounds responsible, but it usually creates noise. Claude does not need your whole archive to help with one section of one project.

The second mistake is asking for the finished asset before planning. That creates beautiful wrong work. Beautiful wrong work is still wrong. It just wastes more time because now you have to edit something that should never have been built.

The third mistake is correction stacking. Every time you send “no, I meant…” you add more weight to the chat. Fix the original prompt when possible. Start clean when needed.

The fourth mistake is using the strongest model, highest effort, extended thinking, Research, web search, connectors, and artifacts for a tiny task. That is not advanced. That is expensive chaos in a cute outfit.

The fifth mistake is refusing to use Projects. If Claude needs your brand voice, audience, product details, examples, or source docs more than once, that context belongs in a Project. Repeating yourself to AI is unpaid admin work.

What This Means for You

Claude limits are annoying, but they are also useful feedback. They show you whether your AI workflow is clean or chaotic.

If you keep hitting the wall too fast, you may not need more Claude. You may need smaller files, clearer prompts, shorter chats, better Projects, fewer tools, and a stronger habit of planning before generating.

Claude should feel like leverage, not a slot machine. You should not be throwing prompts into the void and hoping one comes back useful. Give it cleaner inputs. Give it stronger context. Give it less junk to carry.

That is how you get more useful work from the same tool.

Not by begging Claude to last longer.

By using it like someone who knows what the hell they are doing.

Your First Assignment

Open your last long Claude chat and paste this:

Review this conversation and tell me where I wasted usage.

Identify repeated context, unnecessary tools, unclear prompts, oversized files, long-chat issues, correction loops, and anything I should move into a Project.

Then give me a cleaner workflow for next time.

Run that today. Do not wait until your next usage limit meltdown.

The goal is not to use Claude less. The goal is to use Claude better.

And better is where the freedom is.

Subscribe to Academy of AI

Academy of AI helps everyday people learn the tools already changing work, money, creativity, and freedom. No panic, no jargon, and no gatekeeping. Just practical AI education for people who want to use AI with clarity, confidence, and power.

Subscribe to Academy of AI if you want to stop dabbling with AI and start building real leverage.

A random chat is fine for a quick answer. A Claude Project is what you use when the work matters. Claude describes Projects as self-contained workspaces with their own chat histories and knowledge bases, where you can upload documents, add context, and keep focused conversations together. Projects are available to all users, though free users currently have a five-project limit.

That matters because the future of AI is not better one-off prompts. The future is better setup. Your prompts get stronger when Claude has your context, your examples, your standards, your audience, your voice, your process, and your goals already sitting inside the project.

This is how you stop starting from zero every time.

Why Your Claude Project Needs a File System

A good Claude Project is not just a folder where you dump files and hope for magic. That is chaos in a cute outfit. A good project works more like an operating system.

It tells Claude what the project is, who it serves, what success looks like, how you think, what your standards are, what examples it should follow, what examples it should avoid, and how to help you move work forward.

Claude’s own docs make this clear. Project Knowledge lets you upload documents, text, code, or other files so Claude can use them as context in chats within that project. Project instructions then tell Claude how to behave and respond inside that workspace. Here is the important part people miss: Claude says context is not automatically shared across chats inside a project unless that information is added to the project knowledge base. So if something matters, do not assume Claude will remember it from another chat. Put it in the files.

The Simple Rule

If Claude needs to know it more than once, make it a file.

That includes your bio, your brand voice, your audience, your offers, your content pillars, your product details, your customer objections, your favorite examples, your recurring prompts, your workflows, your style rules, and your quality checklist.

A prompt is temporary. A file is reusable. That is the whole shift.

Step 1: Decide What the Project Is Actually For

Before you create anything in Claude, define the project. Do not skip this. A vague project creates vague output.

A good project has one clear job. It might be “Academy of AI Newsletter,” “Client Onboarding System,” “Course Creation,” “Sales Page Builder,” “Substack Growth,” “Personal Finance,” “Travel Planning,” or “Product Launch.”

Do not create one project called “Business” and stuff your entire life into it. That is how Claude starts mixing your newsletter strategy with your refund policy and your packing list for Palm Springs. We are not doing that.

Use this test: if the project has a different audience, goal, voice, workflow, or source material, it deserves its own Claude Project.

Step 2: Create the Project in Claude

Go to Claude, open Projects, and create a new project. Claude’s help guide says to click Projects, choose + New Project, then give the project a name and description. One sneaky detail: Claude says it does not have access to the name and description, so do not rely on those fields as actual working context. Put the real context inside project instructions and project knowledge.

If you are on a Team or Enterprise plan, choose the visibility setting carefully. Keep private projects private when they include your voice, client notes, company information, or sensitive strategy. Share projects only when the context is meant for the team.

Once the project exists, do not start prompting yet. Build the structure first.

Step 3: Create Your Local Project Folder

Before uploading files to Claude, create a local folder on your computer. This gives you a clean source of truth. You can update files over time, upload the current versions to Claude, and avoid turning your project knowledge into a junk drawer.

Here is the universal structure I would use for almost any Claude Project:

PROJECT-NAME/
  00_START_HERE/
    project-brief.md
    project-instructions.md
    how-to-use-this-project.md

  01_CONTEXT/
    about-me.md
    audience.md
    goals.md
    offers-or-products.md
    constraints.md
    glossary.md

  02_VOICE_AND_STANDARDS/
    voice-guide.md
    brand-rules.md
    quality-bar.md
    examples-i-love.md
    examples-i-hate.md
    mistakes-to-avoid.md

  03_SOURCE_MATERIAL/
    source-index.md
    research-notes.md
    customer-feedback.md
    interviews-or-transcripts.md
    relevant-links.md

  04_WORKFLOWS/
    workflow-index.md
    recurring-prompts.md
    creation-process.md
    review-checklist.md
    publishing-or-delivery-checklist.md

  05_OUTPUTS/
    drafts.md
    final-outputs.md
    decisions-log.md
    ideas-backlog.md

This structure works because it separates identity, context, standards, sources, workflows, and outputs. Claude can understand the project faster because each file has one job. You can also update the project without rewriting everything from scratch.

Step 4: Write the Project Brief

The project brief is the first file Claude should understand. This is the clean overview. It tells Claude what the project is, what it helps you do, who it serves, and what kind of output matters.

Create a file called project-brief.md and use this template:

# Project Brief

## Project Name
[Insert project name]

## What This Project Is For
[Explain the purpose of this project in plain English.]

## Who This Project Serves
[Describe the audience, customer, reader, client, or user.]

## Main Goals
1. [Goal one]
2. [Goal two]
3. [Goal three]

## Success Looks Like
[Describe what a great output or successful project result looks like.]

## What Claude Should Help With
[Writing, research, strategy, editing, planning, analysis, content creation, product building, etc.]

## What Claude Should Not Do
[List boundaries, mistakes, tone issues, overreach, privacy rules, or things you never want.]

## Current Status
[Starting, active, launching, maintaining, revising, scaling, etc.]

## Most Important Context
[Add the 5 to 10 details Claude must understand before helping.]

This file keeps the project grounded. When Claude starts drifting, you can point it back to the brief.

Step 5: Write the About-Me File

This is the file most people skip, and it is the reason their AI output sounds like everyone else. Claude needs to understand who you are, how you work, what you care about, and what kind of help actually feels useful.

Create about-me.md and use this:

# About Me

## Who I Am
My name is [name]. I am [role, business, creator identity, or professional background].

## What I Do
I help [audience] achieve [result] through [method, product, content, service, or expertise].

## My Current Focus
Right now I am focused on:
1. [Focus one]
2. [Focus two]
3. [Focus three]

## How I Like to Work
I prefer help that is [direct, practical, strategic, concise, detailed, creative, etc.].

## How I Like Information
I like responses that are [paragraph format, step-by-step, examples first, plain English, short sections, etc.].

## What I Hate in AI Output
Do not give me:
- Generic advice
- Corporate language
- Fake enthusiasm
- Overexplaining
- Repetition
- Unsupported claims
- Weak endings
- Anything that sounds like standard AI writing

## My Standards
Good work should be clear, useful, specific, human, and easy to act on.

Do not make this precious. Make it honest. The more specific you are, the less Claude has to guess.

Step 6: Build Your Voice Guide

Your voice guide is what keeps Claude from turning your work into polite oatmeal. This file should include your tone, sentence style, rhythm, phrases you use, phrases you hate, and examples of your real writing.

Create voice-guide.md and use this:

# Voice Guide

## Overall Voice
[Describe your voice in 3 to 5 sentences.]

## Tone
The tone should feel:
- [direct]
- [warm]
- [practical]
- [confident]
- [human]
- [funny when useful]

## Sentence Style
[Explain sentence length, rhythm, paragraph style, and pacing.]

## Vocabulary
Use words like:
- [word]
- [word]
- [word]

Avoid words like:
- leverage if not needed
- utilize
- transformative
- unlock unless it truly fits
- generic business jargon

## Humor
[Explain how humor should work. Dry, playful, bold, sarcastic, light, etc.]

## Formatting Preferences
[Paragraph format, headings, clean sections, limited bullets, no single-sentence paragraphs, etc.]

## Example of My Writing
Paste 2 to 5 examples here.

## Why These Examples Work
[Explain what makes them sound like you.]

For Academy of AI, I would add something like: “Write like I am explaining this to a smart friend who wants to win, not like I am presenting at a corporate AI summit.” That one rule fixes a lot of AI nonsense.

Step 7: Add Examples You Love and Hate

Claude learns faster when you show it what good looks like. It learns even faster when you also show it what bad looks like.

Create examples-i-love.md and add strong examples of the kind of work you want. These can be article intros, headlines, emails, landing pages, workflows, outlines, captions, or reports.

Then create examples-i-hate.md and add things you never want. This is the fun file. Put the boring stuff here. Put the generic AI phrases here. Put the lifeless intros here. Give Claude a clear “absolutely not” list.

Use this format:

# Examples I Love

## Example 1
[Paste example.]

## Why It Works
[Explain the rhythm, tone, structure, clarity, emotion, or usefulness.]

## What Claude Should Learn
[State the reusable lesson.]

And:

# Examples I Hate

## Example 1
[Paste bad example.]

## Why It Does Not Work
[Explain what feels generic, boring, confusing, fake, or off-brand.]

## What Claude Should Avoid
[State the rule.]

This is where your taste becomes reusable. That is the real power.

Step 8: Create Your Audience File

If Claude does not understand your audience, it will write for “everyone.” Writing for everyone is how content goes to die.

Create audience.md and use this:

# Audience

## Primary Audience
[Describe the main reader, buyer, client, or user.]

## What They Want
[What are they trying to achieve?]

## What They Struggle With
[What frustrates them? What keeps them stuck?]

## What They Already Know
[Beginner, intermediate, expert, mixed.]

## What They Do Not Want
[What turns them off? What feels overwhelming?]

## Emotional State
They may feel [curious, overwhelmed, behind, ambitious, skeptical, excited, etc.].

## Buying or Subscription Triggers
They take action when [specific trigger].

## Language They Use
Include real phrases, comments, objections, or questions from the audience.

## What Makes Them Trust Us
[Practicality, clarity, proof, honesty, lived experience, results, etc.]

This file makes every output sharper. Articles get better. Sales pages get better. Product ideas get better. Everything gets better when Claude knows who the hell it is talking to.

Step 9: Add Your Goals and Constraints

Claude needs to know what game you are playing. Are you trying to grow subscribers? Sell a product? Create a course? Save time? Build authority? Simplify your life? Launch something this week?

Create goals.md:

# Goals

## Primary Goal
[Insert the main goal.]

## Secondary Goals
1. [Goal]
2. [Goal]
3. [Goal]

## Timeline
[Now, this week, this month, this quarter, this year.]

## Success Metrics
[Subscribers, revenue, conversion rate, comments, shares, time saved, leads, sales, etc.]

## Current Bottlenecks
[What is slowing you down?]

## What We Are Optimizing For
[Speed, quality, clarity, revenue, growth, trust, simplicity, etc.]

Then create constraints.md:

# Constraints

## Time Constraints
[How much time is available?]

## Budget Constraints
[Budget or no budget.]

## Tools Available
[List tools, platforms, software, and accounts.]

## Skills Available
[What you or your team can actually do.]

## Things We Will Not Do
[List boundaries.]

## Risk Areas
[Privacy, accuracy, legal, brand trust, deadlines, technical complexity, etc.]

Constraints are not annoying. Constraints make Claude useful. Without them, Claude gives you the fantasy plan. With them, it gives you the plan you can actually use.

Step 10: Write Your Project Instructions

Project instructions are the rules Claude follows inside that specific project. Claude’s personalization docs describe project instructions as project-specific guidance for focused workflows, requirements, roles, and consistent context across conversations. Profile instructions are account-wide, while project instructions are for a specific workspace.

Here is a strong project instructions template:

You are the AI working partner for this project.

Your job is to help me produce clear, useful, high-quality work based on the files in this project.

Always do the following:
1. Read the relevant project files before giving strategic answers.
2. Ask clarifying questions before complex tasks.
3. Use the audience, voice guide, goals, and constraints.
4. Be direct, practical, and specific.
5. Flag uncertainty instead of pretending.
6. Separate facts from assumptions when needed.
7. Prioritize clarity, usefulness, and trust.
8. Avoid generic AI writing, corporate language, and filler.
9. Do not overpromise.
10. Give me the version I can actually use.

For writing tasks:
- Match the voice guide.
- Use clean headings.
- Write in paragraph format unless I ask for bullets.
- Avoid short, single-sentence paragraphs.
- Keep the tone human, confident, and useful.

For strategy tasks:
- Identify the real problem first.
- Compare options when helpful.
- Tell me what you recommend and why.
- Include risks, tradeoffs, and next steps.

For research tasks:
- Cite sources when current facts matter.
- Tell me what needs verification.
- Do not invent data, quotes, or sources.

Before starting any important task, ask:
“What outcome do you want, who is this for, and what does done look like?”

Paste this into Set project instructions inside Claude. Then upload it as project-instructions.md too. I like having it in both places. The instruction field controls Claude’s behavior, and the file gives you a saved source you can edit later.

Step 11: Upload the Files to Claude Project Knowledge

Once your files are ready, upload them into the project knowledge base. Claude’s guide says you can add content by clicking the plus button in the project, uploading relevant documents, text files, or code snippets, and Claude will process that information for use in chats inside the project.

Claude supports common file types like PDF, DOCX, CSV, TXT, HTML, ODT, RTF, EPUB, JSON, and XLSX if code execution and file creation are enabled. Project files currently have a 30MB per-file limit, and project file content is text extraction only except for multimodal PDFs.

Use clear filenames. Claude’s RAG guidance specifically recommends clear, descriptive filenames and grouping related content together, because that helps Claude retrieve the right information from project knowledge.

Bad filenames look like this:

notes-final-v3-really-final.md
doc1.pdf
random.txt
new-stuff.md

Good filenames look like this:

audience-paid-substack-creators.md
voice-guide-academy-of-ai.md
examples-i-love-newsletter-intros.md
customer-objections-ai-beginners.md
seo-article-review-checklist.md

Make the file name tell Claude what is inside. Your future self will also appreciate not living in document hell.

Step 12: Add Google Drive Files When Needed

If your source material lives in Google Drive, you may not need to download and re-upload everything. Claude’s Google Workspace connector can add Google Docs directly to chats and projects by pasting URLs or selecting recent documents, and Google Docs added to projects sync from Drive so Claude can access the latest version. This applies to private projects, and Claude notes that the Drive option is disabled for shared projects.

This is useful for living documents, like brand guides, editorial calendars, client briefs, research docs, and SOPs. Just remember that Claude says it extracts text content only from Google Drive files, and embedded images in documents are not processed through that connector.

Use Drive for documents that change often. Use uploaded markdown files for your core project brain.

Step 13: Create Your Workflow Files

Workflow files tell Claude how you want repeat tasks handled. This is where the project becomes a machine.

Create workflow-index.md:

# Workflow Index

This project includes the following repeat workflows:

1. Article creation workflow
2. Research workflow
3. Editing workflow
4. SEO optimization workflow
5. Social caption workflow
6. Final QA workflow

Claude should ask which workflow to use when the task is unclear.

Create creation-process.md:

# Creation Process

## Step 1: Clarify the Outcome
Ask what we are creating, who it is for, where it will be published, and what success looks like.

## Step 2: Review Context
Use the project brief, audience file, voice guide, examples, goals, and constraints.

## Step 3: Create an Outline
Do not draft the full piece until the outline is clear.

## Step 4: Draft
Write in the approved voice and structure.

## Step 5: Improve
Edit for clarity, repetition, usefulness, originality, and voice.

## Step 6: Optimize
Add SEO title, description, URL slug, social title, social description, Substack title, subtitle, and tags.

## Step 7: QA
Check for unsupported claims, generic phrasing, weak transitions, and anything off-brand.

Create review-checklist.md:

# Review Checklist

Before finalizing any output, check:

- Does this match the project goal?
- Does this speak to the right audience?
- Does this sound like the voice guide?
- Is anything generic or obvious?
- Is anything repeated?
- Are claims supported?
- Are examples specific?
- Is the next step clear?
- Does this feel useful enough to publish, send, or sell?

These files save you from retyping your standards every single time. That is the point. Repeating yourself to AI is not a business model.

Step 14: Create Recurring Prompts

Recurring prompts are the prompts you know you will use again. Put them in recurring-prompts.md.

Here are a few I would include in every Claude Project:

# Start a New Task

Read the relevant files in this project first.

Then ask me up to 7 clarifying questions before you begin.

The task is:
[insert task]

# Project Audit

Review the files in this project.

Tell me:
1. What this project is set up to do
2. What context is strong
3. What context is missing
4. What files should be updated
5. What Claude may misunderstand
6. The next 5 improvements I should make

# Improve This Output

Use the project files to improve this draft.

Check for:
- Clarity
- Usefulness
- Voice
- Audience fit
- Repetition
- Generic AI language
- Missing examples
- Unsupported claims

Do not rewrite everything unless needed. First give me the improvement plan.

Draft:
[paste draft]

# Create From Scratch

Use the project brief, audience file, voice guide, examples, goals, and workflow files.

Create:
[insert deliverable]

Before drafting, give me:
1. The proposed structure
2. The key angle
3. What files you used
4. Any questions you need answered

These prompts keep the work clean. They also train you to start with context instead of chaos.

Step 15: Run the First Project Test

Now you test the setup. Do not start with your biggest task. Start by asking Claude to explain the project back to you.

Paste this into your new Claude Project:

Read the project knowledge.

Tell me:
1. What this project is for
2. Who it serves
3. What kind of outputs you should create
4. What voice and tone you should use
5. What you should avoid
6. What files seem most important
7. What context is missing
8. What you need from me before we start real work

This test is gold. If Claude misunderstands the project, your files are not clear enough. Fix the files before you ask it to do important work.

Do not blame Claude for bad context. Clean the kitchen before cooking.

Step 16: Add a Decisions Log

A decisions log keeps your project from drifting. Every time you make an important decision, save it.

Create decisions-log.md:

# Decisions Log

## Decision 1
Date:
Decision:
Why we decided this:
What this affects:
What Claude should remember:

This is especially useful for newsletters, product launches, client work, courses, and strategy projects. The decisions log stops you from re-litigating the same thing over and over.

It also helps Claude understand where the project is going.

Step 17: Add a Source Index

Claude can handle files, but you should still make the source material easy to navigate. Create source-index.md.

# Source Index

## Core Files
- project-brief.md: Overview of the project.
- voice-guide.md: Voice and style rules.
- audience.md: Audience details.
- goals.md: Current goals.

## Research Files
- [file name]: [what it contains]
- [file name]: [what it contains]

## Examples
- examples-i-love.md: Strong examples to follow.
- examples-i-hate.md: Weak examples to avoid.

## Notes
Use this file to understand where context lives before searching project knowledge.

This seems boring until it saves you 30 minutes. Boring systems make creative work easier. We love that.

Step 18: Use RAG Without Treating It Like a Trash Can

Claude’s paid plans can use Retrieval Augmented Generation, or RAG, when project knowledge gets large. Claude says RAG lets Projects store up to 10x more content by retrieving the most relevant information from uploaded documents instead of loading everything into memory at once. It activates automatically when needed.

That is powerful, but it is not permission to upload 600 messy files and call it strategy. The better move is to keep your project knowledge clean, named, and organized. Upload comprehensive content, but make it useful. Claude’s own RAG best practices say to upload relevant content upfront, use clear filenames, group related documents together, and reference specific documents by name when needed.

The more you care about the input, the better the output gets. Shocking. Annoying. True.

Step 19: Create a Skill When the Workflow Repeats

Projects hold context. Skills teach Claude how to perform repeat workflows.

Claude describes Skills as folders of instructions, scripts, and resources that Claude loads when relevant to a task. Skills are designed for repeatable tasks, like creating documents with brand guidelines, analyzing data through a specific workflow, or automating personal processes.

You do not need skills on day one. Start with project files. Once you notice a workflow happening again and again, turn it into a skill.

A good skill should solve one specific repeatable task, include clear instructions, define when it should be used, and include examples when helpful. Claude’s custom skill guide says every skill needs a folder with at least a skill.md file, including required name and description metadata.

Example skill structure:

academy-article-editor-skill/
  skill.md
  examples/
    strong-intro.md
    weak-intro.md
  checklists/
    seo-checklist.md
    voice-checklist.md

A simple skill.md could look like this:

---
name: Academy Article Editor
description: Use this skill when editing Academy of AI articles for voice, clarity, SEO, usefulness, and originality.
---

# Academy Article Editor

When editing an article, check for:

1. Clear reader promise
2. Strong Academy of AI voice
3. Human paragraph flow
4. No generic AI phrasing
5. SEO title, description, URL slug, social title, social description, Substack title, subtitle, and tags
6. Useful examples
7. Practical next step
8. Strong ending

Do not rewrite everything unless asked. First identify what needs to change.

Claude lets you upload custom skills as ZIP files through Customize > Skills, then toggle them on or off.

Step 20: Use Cowork for Projects That Need File Work

Claude Projects in the web app are great for context and focused chats. Claude Cowork is for heavier work that needs local files, longer tasks, and finished deliverables.

Claude says Cowork is available on paid plans through Claude Desktop for macOS and Windows. It brings Claude Code’s agentic capabilities to knowledge work, so Claude can take on complex multi-step tasks and produce finished work like formatted documents, organized files, synthesized research, spreadsheets, and presentations.

Cowork can read from and write to local files you choose, run code and shell commands in an isolated virtual machine, coordinate subtasks, and deliver outputs to your file system. That power comes with risk, because Claude can make real changes to your files.

Use Cowork when you want Claude to work with a local project folder. Use normal Projects when you want a persistent AI workspace for chats and uploaded knowledge.

Here is the Cowork version of the project structure:

PROJECT-NAME/
  INSTRUCTIONS.md
  ABOUT-ME/
    about-me.md
    voice-guide.md
    audience.md
  INPUTS/
    source-documents/
    research/
    examples/
  WORKFLOWS/
    workflow-index.md
    checklists/
    recurring-prompts.md
  OUTPUTS/
    drafts/
    final/
    exports/
  ARCHIVE/
    old-versions/

Cowork also supports global instructions and folder instructions. Global instructions apply to every Cowork session, while folder instructions add project-specific context when you select a local folder.

That is the exact setup I would use for serious projects.

Step 21: Add Safety Rules Before You Give Claude Power

The more Claude can do, the more careful you need to be. This is not fear. This is adulthood.

Add safety rules to your project instructions:

# Safety Rules

Claude must ask before:
- Deleting files
- Sending messages
- Publishing content
- Editing source documents
- Making purchases
- Changing account settings
- Sharing private information
- Using sensitive personal or client data
- Taking action outside the chat

Claude should flag:
- Unsupported claims
- Privacy risks
- Legal or financial uncertainty
- Brand trust issues
- Anything that requires human approval

Claude’s connector docs also explain that owners on Team and Enterprise plans can restrict connected services to read-only actions, such as allowing Claude to search email but not send messages, or read Drive files but not create or edit documents.

Use those restrictions when you can. The best AI workflow is powerful and boringly safe.

Step 22: Use the Right Claude Feature for the Job

A lot of people get confused because Claude now has Projects, Skills, Connectors, Artifacts, file creation, Cowork, and more. Here is the simple version.

Use Projects when you need a focused workspace with persistent context. Use Project Knowledge when Claude needs files across multiple chats. Use Project Instructions when Claude needs project-specific rules. Use Skills when a repeat workflow should work across Claude, not just inside one project. Use Connectors when Claude needs access to outside tools like Google Drive, Gmail, Calendar, Slack, Linear, or GitHub. Use Artifacts when Claude is creating something substantial you want to view, edit, or reuse separately from the chat. Claude describes Artifacts as standalone content shown in a dedicated window, useful for things you may want to modify, build on, or reference later.

This is the easiest way to remember it:

Projects = the room
Files = the memory
Instructions = the rules
Skills = the repeat workflow
Connectors = the outside tools
Artifacts = the thing you are building
Cowork = the agent that can work on files and tasks

That is the stack. Once you see it that way, Claude gets much easier.

Step 23: Keep Project Files Small Enough to Stay Useful

Claude can handle a lot, especially with RAG on paid plans, but more context is not always better. More context can mean more noise.

Keep your core files short, direct, and useful. Your about-me.md does not need to become your memoir. Your voice-guide.md does not need every post you have ever written. Your examples-i-love.md should include the strongest examples, not 94 decent ones.

Claude’s usage docs note that message length, file attachment size, conversation length, tool usage, model choice, effort level, and artifact creation can affect usage limits. They also note that content in projects is cached and does not count against limits when reused, which is another reason reusable project context is smart.

Clean context saves time, usage, and sanity. A blessing.

Step 24: Maintain the Project Weekly

A Claude Project is not something you set up once and abandon. Treat it like a living workspace.

Once a week, update the files. Add new decisions. Remove outdated context. Add better examples. Move final outputs into the output log. Update goals. Add new audience language. Capture new customer objections. Delete files that no longer matter.

Use this weekly maintenance prompt:

Review this project knowledge and help me improve the setup.

Tell me:
1. Which files seem outdated
2. What context is missing
3. What files are too vague
4. What examples should be added
5. What instructions should be clearer
6. What workflow should become a skill
7. What I should update before using this project again

This is how your Claude Project gets better over time. Not through magic. Through maintenance.

Starter File Structures by Project Type

A universal structure is great, but some projects need specific files. Here are a few ready-to-steal setups.

Newsletter or Substack Project

NEWSLETTER-PROJECT/
  00_START_HERE/
    project-brief.md
    project-instructions.md

  01_CONTEXT/
    about-me.md
    audience.md
    publication-positioning.md
    content-pillars.md
    subscriber-goals.md

  02_VOICE_AND_STANDARDS/
    voice-guide.md
    seo-rules.md
    headline-style.md
    examples-i-love.md
    examples-i-hate.md

  03_SOURCE_MATERIAL/
    article-ideas.md
    reader-comments.md
    research-notes.md
    source-index.md

  04_WORKFLOWS/
    article-workflow.md
    headline-workflow.md
    editing-checklist.md
    seo-checklist.md
    social-caption-workflow.md

  05_OUTPUTS/
    drafts.md
    published-posts.md
    best-performing-posts.md

This is what I would use for Academy of AI.

Digital Product Project

DIGITAL-PRODUCT-PROJECT/
  00_START_HERE/
    product-brief.md
    project-instructions.md

  01_CONTEXT/
    audience.md
    problem.md
    transformation.md
    offer.md
    pricing.md

  02_STANDARDS/
    brand-voice.md
    product-quality-bar.md
    examples-i-love.md
    examples-i-hate.md

  03_SOURCE_MATERIAL/
    customer-research.md
    competitor-notes.md
    testimonials.md
    objections.md

  04_WORKFLOWS/
    product-outline-workflow.md
    lesson-writing-workflow.md
    sales-page-workflow.md
    launch-workflow.md

  05_OUTPUTS/
    product-drafts.md
    sales-assets.md
    launch-emails.md

Use this when you are building templates, courses, guides, prompt packs, Notion systems, or paid resources.

Client Project

CLIENT-PROJECT/
  00_START_HERE/
    client-brief.md
    project-instructions.md
    scope.md

  01_CONTEXT/
    client-overview.md
    audience.md
    goals.md
    constraints.md
    stakeholders.md

  02_BRAND/
    brand-voice.md
    brand-rules.md
    examples-approved.md
    examples-rejected.md

  03_SOURCE_MATERIAL/
    meeting-notes.md
    client-feedback.md
    research.md
    assets-index.md

  04_WORKFLOWS/
    deliverable-workflow.md
    review-checklist.md
    revision-process.md
    approval-process.md

  05_OUTPUTS/
    drafts.md
    final-deliverables.md
    decisions-log.md

This structure protects your client work from becoming scattered and messy.

Personal Productivity Project

PERSONAL-OS/
  00_START_HERE/
    personal-brief.md
    project-instructions.md

  01_CONTEXT/
    about-me.md
    goals.md
    values.md
    current-projects.md
    constraints.md

  02_SYSTEMS/
    weekly-review.md
    daily-planning.md
    decision-rules.md
    recurring-tasks.md

  03_REFERENCE/
    routines.md
    notes.md
    ideas.md

  04_WORKFLOWS/
    weekly-planning-prompt.md
    project-prioritization-prompt.md
    email-cleanup-prompt.md

  05_OUTPUTS/
    weekly-plans.md
    decisions-log.md
    completed-projects.md

This is for using Claude like a personal operating system, without letting it run your life like a weird little robot boss.

The Best First Prompt for Any New Claude Project

Once everything is set up, this is the first prompt I would use:

Read the project knowledge and project instructions.

Before doing any work, tell me:
1. What you understand this project is for
2. What files you used
3. What voice and standards you should follow
4. What outputs you are best equipped to help create
5. What context is missing
6. What questions you need answered before we begin

Then wait for my answers.

This prompt forces Claude to orient itself. It also shows you whether the setup works.

The Everyday Prompt for Using the Project

After setup, use this prompt constantly:

Use the project knowledge for context.

I want to create:
[insert output]

Audience:
[insert audience]

Goal:
[insert goal]

Success criteria:
[insert what good looks like]

Before drafting, ask me any missing questions. Then create the outline first.

This keeps Claude from sprinting into the wrong task. Fast is only useful when the direction is right.

The Project Audit Prompt

Run this once a month:

Audit this Claude Project.

Tell me:
1. What is working well
2. What context is missing
3. What files should be added
4. What files should be removed or merged
5. What instructions are unclear
6. What repeat workflows should become skills
7. What I should update based on the outputs we have created
8. The 5 highest-impact improvements to make next

Your project should get smarter as you use it. If it does not, you are just hoarding files.

What This Means for You

A Claude Project is not just a place to keep chats. It is how you teach Claude your world.

The better your setup, the better the work. Your files become memory. Your examples become taste. Your project instructions become standards. Your workflows become leverage. Your skills become repeatable systems.

This is how you stop using Claude like a random chatbot and start using it like an actual work partner.

Not because Claude is magic. Because you gave it the right room, the right rules, and the right context.

That is the whole move.

Your First Assignment

Create one Claude Project today. Not five. One.

Pick the project that would save you the most time or make your work noticeably better this week. Create the local folder. Add the starter files. Upload them to Project Knowledge. Add project instructions. Run the first project test.

Use this prompt to begin:

Help me set up a Claude Project for [project name].

Ask me 10 questions about the project, audience, goals, voice, standards, source material, workflows, constraints, and outputs.

After I answer, create:
1. A recommended file structure
2. The content for project-brief.md
3. The content for project-instructions.md
4. A list of files I should create next
5. The first prompt I should use after uploading everything

Do that once, and Claude gets better forever inside that project.

That is not a small upgrade.

That is your AI operating system.

Subscribe to Academy of AI

Academy of AI helps everyday people learn the tools already changing work, money, creativity, and freedom. No panic, no jargon, and no gatekeeping.

Just practical AI education for people who want to use these tools with clarity, confidence, and power.

Subscribe to Academy of AI if you want to stop dabbling with AI and start building real leverage.

Most people use Claude like a chatbot. That’s a mistake.

Most people use Claude like a prettier search bar. They open a chat, ask one question, get one answer, and then wonder why AI still feels slightly underwhelming.

That is not Claude’s fault. That is like buying a full commercial kitchen and only using the toaster. Cute, but we can do better.

Claude is not just a place to ask questions. It can help you think, write, research, code, build documents, make spreadsheets, create decks, test ideas, organize work, automate repeat tasks, connect to tools, and turn your messy brain into a cleaner system.

The trick is knowing which version of Claude you need for the job. Sometimes you need a fast assistant. Sometimes you need a deep thinker. Sometimes you need a researcher, coder, designer, spreadsheet analyst, or project manager.

That is the whole point of this guide.

Claude has grown way beyond basic chat. Anthropic now documents features like Projects, Artifacts, Web Search, Research, Skills, Connectors, Plugins, Claude Cowork, Claude Code, Claude for Excel, Claude for PowerPoint, Claude Design, and more. Some features depend on your plan, workspace, and beta access, so always check what is available inside your own Claude account before building a workflow around it.

Model names also change fast, which is why I do not want you obsessing over one perfect model forever. As of this writing, Anthropic lists Claude Opus 4.8 for coding, agentic tasks, and professional work, while Claude Sonnet 4.6 is positioned for coding, computer use, long-context reasoning, agent planning, knowledge work, and design. Translation: use the strongest model for serious thinking and the faster model for everyday work.

Let’s make Claude actually useful.

The Better Way to Think About Claude

Claude is not one tool. It is a stack of work modes.

There is Claude for thinking, where you use it to reason through decisions, explain ideas, and challenge your assumptions. There is Claude for making, where you use it to create documents, spreadsheets, presentations, prototypes, designs, code, and dashboards. There is Claude for connecting, where it pulls context from tools like email, calendars, drives, and other apps. Then there is Claude for remembering, where Projects, instructions, skills, and files help it understand how you work over time.

That is the upgrade. Stop asking, “What can Claude answer?” Start asking, “What kind of work do I need Claude to help me do?”

That one shift changes everything.

1. Use Claude as a Better Chat Partner

Basic chat is still useful, but only when you stop asking lazy questions. “Help me with marketing” is not a prompt. It is a cry for help in a trench coat.

Use Claude chat when you need to untangle an idea, draft something quickly, ask for suggestions, or talk through a problem. The key is to give it context, stakes, and a clear job.

Try this:

I want to think through this problem: [describe problem].

Ask me 5 questions first so you understand the context, goal, constraints, and what I have already tried.

After I answer, help me find the clearest next step.

This makes Claude interview you before it answers. That matters because most bad AI output happens because the tool guessed instead of asking.

2. Use Claude as a Deep Thinker

Sometimes you do not need speed. You need better thinking.

Use Claude’s strongest available model when the task involves strategy, judgment, complex tradeoffs, hard decisions, long documents, or anything where a shallow answer could cost you. This is where Claude can feel less like a chatbot and more like a thinking partner.

Try this:

Think through this carefully before answering.

I am deciding between: [option A] and [option B].

My goal is: [goal].
My constraints are: [constraints].
The stakes are: [stakes].

Compare the options, explain the tradeoffs, identify hidden risks, and give me a clear recommendation.

This is not for “write a caption.” This is for real decisions. Use the big brain when the work deserves it.

3. Use Claude as a Fast Assistant

Not every task needs deep reasoning. Sometimes you need a quick rewrite, summary, checklist, outline, or answer.

For that, use the faster model available in Claude. Save the heavy model for harder work. This keeps your workflow moving and helps you avoid burning premium capacity on tiny tasks.

Try this:

Answer quickly and practically.

Task: [insert task]

Constraints:
- Keep it under 150 words
- No preamble
- No generic advice
- Give me the usable version first

This is great for emails, captions, quick summaries, simple lists, and “I need this cleaned up now” moments.

4. Use Claude for Careful Reasoning

Extended thinking is for problems where Claude needs more room to reason before responding. Anthropic describes extended thinking as giving Claude enhanced reasoning capabilities for complex tasks, with varying transparency into the reasoning process before the final answer.

Use this for business decisions, technical planning, finance scenarios, market analysis, strategy, and any question with multiple moving parts.

Try this:

Use careful reasoning for this.

Problem: [describe problem]

Before recommending anything, identify:
1. What we know
2. What we are assuming
3. What is uncertain
4. What could go wrong
5. What decision I need to make

Then give me the best recommendation based on the current information.

Do not ask Claude to be dramatic. Ask it to be careful. Different energy, much better results.

5. Use Claude Cowork for Real Work, Not Just Replies

Claude Cowork is where Claude starts feeling less like a chat tool and more like a work partner. Anthropic says Cowork can take an outcome, step away from chat, and come back with finished work like formatted documents, organized files, synthesized research, spreadsheets, presentations, and long-running tasks.

Use Cowork when the task has multiple steps, files, research, formatting, or deliverables. Do not use it for tiny one-off prompts. That is not the point.

Try this:

I want you to help me complete this work product: [describe final deliverable].

The final result should include: [list deliverables].

Use the files and context I provide. Create a plan first, ask me any missing questions, then complete the work in stages so I can review each major decision.

Cowork is powerful, but be careful with sensitive files. Agentic tools can make real changes, so keep your guardrails tight.

6. Use Claude Code to Build and Fix Things

Claude Code is for people building software, websites, automations, internal tools, scripts, and technical systems. Anthropic’s Agent SDK documentation says it can power agents that read files, run commands, search the web, edit code, and use the same tool loop behind Claude Code.

You do not need to be a senior developer to benefit from this. You do need enough judgment to review what it changes. AI coding without review is how bugs get dressed up as progress.

Try this:

Review this codebase or file and help me improve it.

Goal: [what I want the code to do]
Current issue: [bug, feature, error, or improvement]
Constraints: [language, framework, style, dependencies]

First explain what you think is happening. Then propose the smallest safe change. Do not rewrite more than necessary.

This is how you use Claude Code responsibly. Small changes. Clear goals. Review everything.

7. Use Claude for Excel and Data Modeling

Claude can now work with files and create documents like Excel spreadsheets, PowerPoint presentations, Word documents, and PDFs directly in conversations, according to Anthropic’s file creation documentation.

This is huge for entrepreneurs, operators, creators, and anyone who quietly fears spreadsheets. Claude can help build models, clean data, summarize trends, create formulas, and make your numbers less rude.

Try this:

Help me build a spreadsheet model for: [goal].

I need it to include:
- Input assumptions
- Revenue or cost calculations
- Scenario tabs
- Clear formulas
- A summary dashboard

Ask me for the numbers you need before creating the model.

Use Claude for structure, formulas, and scenario thinking. Then check the math. Always check the math.

8. Use Claude for Slides and Presentations

Claude can help you turn ideas into presentations, not just write random bullets. This is especially useful for pitch decks, workshops, team updates, sales calls, webinars, course lessons, and executive summaries.

The mistake is asking for “a deck.” That gets you generic slides. Instead, tell Claude the audience, purpose, decision, emotional arc, and what the deck needs to make people believe.

Try this:

Help me create a presentation about: [topic].

Audience: [who will see it]
Goal: [what I want them to understand, decide, or do]
Tone: [clear, persuasive, premium, educational, etc.]
Length: [number of slides]

Create a slide-by-slide outline with the purpose of each slide, suggested title, key points, visual idea, and speaker notes.

Slides are not decoration. Slides are persuasion with structure.

9. Use Claude Design for Mockups and Visual Work

Claude Design lets users collaborate with Claude to create polished visual work like designs, prototypes, slides, one-pagers, and more. Anthropic says it can help with realistic prototypes, product wireframes, pitch decks, marketing collateral, and design explorations.

Use this when you need to make an idea visible. A rough mockup can save weeks of vague conversation. People understand faster when they can see the thing.

Try this:

Create a visual mockup for: [product, landing page, app screen, deck, one-pager, etc.].

Audience: [who it is for]
Goal: [what it should communicate]
Brand style: [describe colors, typography, vibe, examples]
Must include: [sections or components]
Avoid: [anything off-brand]

Start with 3 visual directions before building the final version.

This is perfect for founders, marketers, designers, and creators who need to move from idea to visible concept fast.

10. Use Claude in Chrome to Browse With You

Claude in Chrome is a browser extension that lets Claude read, click, and navigate websites alongside you in the side panel while you browse. Anthropic says it is available in beta for paid plans and carries safety risks because Claude can interact with websites on your behalf.

Use it for research, comparison shopping, website audits, product testing, competitor analysis, form review, and guided browsing. Do not use it casually on sensitive accounts without thinking.

Try this:

Look at the page I am viewing and help me analyze it.

Goal: [audit, summarize, compare, extract key details, check usability, etc.]

Tell me:
1. What this page is trying to do
2. What is clear
3. What is confusing
4. What I should click or check next
5. Any red flags I should notice

Browser AI is powerful. Treat it like giving an assistant access to your screen, because that is basically what it is.

11. Use Computer Use for Controlled Tasks

Claude’s computer use tool can interact with computer environments through screenshots, mouse control, keyboard control, and desktop automation. Anthropic also notes that computer use is beta and comes with distinct risks, especially when interacting with the internet.

This is not where you start. This is where you go after you understand the task, the permissions, and the risk.

Try this:

Help me complete this computer task safely: [describe task].

Before taking any action, create a step-by-step plan. Ask for confirmation before anything involving purchases, account changes, messages, sensitive data, downloads, or external submissions.

After each major step, tell me what you did and what you need next.

The magic word here is confirmation. Never let an agent freestyle with your accounts.

12. Use Claude to Delegate Bounded Work

The real upgrade is not “Claude answered me.” The upgrade is “Claude completed a bounded outcome.”

A bounded task has a clear finish line. Examples: organize this folder, summarize these documents, draft this report, compare these vendors, create this spreadsheet, prepare this meeting brief, or build this tracker.

Try this:

I want to delegate this bounded task: [describe task].

Final output should be: [document, spreadsheet, report, checklist, presentation, etc.]
Success criteria: [what done means]
Sources to use: [files, links, notes, folders]
Restrictions: [what not to touch, change, assume, or include]

Create a plan first. Then complete the task in stages.

Claude performs better when “done” means something specific. Otherwise, you get a beautiful pile of almost-helpful.

13. Use Claude Web Search for Current Information

Web Search gives Claude access to real-time web content beyond its knowledge cutoff, and Anthropic says responses include citations for sources drawn from search results.

Use this for current events, product updates, prices, policies, travel details, laws, market research, software changes, and anything that may have changed recently.

Try this:

Use web search to answer this with current sources: [question].

Requirements:
- Use primary or official sources when possible
- Cite every important claim
- Separate confirmed facts from interpretation
- Tell me what is still uncertain

Do not use old AI memory for current facts. That is how people publish nonsense with confidence.

14. Use Claude Research for Deep Investigation

Research mode is for bigger questions that need more than one search result. Use it for market maps, competitive analysis, buyer research, policy reviews, industry scans, and deep content briefs.

The key is to ask for synthesis, not a pile of links. You want Claude to tell you what the sources mean together.

Try this:

Research this topic deeply: [topic].

I need a decision-ready brief, not a link dump.

Include:
1. The main findings
2. Important sources
3. Points of disagreement
4. What is changing
5. Risks or unknowns
6. My best next move

Research should make you smarter. It should not just make your tab count more dramatic.

15. Use Skills for Repeat Workflows

Claude Skills let you customize Claude with specialized knowledge and repeatable workflows. Anthropic says custom skills can be simple instructions or complex multi-file packages, and the best skills solve one specific repeatable task with clear instructions, examples, and defined use cases.

Use Skills for things you do often: newsletter editing, brand voice rewriting, customer support replies, meeting summaries, campaign briefs, sales call analysis, SEO drafts, course lesson creation, or financial reporting.

Try this:

Help me design a Claude Skill for this repeat workflow: [workflow].

The skill should:
- Know when to activate
- Follow my style and standards
- Use these examples: [paste examples]
- Avoid these mistakes: [list mistakes]
- Produce this format every time: [format]

Create the skill instructions and a test prompt.

A prompt helps once. A skill helps every time.

16. Use Plugins to Bundle Workflows

Plugins can bundle skills, connectors, and sub-agents into a ready-to-use setup. Anthropic says plugins are available to paid plans and can connect Claude to services like Google Drive, Gmail, Slack, DocuSign, and more.

Use plugins when a workflow needs multiple pieces working together. This is especially useful for sales, finance, legal, marketing, HR, engineering, design, operations, and data analysis.

Try this:

I want to build a plugin-style workflow for: [business function].

It should include:
- The skills Claude needs
- The connectors it should use
- The steps it should follow
- What requires human approval
- The final output format

Design the workflow before recommending tools.

Do not install random plugins just because they sound fancy. Start with the workflow. Then choose the tools.

17. Use Projects So Claude Knows the Job

Projects are where Claude becomes more useful over time. Anthropic says project instructions help Claude understand the specific context and requirements for a particular project, and they are useful when you need consistent context across multiple conversations.

Create a Project for each major area of your life or business. Examples: Academy of AI, sales pages, course creation, personal finance, client work, Substack strategy, travel planning, or product development.

Try this:

Help me set up a Claude Project for: [project name].

Tell me:
1. What instructions to add
2. What files to upload
3. What examples Claude should study
4. What outputs I will create often
5. What rules Claude should follow every time

This is how you stop re-explaining yourself. Your context should not live only in your head.

18. Use Scheduled Tasks for Recurring Work

Claude Cowork includes scheduled tasks, which Anthropic describes as tasks Claude can complete automatically on a cadence you choose. Cowork can also organize related work into persistent projects with files, links, instructions, and memory.

Use scheduled tasks for weekly reports, content briefs, competitor monitoring, inbox summaries, recurring research, client updates, or morning planning.

Try this:

Create a recurring task for: [task].

Cadence: [daily, weekly, monthly]
Sources to check: [files, apps, links, folders]
Final output: [brief, dashboard, checklist, email draft, etc.]
Approval needed before: [sending, editing files, sharing, making changes]

Write the exact task instructions Claude should follow each time.

Recurring tasks are where AI starts saving real time. Not once. Every week.

19. Use Connectors to Pull From Your Actual Tools

Connectors let Claude work with your real tools and data sources. For example, Anthropic says Google Workspace connectors can connect Gmail, Google Calendar, and Google Drive so Claude can search emails, manage calendar work, retrieve Drive files, read docs, and create folders without leaving the conversation.

This matters because AI is only as good as the context it can access. A generic answer is fine. An answer based on your actual files, calendar, docs, and email is much better.

Try this:

Use my connected tools to help me prepare for: [meeting, launch, trip, project, etc.].

Please find:
- Relevant emails
- Calendar details
- Related documents
- Open questions
- Next actions

Do not send, delete, change, or share anything without asking me first.

Connectors are powerful, but permission matters. Keep the approval step.

20. Use Artifacts for Things You Want to Keep

Artifacts are for substantial work that stands alone. Anthropic says artifacts let you turn ideas into shareable apps, tools, or content, and they appear in a dedicated window separate from the main conversation so you can edit, reuse, or reference them later.

Use artifacts for calculators, dashboards, checklists, landing pages, mini apps, diagrams, lesson plans, templates, and anything you might want to revisit.

Try this:

Create this as an artifact: [describe artifact].

Purpose: [what it helps me do]
Audience: [who will use it]
Must include: [features or sections]
Style: [simple, visual, branded, interactive, etc.]

Make it something I can edit and reuse later.

Chats disappear into the scroll. Artifacts become assets.

21. Use Claude to Match Your Voice

Claude can write well, but that does not mean it writes like you. Without voice context, AI tends to slide into polished, generic, slightly dead internet language.

Claude’s personalization features include profile instructions, project instructions, and skills that can adjust tone, format, communication patterns, and specialized behaviors. Anthropic also notes that styles are moving into skills, which makes voice and workflow customization even more system-based.

Try this:

Study my writing style from these samples.

Analyze:
- Sentence length
- Rhythm
- Tone
- Humor
- Vocabulary
- Paragraph structure
- What I avoid
- What makes the writing sound like me

Then create a voice guide Claude can follow for future drafts.

Samples:
[paste samples]

Your voice is not a garnish. Your voice is the brand.

22. Use Team Projects to Share Context

Team Projects help groups work from shared context. This matters because most team AI failures come from everyone prompting differently, using different files, and silently creating chaos.

Anthropic says project visibility and sharing features are available on Team and Enterprise plans, with options for public projects inside an organization or private projects for invited members.

Try this:

Help me create a shared team project for: [team workflow].

The team needs consistent context about:
- Brand standards
- Customer information
- Approved examples
- Templates
- Rules
- Review process

Create the project instructions and a simple onboarding note for team members.

This is how teams stop treating AI like random side quests.

23. Use Global Instructions as Guardrails

Global instructions are your default rules. Use them to tell Claude how you want answers, what to avoid, what tone to use, and when to ask questions first.

This is where you ban the annoying stuff. No corporate voice. No fake certainty. No filler. No “great question.” No generic advice. No over explaining unless asked.

Try this:

Help me write account-wide instructions for Claude.

I want Claude to:
- Be direct and useful
- Ask questions before complex tasks
- Avoid generic advice
- Use my preferred tone
- Flag uncertainty
- Never overpromise
- Keep outputs practical

Write this as instructions Claude can follow in every conversation.

Guardrails save time. They also protect your taste.

24. Use Claude With a Knowledge Vault

Your best AI results will come from your best context. That means you need a place to store your voice, goals, offers, frameworks, customers, examples, brand rules, and repeat workflows.

This can live in Obsidian, Notion, Google Drive, Claude Projects, or a folder of markdown files. The tool matters less than the habit. Your expertise needs to become reusable.

Try this folder structure:

ABOUT-ME/
- about-me.md
- brand-voice.md
- goals.md
- audience.md

EXAMPLES/
- examples-i-love.md
- examples-i-hate.md
- best-performing-content.md

BUSINESS/
- offers.md
- customer-objections.md
- pricing.md
- product-notes.md

WORKFLOWS/
- newsletter-workflow.md
- sales-page-workflow.md
- research-workflow.md

Claude cannot use the wisdom you never capture. Get it out of your head.

25. Use an About-Me File So Claude Understands You

This is the most underrated move in the whole list. Create one file that explains who you are, what you do, who you help, what you care about, how you communicate, and what kind of output you want.

This file becomes your AI operating manual. Every serious Project should have one.

Try this:

Help me create an about-me file for Claude.

Ask me questions about:
- Who I am
- What I do
- My audience
- My goals
- My voice
- My offers
- My standards
- What I hate in AI output
- What good work looks like to me

After I answer, turn it into a clean markdown file I can reuse in Claude Projects.

This is how Claude stops sounding generic. You have to teach it what “good” means to you.

The 5 Claude Workflows I Would Start With

Do not try all 25 today. That is how people turn AI into productivity cosplay. Pick the workflows that solve your actual problems right now.

Start with Projects, because reusable context changes everything. Then create your About-Me file so Claude understands your voice and goals. After that, build one Skill for a repeat workflow, create one Artifact you can reuse, and connect one tool that gives Claude better context.

That is enough to change your week.

A strong starter stack looks like this:

1. Create one Claude Project
2. Add an about-me file
3. Add your voice guide
4. Build one reusable prompt or Skill
5. Create one Artifact you can use again

This is not about trying every shiny feature. It is about building an AI setup that actually fits your life.

The Biggest Mistake People Make With Claude

The biggest mistake is using Claude once and expecting magic.

Claude gets better when you give it context, examples, goals, constraints, and feedback. It gets better when you save what works. It gets better when you build Projects, Skills, instructions, and files around your actual work.

Most people keep starting from zero. That is the expensive way to use AI.

Do not start from zero every time. Build your system once, then improve it every week.

Your First Assignment

Open Claude and paste this:

Help me build my personal Claude operating system.

Ask me 10 questions about my work, goals, audience, voice, tools, repeat tasks, files, and current bottlenecks.

After I answer, recommend:
1. The first 3 Claude features I should use
2. The Projects I should create
3. The files I should upload
4. The repeat workflows I should turn into Skills
5. The first Artifact I should build
6. A 7-day setup plan

Run that prompt today. Not because you need to master every Claude feature overnight, but because you deserve better than using AI like a fancy blank box.

The Bottom Line

Claude can chat, think, write, research, code, design, model, browse, connect, organize, automate, and create reusable assets. But the tool does not matter if your workflow is messy.

The goal is not to use every feature. The goal is to build a system that helps you work smarter, create faster, and keep your brain focused on the things only you can do.

Use Claude for speed, but do not give up judgment. Use it for output, but keep your taste. Use it for automation, but keep your standards. Use it for research, but verify what matters.

That is how you use Claude like a powerful person.

Not as a chatbot.

As a whole damn team.

Subscribe to Academy of AI

Academy of AI helps everyday people learn the tools already changing work, money, creativity, and freedom. No panic, no jargon, and no gatekeeping.

Just practical AI education for people who want to use these tools with clarity, confidence, and power.

Subscribe to Academy of AI if you want to stop dabbling with AI and start building real leverage.

I use ChatGPT every day. I use it to write, plan, brainstorm, organize ideas, build systems, test angles, clean up messy thoughts, and move faster when my brain has too many tabs open. I love it. I also think a lot of people are using it in a way that quietly makes them weaker.

Not because ChatGPT is evil. Not because AI is rotting everyone’s brain. Not because we all need to throw our laptops into a lake and start journaling by candlelight like dramatic little Victorian ghosts.

The problem is simpler than that. A lot of people are letting ChatGPT think before they do.

That is where things get messy. When you open ChatGPT before you have even tried to form your own thought, the tool does not just help you. It starts steering. It gives you the structure, the language, the argument, the examples, and the ending before your brain has done any real work.

Then you edit what it gave you and call it collaboration.

Sometimes that is fine. Sometimes you just need a quick email or a cleaner grocery list. But if you do that for important work over and over again, you start skipping the part where your own thinking gets stronger.

That is the real risk.

Not AI.

Skipping the reps.

The Problem Is Not ChatGPT. The Problem Is Autopilot.

Let’s use a gym example because it makes this painfully obvious. Imagine you hire a trainer, but every time you show up, the trainer lifts the weights for you. You still go to the gym. You still watch the workout. You still feel involved. But your body is not doing the hard part.

That is how a lot of people use ChatGPT.

They ask it to write the draft before they know what they think. They ask it to summarize the book before they try to understand the chapter. They ask it to build the strategy before they define the problem. They ask it to explain the meeting before they sit with what actually happened.

The output appears, so it feels productive. But your brain did not have to push.

That is what people mean when they talk about “cognitive debt.” You get the answer now, but you may not really own it later. You have the paragraph, but not the memory. You have the plan, but not the judgment. You have the polished version, but not the thinking underneath it.

That is not leverage. That is borrowing.

And eventually, the bill shows up.

The Study Everyone Is Talking About

A 2025 preprint called Your Brain on ChatGPT looked at how people wrote essays with different kinds of support. The researchers had 54 participants write SAT-style essays across three groups: one used an AI assistant, one used search engines, and one wrote without tools. The study used EEG to look at brain connectivity during writing, and it found that the brain-only group showed the strongest brain-network engagement, the search group landed in the middle, and the AI group showed the weakest connectivity. The AI group also reported the lowest sense of ownership over their essays and had more trouble quoting their own work afterward. (arXiv)

That is a big deal, but I want to be careful here. This does not prove that ChatGPT makes everyone dumb. It was one study, with one kind of task, in a controlled setting. Essay writing in a study is not the same thing as running a business, building a course, editing a newsletter, coding a product, or planning your week.

But the warning is useful. If you let AI do the thinking first, your brain may stay less engaged. That should not scare us away from AI. It should teach us to use it better.

The order matters.

Think first. Then use AI.

That one change can completely shift the relationship.

AI Can Also Make You Better

Here is where the conversation gets more interesting. AI is not only a risk. Used well, it can make people faster and better.

In a field experiment with 758 consultants at Boston Consulting Group, researchers found that GPT-4 helped consultants complete more tasks, work faster, and produce higher-quality results on tasks that fit within the model’s strengths. But the same research also found that when consultants used AI for a task outside the model’s strengths, they performed worse than people who did not use AI. BCG described this as the “jagged frontier,” meaning AI is great at some things and unreliable at others. (SSRN)

That is the whole lesson. AI can make you better when you know where it helps. AI can make you worse when you trust it in places where you cannot judge the answer.

Developers have seen the upside too. A controlled study on GitHub Copilot found that developers with access to the AI pair programmer completed a coding task 55.8% faster than the control group. (arXiv) Creative work has the same tension. Research on AI-assisted story writing found that AI ideas could improve ratings for creativity and enjoyment, especially for less experienced writers, but AI-assisted stories also became more similar to each other. (arXiv)

So no, the takeaway is not “AI bad.”

The takeaway is this: AI can make strong thinkers stronger, and it can help weak thinking look polished before it is ready.

That is the line we need to watch.

My Rule: Do the First Messy Version Yourself

This is the rule I want you to steal.

Do the first messy version yourself.

Before you ask ChatGPT to write the article, write the ugly outline. Before you ask it to build the strategy, write what you think the problem is. Before you ask it to summarize a topic, explain what you already understand. Before you ask it to create the sales page, write the rough offer in your own words.

It does not need to be good. Actually, it probably should not be good. The first version is allowed to be awkward, uneven, dramatic, unfinished, and full of half-formed thoughts. That is the point.

That messy first version proves your brain showed up.

Once you have your own thinking on the page, ChatGPT becomes way more useful. Now it has something to respond to. It can help you find what is unclear, what is missing, what is repetitive, what is strong, what needs evidence, and what should be cut.

That is very different from asking it to create the whole thing from zero.

One makes AI your assistant.

The other makes AI the driver.

I want you driving.

Start With Ten Minutes of Your Own Thinking

Before opening ChatGPT, give yourself ten minutes. Set a timer. Write what you think. Do not edit. Do not make it cute. Do not worry about grammar, structure, or whether the idea is “good enough” yet.

Just get your thoughts out of your head.

This works for almost anything. An article. A pitch. A hard email. A business idea. A lesson plan. A launch. A personal decision. A product outline. A meeting recap.

Once the timer ends, then bring in ChatGPT and say:

I wrote this rough version before asking for help.

Please read it and tell me:
1. What my main point seems to be
2. What feels strongest
3. What feels unclear
4. What I am repeating
5. What questions I need to answer before improving it

Do not rewrite it yet.
Here is my draft:
[paste draft]

That last line matters. “Do not rewrite it yet.”

You are not ready for polish. You need clarity first.

Ask ChatGPT to Push Back

Most people use ChatGPT like a very agreeable assistant. That can be helpful, but sometimes it is too soft. If your idea is weak, you do not need a cheerleader. You need someone to tell you where it breaks.

This is one of the best ways to use AI. Make it challenge you before the real world does.

Paste your idea and ask:

I want you to challenge this idea before I spend more time on it.

Tell me:
1. What feels unclear
2. What assumptions I might be making
3. What a skeptical reader, buyer, or client would question
4. Where this could fail
5. What would make it stronger

Be direct, but useful.
Here is the idea:
[paste idea]

This is not about letting ChatGPT destroy your confidence. It is about making your idea stronger while it is still cheap to change.

That is the gift. It is much better to find the weak spot in a chat than after you publish, launch, pitch, or spend three weeks building the wrong thing.

Use ChatGPT to Find What You Missed

This is where AI gets really helpful. After you have your own draft or plan, ask ChatGPT to find the holes.

Not to take over. Not to rewrite everything. Just to help you see what you missed.

Maybe your article needs a better example. Maybe your sales page avoids the biggest buyer objection. Maybe your plan has a timing problem. Maybe your argument has a gap you did not notice because you were too close to it.

Use this prompt:

Review this and help me find what is missing.

Look for:
1. Missing examples
2. Weak logic
3. Unanswered objections
4. Repetition
5. Claims that need proof
6. Places where the reader might get confused
7. Sections that should be cut or simplified

Do not rewrite the full piece. Give me a clear improvement list.
Here is the draft:
[paste draft]

This is how you use AI without disappearing into it. You keep ownership. ChatGPT helps you see the blind spots.

That is a healthy relationship with the tool.

Make Sure You Can Explain the Work Without Looking

This is the part most people skip.

After ChatGPT helps you create something, close the chat and explain the final idea out loud. Seriously. Say it like you are explaining it to a friend.

What is the main point? Why does it matter? What are the strongest examples? What is the conclusion? What would someone disagree with? What are you asking the reader, client, customer, or team to do next?

If you cannot explain it without looking, you do not fully own it yet.

That does not mean you did something wrong. It means you need one more pass.

Use ChatGPT to quiz you:

Quiz me on this work so I can make sure I actually understand it.

Ask me 7 short-answer questions about:
1. The main idea
2. The strongest argument
3. The weakest point
4. The key examples
5. The assumptions
6. The conclusion
7. The next action

Do not show me the answers until I respond.
Here is the work:
[paste final draft or summary]

This is especially useful if you are a student, creator, founder, teacher, or anyone using AI to publish or present ideas. If your name is on it, your brain should be in it.

Check the Logic Before You Trust the Answer

ChatGPT can sound confident when it is wrong. We know this. We have all seen it make something up with the energy of a man in a linen shirt explaining crypto at a pool party.

So when the answer matters, ask it to show you the assumptions.

You do not need a giant behind-the-scenes reasoning diary. You need the clean version: what is it assuming, what is uncertain, what needs checking, and where the answer might fail.

Use this:

Before I rely on this, help me inspect the logic.

Break it down into:
1. Main recommendation
2. Key assumptions
3. What information is missing
4. What could be wrong
5. What I should verify
6. A safer version of the recommendation

Here is the answer:
[paste answer]

Use this for anything involving money, health, legal issues, business strategy, research, data, travel, taxes, or public claims. Basically, anything where being wrong would be more than mildly annoying.

ChatGPT is great. Verification is still your job.

Make the Final Version Sound Like You

One of the biggest problems with AI writing is not that it is bad. It is that it can be aggressively fine.

Clean. Polished. Smooth. Empty. Like a hotel lobby with Wi-Fi.

That is not what we want.

If you are using ChatGPT to write, your final pass needs to bring you back into the work. Your voice. Your rhythm. Your taste. Your humor. Your opinions. Your lived experience. Your little human fingerprints.

The draft can get help. The final version needs you.

Use this prompt:

Review this draft and flag anything that does not sound like me.

Look for:
1. Generic AI phrasing
2. Corporate language
3. Sentences that are too polished
4. Predictable transitions
5. Places where my opinion should be stronger
6. Moments that need a more human example

Do not rewrite everything. Show me what to fix and suggest better options.
Here is the draft:
[paste draft]

Then read it out loud. If you would never say it to a friend, do not publish it.

That is the simplest voice test.

Use AI Where You Have Taste

Here is another rule I love.

Use AI first in areas where you already have taste.

If you know writing, use ChatGPT to help with drafts, hooks, edits, and repurposing. You will know what sounds good and what sounds fake. If you know sales, use it to test offers, objections, and email angles. You will know what feels persuasive and what feels desperate. If you know operations, use it to map workflows. You will spot missing steps fast.

But if you know nothing about the topic, slow down.

AI can still help you learn, but do not treat the first answer like the final answer. Ask for sources. Ask what beginners misunderstand. Ask what experts would disagree with. Ask what you need to verify before acting.

Use this prompt when you are new to something:

I am new to this topic, so do not assume I can judge your answer well.

Explain it simply. Tell me what beginners usually misunderstand. Flag anything that may be oversimplified. Tell me what I should verify before I act on this.

That prompt adds a little humility to the process.

We love humility. We love not publishing nonsense. Growth.

Do Not Let AI Make You Sound Like Everyone Else

AI has a sameness problem. That does not mean every AI-assisted piece sounds the same, but it can happen fast when people accept the first clean draft.

You know the vibe. Perfectly structured. Pleasantly generic. A little too balanced. A little too neat. No real edge. No real story. No weirdness. No risk.

That kind of writing is forgettable.

If you are a creator, entrepreneur, educator, or brand, your voice is not decoration. It is the asset. AI should help you say what you mean more clearly. It should not make you sound like the average of the internet.

This is why your own draft matters. Your stories matter. Your frustration matters. Your jokes matter. Your “I would never say that” instincts matter. That instinct is not a problem to correct. It is taste.

Protect it.

A Better Way to Use ChatGPT Every Day

Here is the simple workflow I would use.

Spend five to ten minutes thinking without AI. Write the messy version. Then ask ChatGPT to help you clarify, challenge, organize, or improve it. After that, revise the work yourself. Finally, explain the finished idea back in your own words so you know you actually understand it.

That is it.

It is not complicated. It just requires you to stop handing ChatGPT the first move.

Think of it like cooking with an incredible assistant. You choose the dish. You know who you are feeding. You decide what tastes good. ChatGPT can chop, prep, suggest, clean, and help you move faster.

But you still need to taste the food.

Do not serve something you did not taste.

What Students Should Do

If you are a student, please do not use ChatGPT to skip learning. I say that with love. The point of school is not just turning in documents. It is building the brain that can make sense of the world.

Use ChatGPT as a tutor, not a ghostwriter.

Try the problem first. Write the paragraph first. Explain the concept first. Then ask ChatGPT what you missed. Ask it to quiz you. Ask it to explain the part that still feels confusing. Ask it to give you practice questions and grade your answers.

Use this:

I need to learn this, not just finish it.

First, ask me what I already understand. Then explain what I am missing in plain English. After that, quiz me without showing the answers. If I get something wrong, explain it a different way and quiz me again.

That is how AI helps you get smarter.

Not by doing the assignment.

By helping you build the muscle.

What Creators Should Do

If you are a creator, use ChatGPT to speed up the parts that drain you, not erase the parts that make people care.

Let it help you brainstorm hooks, organize messy ideas, repurpose strong posts, test objections, and clean up structure. But do not let it flatten your voice. Do not let it remove the story. Do not let it polish the piece until there is no pulse left.

Your best work probably has a little heat in it. A little tension. A little “I need to say this.” ChatGPT can help shape that, but it cannot create your lived experience from nothing.

Use this:

Help me improve this draft without making it sound generic.

Keep my point of view, humor, edge, and lived experience intact. Improve the structure and clarity, but flag anything that sounds like standard AI content.

Here is the draft:
[paste draft]

That is the creator workflow. AI helps. You lead.

What Business Owners Should Do

If you run a business, ChatGPT should not just be your content machine. It should be your thinking partner.

Use it to analyze customer feedback, draft offers, compare tools, summarize sales calls, improve onboarding, create SOPs, build FAQs, brainstorm campaigns, and spot bottlenecks. That is where the leverage lives.

But do not ask it for business advice without giving it real context. If ChatGPT does not understand your customer, offer, pricing, audience, constraints, and current traction, it will fill in the blanks with generic business soup.

Use this before asking for strategy:

Before giving me business advice, ask me questions about my customer, offer, pricing, audience, current traction, constraints, and what I have already tried.

After I answer, separate your response into:
1. What is clear
2. What you are assuming
3. What needs more evidence
4. What I should do next

That turns ChatGPT from “random advice generator” into something much more useful.

The Standard I Want You to Use

Here is the standard.

If ChatGPT helped you write it, you should still be able to explain it.

If ChatGPT helped you plan it, you should still understand the strategy.

If ChatGPT helped you summarize it, you should still know what matters.

If ChatGPT helped you decide it, you should still understand the tradeoffs.

If ChatGPT helped you polish it, it should still sound like you.

That is the difference between using AI and hiding behind AI.

One makes you better. The other makes you dependent.

We want better.

Your First Assignment

Open ChatGPT and paste this:

Help me audit how I currently use AI.

Ask me 10 questions about when I use ChatGPT, what I ask it to do, what I still do myself, how often I verify outputs, and whether I can explain AI-assisted work afterward.

After I answer, tell me:
1. Where I am using AI well
2. Where I may be using AI too early
3. What tasks I should think through before prompting
4. What tasks AI can help me improve
5. A simple weekly habit to keep my brain involved

Do not use this to shame yourself. That is boring and unhelpful. Use it to get honest.

Most people do not need to quit AI. They need to stop using it like a brain replacement and start using it like a brain upgrade.

The Bottom Line

ChatGPT is not making you dumb.

Bad habits are.

If you use it to avoid thinking, your thinking gets weaker. If you use it to challenge your ideas, clarify your thoughts, test your logic, and improve your drafts, you get sharper.

The tool is not the problem. The pattern is.

So keep your brain in the room. Start with your own messy thoughts. Ask ChatGPT to push back. Let it find what you missed. Check the logic. Make sure you can explain the final work. Then rewrite it until it sounds like you again.

That is how you get the speed without losing the skill.

That is how you use AI like a powerful person, not a passive one.

Subscribe to Academy of AI

Academy of AI helps everyday people learn the tools already changing work, money, creativity, and freedom. No panic, no jargon, and no gatekeeping. Just practical AI education for people who want to use these tools with clarity, confidence, and power.

Subscribe to Academy of AI if you want to work smarter without outsourcing the best parts of being human.

ChatGPT is one of the most useful tools on the internet, which is exactly why people say so much weird shit about it.

Some people think it reads the entire web every time they ask a question. Some people think it remembers everything forever. Some think it never lies. Some think it is secretly stealing every file, owning every image, replacing every expert, and preparing to ruin every dinner party with a six-paragraph answer about productivity.

The truth is less dramatic and way more useful.

ChatGPT is not magic. It is not a brain in a box. It is not a search engine by default. It is not a lawyer, doctor, therapist, accountant, business partner, or psychic. It is a powerful AI system that can help you think, write, learn, plan, analyze, create, and move faster when you understand what it can and cannot do.

That is the whole game.

The people who use ChatGPT well are not the people who believe the hype. They are the people who understand the tool clearly enough to use it with judgment.

So let’s clear the fog.

Read more

35 ChatGPT cheat codes make it way more useful

Most people use ChatGPT like a blank box with a blinking cursor and a dream. They type a messy question, hit enter, and hope the answer lands somewhere between “useful” and “not embarrassing.”

That is not a strategy. That is AI roulette.

The good news is that you do not need a giant prompt every time. You just need better shortcuts. Think of these cheat codes like little mode switches. You put one at the beginning of your prompt, and ChatGPT instantly understands what kind of answer you want.

Do you want a summary? Use a code. Do you want a table? Use a code. Do you want it to think more carefully, compare options, avoid fluff, or write for a specific audience? Use a code.

This works because clear instructions matter. OpenAI’s own prompting guidance recommends being specific about context, outcome, length, format, and style, and putting instructions at the beginning of the prompt when you want a more controlled response. (OpenAI Help Center)

That is exactly what these cheat codes do. They tell ChatGPT how to work before it starts working.

How to Use These ChatGPT Cheat Codes

Use these codes at the very beginning of your prompt. The code comes first, then the task. For example, instead of writing, “Can you summarize this article for me?” you would write, “/EXEC SUMMARY: Summarize this article for a busy founder deciding whether to act on it.”

That small change gives ChatGPT a job, a format, and a level of importance. You are not just asking for a summary. You are asking for a decision-ready summary.

You can also stack cheat codes when you need more control. For example, “/EXEC SUMMARY /CHECKLIST /NO AUTOPILOT: Summarize this launch plan and turn it into a practical action list.” That tells ChatGPT to keep it high-level, make it usable, and avoid lazy generic advice.

Do not overdo it. Two or three codes usually work better than seven. The goal is not to look like you are hacking the Pentagon. The goal is to get a better answer with less back-and-forth.

Read more

AI is not coming for every human. It is coming for average work, and that distinction matters. Average emails, average summaries, average slides, average research, average content calendars, average first drafts, and average strategy documents are all getting easier to produce, faster to revise, and cheaper to create.

For years, average work still looked valuable because it took time. Someone had to research the topic, draft the thing, format the document, clean up the copy, and send it to the team. Effort made the work look expensive, even when the final result was only fine.

AI broke that illusion. Now the first draft can happen in seconds, the summary can appear before your coffee cools, and the rough outline can show up before the meeting even starts. That does not mean human work is dead, so please unclench. It means generic work lost its costume.

The market is no longer asking, “Did a human make this?” The market is asking, “Is this worth paying for?” That is the new game. It is uncomfortable, but it is also clarifying as hell.

The Cost of Average Intelligence Is Falling

The cost of using powerful AI keeps dropping, which means more people and businesses can use it more often. Stanford’s 2025 AI Index found that the inference cost for a system performing at GPT-3.5 level dropped more than 280-fold between November 2022 and October 2024. That is not a tiny efficiency gain. That is a full reset in how cheap first-pass intelligence has become. (Stanford HAI)

Companies are paying attention. McKinsey’s 2025 global AI survey reported that 88% of respondents said their organizations regularly use AI in at least one business function. That does not mean every company is using AI well, but it does mean this shift has moved far beyond the “early adopter” phase. (McKinsey & Company)

This is why waiting is risky. AI does not need to become perfect to change your work. It only needs to become useful enough, cheap enough, and accessible enough for people to start asking why they are paying humans for work that looks generic.

The Real Threat Is “Good Enough”

The scary part is not that AI will become better than the best people. The scary part is that AI is already good enough for a lot of average tasks. A rough memo, a basic research summary, a first-pass sales email, a simple presentation outline, or a standard operating procedure draft can now be created with almost no friction.

That matters because most workplaces are full of tasks that never needed genius. They needed time, attention, and someone willing to do them. AI changes the price of that work, and once the price changes, expectations change with it.

When the first version becomes cheap, people do not create less. They create more. More drafts, more tests, more emails, more reports, more content, more prototypes, more options, and more analysis. The bottleneck stops being “Can we make something?” and becomes “Who knows what is worth making?”

That is where your value moves. You do not stay valuable by proving you can produce the same average output faster than a machine. You stay valuable by becoming the person who knows what should exist, what should be ignored, what matters, what will fail, and what is actually worth shipping.

The New Human Edge

The future does not belong to people who avoid AI. It belongs to people who use AI to amplify the parts of themselves that are hardest to copy. Those parts are judgment, taste, context, trust, relationships, accountability, and lived experience.

AI can generate 50 options, but someone still has to choose the right one. AI can draft the email, but someone still has to know whether it sounds like the brand, speaks to the customer, and deserves to be sent. AI can summarize the report, but someone still has to know which insight changes the decision.

That someone should be you. Not because you are anti-AI, but because you are learning how to move above the output layer. The person who only makes the thing becomes easier to replace. The person who defines the problem, guides the tool, edits the result, owns the outcome, and builds the system becomes harder to ignore.

Stop Competing on Basic Output

If your main value is “I can write this,” “I can summarize this,” “I can format this,” or “I can make this look professional,” you are standing in the most crowded part of the market. AI is already very good at basic output, and it will keep getting better.

That does not mean those skills are useless. Writing, summarizing, formatting, researching, and producing still matter. The difference is that those tasks are no longer enough on their own. They need to be connected to judgment, strategy, audience understanding, and results.

The better move is to stop selling the task and start owning the reason behind the task. Do not just write the email. Understand the buyer, the objection, the timing, and the action you want them to take. Do not just make the deck. Understand the decision the deck needs to unlock.

AI can help create the output. You bring the reason the output exists.

Move From Task-Doer to Problem-Definer

The most valuable person in the room is often not the fastest producer. It is the person who pauses and asks, “What are we actually trying to solve?” That question sounds simple, but it changes everything.

Most bad work starts with a weak brief. Someone asks for a landing page when they really need clearer positioning. Someone asks for a social post when they really need a stronger offer. Someone asks for a report when they really need a decision.

AI will happily execute the wrong task if you ask it to. That is why problem-definition becomes a premium skill. The better you get at identifying the real problem, the better every AI-assisted output becomes.

Before you ask AI to create anything important, ask it to help clarify the assignment. Make it identify the audience, the goal, the constraints, the stakes, the risks, and the success criteria first. A smarter brief creates smarter work.

Sell Outcomes, Not Hours

Nobody cares that something took six hours if AI can create a usable first version in six minutes. That sounds harsh, but it is actually freeing. You do not need to prove you suffered. You need to prove you solved the right problem.

The old argument was, “This took me a long time.” The new argument is, “This saved time, reduced risk, increased clarity, improved the decision, helped the customer, or made money.” That is a stronger position.

If you are a freelancer, creator, consultant, employee, founder, or educator, this matters right now. Stop centering the labor. Center the transformation. The work is not valuable because it took effort. It is valuable because it creates a result people care about.

Your new value statement should sound less like “I spent all weekend on this” and more like “I found the problem everyone else missed.” That is how you stay expensive when production gets cheap.

Build a Context Library

Prompts are useful, but context is where the real power lives. A prompt is what you ask in the moment. Context is what AI needs to understand your voice, audience, standards, products, values, preferences, and mistakes.

If AI keeps giving you generic answers, the tool might not be the problem. The problem may be that you have not given it enough of your world. AI cannot read your mind, your customer calls, your brand standards, your sales history, or your weird little preferences unless you capture them somewhere.

Start building a simple context library. Include your bio, audience notes, brand voice, offers, product details, customer objections, examples you love, examples you hate, and rules you never want AI to break. This can live in Claude Projects, ChatGPT Projects, Notion, Google Docs, or a plain folder on your computer.

Your expertise cannot help AI if it only lives in your head. Turn your taste, standards, and scars into reusable context. That is how you stop getting average answers from average prompts.

Train Your Taste

Taste is not some mysterious gift reserved for creative geniuses in black turtlenecks. Taste is pattern recognition. It comes from reps, feedback, failure, editing, shipping, watching what lands, and noticing what people actually respond to.

AI can generate options, but taste chooses. It tells you which headline has energy, which sentence feels fake, which sales angle is too obvious, which design is trying too hard, and which idea has real heat. That skill becomes more valuable as AI creates more volume.

The way to train taste is to compare outputs. Ask AI for ten versions, then rank them. Explain why one works and another does not. Save your best before-and-after edits so your standards become clearer over time.

Your taste is not the opposite of AI. Your taste is what makes AI useful. Without it, you are just approving polished beige internet soup.

Use AI Where You Already Have Judgment

A lot of people use AI backward. They say, “I am bad at this, so AI will do it for me.” That can work for low-stakes tasks, but it gets risky fast when the output matters.

If you do not understand the work, you cannot judge the work. You might approve something that looks clean but is strategically wrong. You might publish a piece that sounds professional but says nothing. You might accept a financial model, legal summary, or business plan that misses the most important risk.

Use AI first where you already have taste. If you are a strong writer, use AI for drafts, angles, edits, and repurposing. If you know sales, use AI to test offers and objections. If you understand operations, use AI to map workflows and find friction.

Your skill is the steering wheel. AI is the engine. Do not hand the wheel to something you cannot evaluate.

Become the Editor of Abundance

The old problem was scarcity. Not enough ideas, time, drafts, research, or options. AI creates a new problem: too much of everything.

Now you can generate 30 headlines, 20 email angles, 10 business models, 15 product ideas, and a month of content in one sitting. That sounds powerful, and it is. It can also become chaos if you do not know how to choose.

Editing becomes more valuable in a world full of options. Editing is not just grammar. It is deciding what matters, what gets cut, what gets clarified, and what deserves attention. It is knowing when more is making the work worse.

The person who can manage abundance wins. Use AI to create options, then use your judgment to cut hard. The goal is not more output. The goal is better decisions.

Turn Repeat Work Into Systems

If you do the same task three times, it should probably become a system. That system can be a checklist, template, prompt, workflow, operating procedure, intake form, project folder, or review process. It does not need to be fancy. It needs to make the next round easier.

Most people use AI to finish tasks. Smart people use AI to reduce repeated friction. If clients ask the same questions, build an FAQ. If your team creates the same report every week, build a template. If every launch feels chaotic, build a launch checklist.

A task disappears after you finish it. A system keeps paying you back. That is the difference between being busy and building leverage.

This is one of the biggest upgrades you can make. Stop being the person who answers the same question forever. Become the person who builds the system that makes the question easier to answer next time.

Stay Close to Real People

AI is trained on a lot of internet content, and the internet is not reality. It is loud, messy, performative, outdated, and full of people trying to sound smarter than they are. Real customers are better.

Talk to people. Read comments, support tickets, reviews, refund requests, sales call notes, objections, and customer emails. Study what people actually say when they are confused, excited, annoyed, skeptical, or ready to buy.

The more synthetic content floods the internet, the more valuable direct human contact becomes. Real language from real people gives you an edge AI cannot invent from scratch. It shows you the problems that actually hurt, not the ones a generic persona says might matter.

Do not let AI pull you away from reality. Use AI to understand reality faster. Paste real feedback into your AI tool and ask it to find patterns, objections, emotional language, content ideas, and product opportunities based only on what real people said.

Protect Trust Like It Is the Product

Trust is the most expensive asset in an AI-powered world. Speed is useful, but speed without trust turns into noise. If AI helps you publish faster but your work gets sloppier, you lose.

This matters for creators, brands, employees, founders, and educators. Do not publish claims you cannot defend. Do not fake expertise. Do not automate touchpoints that should feel human. Do not use AI to manipulate people, invent proof, or blur lines that should stay clear.

AI can help you move faster, but you are still responsible for what you send into the world. Your audience does not need you to be anti-AI. They need you to be accountable.

Before publishing important work, ask AI to check for trust risk. Have it flag unsupported claims, vague promises, privacy issues, tone problems, ethical concerns, and anything that could damage credibility. Then make the human call.

Kill Unnecessary Work Before You Automate It

AI makes it easy to add more. More emails, more reports, more dashboards, more automations, more posts, more workflows, more meetings disguised as productivity. More is not always better.

Sometimes the smartest move is to remove. Remove the report nobody reads. Remove the meeting nobody needs. Remove the workflow step that only exists because someone created it in 2018 and everyone got too tired to question it.

Do not use AI to make bad systems faster. That is just chaos with better formatting. Use AI to ask what should stop existing before you ask what should be automated.

This is where taste becomes operational. Taste is not only knowing what to create. Taste is knowing what to kill before it wastes another hour of everyone’s life.

Build Public Proof of Your Thinking

If average output gets cheap, your thinking needs to become visible. This matters whether you are a creator, employee, freelancer, founder, consultant, or educator. People need to see how you make decisions, not just what you produce.

Share your frameworks. Explain your process. Break down mistakes. Show before-and-after examples. Teach what you noticed. Tell people why one option worked and another failed. That kind of proof makes you harder to compare to a tool.

AI can generate a post, but it cannot be you. It does not have your lived experience, your relationships, your community, your scars, your taste, or your receipts. Your edge is not simply what you know. It is how you see.

This is why publishing matters. Public thinking builds trust before the sale, the interview, the pitch, or the opportunity. It tells people there is a human behind the work with judgment they can actually follow.

Make AI a Practice, Not a Panic Button

Most people use AI only when they are behind. They are rushed, overwhelmed, and desperate for a shortcut. Then they ask a weak question, get a weak answer, and decide the tool is overhyped.

That is not AI strategy. That is panic prompting.

AI gets powerful when it becomes a weekly practice. Pick one workflow each week and improve it. Build one better prompt, update one context file, review one output, create one system, or ask AI to find one bottleneck you can remove.

The World Economic Forum’s Future of Jobs research says employers expect 39% of key skills required in the job market to change by 2030. That is not a reason to panic, but it is a reason to practice. Your AI skill will not compound if you only touch these tools when you are already stressed. (World Economic Forum)

You do not need to become an AI expert overnight. You need to stop treating AI like a random tool you use sometimes and start treating it like a real skill you build on purpose.

The New Human Moat

People love saying “AI will never replace humans” because it feels comforting. Comfort is not a strategy. AI will replace some tasks, pressure some roles, and expose work that was only valuable because it used to take time.

But AI will also make sharp people sharper. It will help creators create more, entrepreneurs test faster, teachers explain better, employees automate busywork, and small teams build things that used to require bigger budgets.

The human moat is not simply “being human.” That is too vague to be useful. The human moat is context, judgment, taste, trust, relationships, responsibility, lived experience, and the ability to turn messy reality into useful decisions.

That is the work now. Not fighting AI on what it does best, but moving toward the value it cannot create alone.

The Academy of AI Framework

Here is the framework I want you to remember. AI creates options, but you create direction. AI creates drafts, but you create standards. AI creates speed, but you create trust. AI creates volume, but you create taste. AI creates systems, but you create responsibility.

That is how you compete. Not by pretending AI is not powerful. Not by trying to outwork a machine. Not by hiding from the future and hoping your industry gets a hall pass.

You compete by moving up. You stop being only the person who makes the thing. You become the person who knows what thing should be made, why it matters, who it serves, how it should work, and when it is good enough to ship.

That is a very different job. It is also a much better one.

Your First Assignment

Open Claude, ChatGPT, Gemini, or whatever AI tool you use and paste this prompt. Do not just read it and nod like a responsible adult. Run the audit and look at the answer honestly.

Help me identify the parts of my work that are most vulnerable to AI.

My role is: [insert role]
My main tasks are: [insert tasks]
My strongest skills are: [insert skills]
My audience, customers, or stakeholders are: [insert people]
My goals are: [insert goals]

Sort my tasks into 4 categories:

1. Work AI can probably do faster
2. Work AI can help me do better
3. Work that still needs my judgment
4. Work I should turn into a reusable system

Then give me a 30-day plan to become more valuable by using AI instead of competing against it.

This is where the shift starts. Find the weak spots, build the systems, capture your context, train your taste, stay close to real people, sell outcomes, protect trust, and practice every week. Average work is getting cheaper, but you do not have to stay average.

Subscribe to Academy of AI

Academy of AI helps everyday people learn the tools already changing work, money, creativity, and freedom. No panic, no jargon, and no gatekeeping. Just practical AI education for people who want to stay sharp, build smarter, and move with the future instead of getting dragged by it.

Subscribe to Academy of AI if you want to use AI with more clarity, confidence, and power. Bring your ambition, your questions, and your beautiful, messy, human brain. We have work to do.

Let’s get one thing clear before the internet starts acting messy.

Claude will not magically make money for you while you sit around refreshing your bank account like it owes you rent. AI does not replace work, judgment, taste, or follow-through.

But Claude can absolutely help you move faster.

It can help you find income ideas, package your skills, create offers, validate demand, write outreach, build content systems, and launch simple tests in days instead of months.

That is the real opportunity.

Most people do not need a massive business plan to start making money online. They need one clear offer, one specific audience, one painful problem, and one simple way to sell the solution.

Claude can help you find that.

The goal is not to build a perfect business this week. The goal is to test something real. A service. A template. A guide. A content funnel. A micro-offer. A small product that solves one annoying problem for one specific group of people.

That is how income starts.

Not with perfection.

With proof.

How to Use Claude to Find Income Ideas

The mistake most people make is asking Claude for “business ideas” with no context. Of course the answers feel generic. You gave it nothing to work with.

Claude needs your skills, time, budget, interests, audience, strengths, and limits. It also needs to know what you refuse to do. That part matters. A business you hate is not freedom. It is just a job with worse boundaries.

Use these prompts like strategy sessions. Fill in the blanks honestly. Then ask follow-up questions. Tell Claude what feels too hard, too boring, too expensive, or too slow. Make it refine the ideas until something feels simple enough to start.

You are not looking for the idea that sounds impressive.

You are looking for the one you can launch.

1. Claude Prompt to Find Income Streams You Can Test Fast

Before you build anything, you need to know what makes sense for your actual life. Not someone else’s life. Not some 22-year-old on TikTok with unlimited energy and suspicious lighting.

This prompt helps Claude match your skills, time, budget, and preferences to realistic income experiments. The word “experiment” matters. You are testing for demand, not marrying the first idea that flirts with you.

Copy this Claude prompt:

Act as a practical online income strategist. Help me find realistic income streams I can test in the next 7 days.

My skills are: [insert skills]
My experience level is: [beginner, intermediate, expert]
My available time this week is: [insert hours]
My budget is: [insert budget]
My preferred income model is: [services, digital products, content, templates, coaching, affiliate, community, etc.]
I do not want to do: [insert limits]
My current audience or network is: [describe audience, email list, social following, clients, or say none]
My income goal for the test is: [first sale, $100, $500, client lead, validation, etc.]

Give me 10 income stream ideas I could test quickly. For each idea, include the offer, target buyer, problem solved, why someone would pay, price range, where to find buyers, how AI can help, and the first 3 steps to start today.

Rank the ideas by fastest path to first dollar, easiest to execute, and best long-term potential. Be honest about what is realistic.

Use this when you feel scattered. Claude will give you a menu, but your job is to choose one. Not five. One.

2. Claude Prompt to Create a Fast Digital Product

Digital products are beautiful because you can make them once and sell them more than once. But people overcomplicate them into oblivion.

Your first digital product does not need to be a giant course. It can be a checklist, template, prompt pack, workbook, Notion dashboard, spreadsheet, mini-guide, swipe file, or tutorial.

Simple sells when it solves a real problem.

This prompt helps Claude find product ideas you can actually create without disappearing into a six-month “building phase” where nothing gets launched.

Copy this Claude prompt:

Act as a digital product strategist. Help me create a simple digital product I can build quickly with AI.

My niche is: [insert niche]
My audience is: [insert audience]
My skill or knowledge area is: [insert skill]
My audience struggles with: [insert problem]
My preferred product formats are: [templates, guides, ebooks, prompts, spreadsheets, Notion systems, Canva templates, mini-courses, etc.]
My skill level is: [beginner, intermediate, expert]
My goal is: [side income, first product, audience growth, paid subscribers, lead generation, etc.]
My available creation time is: [insert hours]

Generate 10 digital product ideas I can create fast. For each idea, include the product name, format, promise, ideal buyer, problem solved, price range, best platform to sell it, simple outline, and 5 content ideas to promote it.

Then choose the best product to launch first based on speed, demand, simplicity, and sales potential. Give me a 3-day creation plan.

This is the prompt for anyone sitting on knowledge but unsure how to package it. Your brain probably has products hiding inside it. Claude helps you pull them out and put a price tag on them.

Read more

Most people use ChatGPT like they just met it in an airport.

They open a blank chat, type one random request, get one okay answer, and then decide AI is either magic or overrated. Neither is true. The real problem is that they never set it up.

That is like hiring an assistant, giving them no job description, no background, no preferences, no goals, no examples, and then getting mad when they guess wrong. Of course the output feels generic. ChatGPT does not know you yet.

That changes today.

This is the ChatGPT setup checklist I wish everyone had before using AI for serious work. Before you ask it to write your emails, build your business plan, create spreadsheets, edit your content, plan your week, or help you make big decisions, you need to tell it who you are and how you work.

Not once in a random chat.

Properly.

OpenAI currently lets users manage personalization through settings like Custom Instructions, Memory, and style controls, though feature availability can vary by plan, workspace, and rollout. So use this as your practical setup guide, and do not panic if one menu looks slightly different on your account.

Let’s make ChatGPT useful before you make it busy.

1. Create Your ChatGPT Account and Secure It First

Before you customize anything, make sure your account is clean, accessible, and protected. Use an email you actually control, save your login in a password manager, and turn on security features before you start building your AI workflow around this account.

In your account settings, look for Security. OpenAI supports multi-factor authentication, and MFA adds a second verification step when signing in. OpenAI also supports passkeys in ChatGPT security settings, which can make sign-in safer and easier for eligible accounts.

This is not the sexy part of AI. It is the “please do not lose access to the account that knows your business, writing style, files, workflows, and goals” part. Protect the house before you start decorating it.

Prompt to use after setup:

Help me create a simple security checklist for my ChatGPT account.

Include:
1. Login method
2. Password manager
3. MFA or passkey setup
4. Recovery options
5. Devices I should review
6. What sensitive information I should never paste into ChatGPT

Keep it practical and beginner-friendly.

2. Decide Your Data and Privacy Settings on Purpose

Do not skip the privacy settings and pretend they are not there. If you are going to use ChatGPT for work, money, content, personal planning, or business strategy, you need to understand how your data settings work.

Go to Settings → Data Controls and review your options. OpenAI says Data Controls let users manage whether conversations are used to improve models, and users can also use Temporary Chat when they do not want a conversation to appear in history, use or create memories, or be used for training.

This does not mean you should paste your entire private life into ChatGPT. Do not share passwords, Social Security numbers, bank account numbers, passport numbers, private client data, or anything that would hurt you if exposed. ChatGPT needs context, not your identity documents.

Prompt to use:

Help me create my personal ChatGPT privacy rules.

I plan to use ChatGPT for:
[writing, business, finance, work, school, personal planning, etc.]

Create a clear list of:
1. Information I can safely share
2. Information I should summarize instead of pasting directly
3. Information I should never share
4. When I should use Temporary Chat
5. How to redact files or examples before uploading them

Make this simple enough that I can follow it every day.

3. Turn On Personalization Before You Start Working

Personalization is where ChatGPT starts becoming more useful. This is where you tell it how to respond, what kind of help you want, and what you do not want repeated in every answer.

On web, OpenAI’s Custom Instructions guide says to go to Settings → Personalization, make sure customization is enabled, and enter instructions in the Custom Instructions field. On mobile, the same guide points users to Settings → Customize ChatGPT.

Think of this as your default operating system. Without it, every chat starts too blank. With it, ChatGPT has a better idea of your voice, goals, standards, and preferences before you even ask the question.

Prompt to use:

Interview me so we can create my ChatGPT personalization setup.

Ask me questions about:
1. Who I am
2. What I do
3. My biggest goals
4. What I use ChatGPT for
5. My preferred communication style
6. How detailed I want answers
7. What tone I like
8. What I hate in AI responses
9. What formats help me most
10. What I want ChatGPT to remember about working with me

Ask one section at a time. After I answer everything, turn it into clean Custom Instructions I can paste into ChatGPT settings.

4. Fill Out Custom Instructions Like a Real Operating Manual

Most people write weak Custom Instructions. They say things like, “Be helpful” or “Use a friendly tone.” That is not enough. ChatGPT already tries to be helpful. You need to tell it what helpful means for you.

Your Custom Instructions should include who you are, what you are building, how you like to work, what level of detail you prefer, what tone you want, what formats you use most, and what behaviors you do not want. OpenAI notes that Custom Instructions can be changed or removed and are used to customize future responses.

Use this template as your starting point.

About me:
My name is [name]. I am [role/profession/business type]. I use ChatGPT mainly for [writing, strategy, research, spreadsheets, content, planning, learning, coding, etc.].

My current goals are:
1. [goal]
2. [goal]
3. [goal]

My audience or customers are:
[describe audience]

How I want ChatGPT to respond:
Use a [direct, warm, strategic, plainspoken, detailed, concise, etc.] tone. Give me practical answers I can use immediately. Ask clarifying questions before complex tasks. When possible, organize answers with clear headings and examples.

My preferences:
I prefer [paragraphs, bullet points, tables, step-by-step plans, templates, code blocks, etc.]. I like answers that are [specific, honest, actionable, creative, strategic, etc.].

Do not:
Do not use corporate filler. Do not over-explain simple things. Do not start with “Great question.” Do not repeat my question back to me. Do not give generic advice. Do not pretend to know something if you are uncertain.

Quality standard:
Prioritize accuracy, usefulness, clarity, and real-world application. If facts may have changed, tell me what needs verification.

This is the first big unlock. Once this is saved, ChatGPT stops starting from zero every time.

5. Set Up Memory With Intention

Memory is powerful, but you should use it intentionally. OpenAI says ChatGPT memory has controls for Reference saved memories and Reference chat history, and users can manage or delete saved memories in Settings → Personalization → Manage memories. Temporary Chat does not reference memories or create new ones.

Here is the simple way to think about it. Custom Instructions are what you manually write. Memory is what ChatGPT can retain or reference over time, depending on your settings. Use memory for things that are stable and helpful. Do not use it as a junk drawer.

Good things to remember: your name, your business, your writing preferences, your audience, your recurring projects, your goals, your favorite formats, and your “never do this” rules.

Prompt to use:

Help me decide what ChatGPT should remember about me.

Based on what I tell you, create:
1. A list of useful memories to save
2. A list of things that should stay out of memory
3. A short set of “Remember that…” statements I can give ChatGPT
4. A monthly memory review checklist

Here is what I want ChatGPT to know about me:
[paste your background, goals, work, preferences, and projects]

Then save only what is actually useful.

Subscribe now

6. Use This “Remember Me” Prompt

After your privacy settings and Custom Instructions are handled, give ChatGPT a clean memory prompt. This helps it understand the stable facts that should shape future work.

Do not overload this with every detail of your life. Keep it focused on the work you want ChatGPT to help with.

Remember the following about me for future conversations, if memory is enabled:

My name is [name].
I am [role/profession].
I am building or working on [main project/business/goal].
My main audience is [audience].
My top 3 goals right now are [goals].
I prefer responses that are [style preferences].
I dislike responses that are [things to avoid].
When helping me, prioritize [clarity, speed, depth, creativity, accuracy, strategy, etc.].
Before major tasks, ask clarifying questions first.

This is where ChatGPT starts to feel less like a tool and more like someone who has been briefed.

7. Choose Your Base Style and Tone

If your account has the option, choose a base style and tone that fits how you want ChatGPT to communicate. OpenAI says users can select a ChatGPT personality in Settings → Personalization, and changes apply across chats.

Do not overthink this. If you are not sure, choose the default or most neutral option and let your Custom Instructions do the heavy lifting. A personality setting can help, but your own instructions matter more.

Prompt to use:

Based on my communication preferences, help me choose the best ChatGPT tone.

I want responses that feel:
[direct, warm, analytical, creative, concise, detailed, casual, professional, etc.]

I do not want responses that feel:
[corporate, robotic, overly cheerful, too long, too vague, etc.]

Recommend the best default tone and write a short instruction I can add to my Custom Instructions.

Your goal is not to make ChatGPT sound cute. Your goal is to make it useful in a voice you can actually stand reading every day.

8. Create Your Personal AI User Manual

This is the step most people never do. They tell ChatGPT one thing at a time, forever. That is inefficient and deeply annoying.

Instead, create a personal AI user manual. This is a one-page document that explains who you are, how you work, what you are building, and how ChatGPT should help you.

Prompt to use:

Create my Personal AI User Manual.

Ask me questions first about:
1. My work
2. My business or career
3. My audience
4. My goals
5. My current projects
6. My strengths
7. My weaknesses
8. My preferred working style
9. My writing or communication style
10. What kind of help I want from ChatGPT

After I answer, write a clean one-page user manual that I can save, paste into projects, or use to update my Custom Instructions.

This becomes your foundation. When a new chat goes sideways, your user manual brings it back.

9. Create Your Goal Map

ChatGPT cannot help you move toward a goal it does not know exists. So tell it where you are going.

Your goal map should include what you are building, what matters right now, what deadlines exist, what success looks like, and what you do not want to waste time on. This makes ChatGPT more strategic because it can connect tasks back to outcomes.

Prompt to use:

Help me create a 90-day goal map.

My current situation is:
[describe where you are]

My main goals are:
[list goals]

My constraints are:
[time, money, skills, team, energy, tools, etc.]

Ask me any missing questions. Then create a 90-day goal map with:
1. Main objectives
2. Key projects
3. Weekly priorities
4. Success metrics
5. Risks
6. What I should stop doing
7. How ChatGPT should help me each week

This turns ChatGPT from a response machine into a planning partner.

10. Teach ChatGPT Your Voice

If you want ChatGPT to write anything for you, teach it your voice before asking for drafts. Otherwise, it will write like the internet’s most polite middle manager.

Give it samples. Ask for analysis. Turn that analysis into a style guide.

Prompt to use:

I want you to learn my writing voice.

Here are 3 examples of my writing:
[paste sample 1]
[paste sample 2]
[paste sample 3]

Analyze my voice in detail. Look at:
1. Sentence length
2. Paragraph style
3. Tone
4. Humor
5. Word choice
6. Rhythm
7. Openings and endings
8. How I explain ideas
9. What I avoid
10. What makes my writing sound like me

Then create a reusable voice guide. After that, when I ask you to draft content, use this guide unless I tell you otherwise.

Your voice is not decoration. It is trust. Do not let AI sand it down.

Subscribe now

11. Build Your “Do Not Do This” List

A good assistant knows what to do. A great assistant also knows what not to do.

Your “do not” list might include no generic advice, no fake urgency, no corporate jargon, no overusing em dashes, no long intros, no fake case studies, no unsupported claims, no unnecessary disclaimers, no bland social media captions, and no “in today’s fast-paced world” nonsense.

Prompt to use:

Help me create my “Do Not Do This” list for ChatGPT.

Ask me what annoys me in AI responses, writing, strategy, planning, and research.

Then create a clear list of rules ChatGPT should follow when working with me.

Format it as:
1. Never do this
2. Why it bothers me
3. What to do instead

This is how you get fewer annoying answers without correcting ChatGPT 700 times.

12. Set Up Projects for Your Main Workflows

If your account has Projects, use them. OpenAI says Projects create a focused space for chats and work, and project memory requires memory settings like Reference saved memories and Reference chat history for most subscriptions.

Create Projects for the work you repeat. Examples: Newsletter, Business Strategy, Client Work, Personal Finance, Fitness, Learning, Content Calendar, Spreadsheets, Travel, Research, or Family Admin.

Do not put everything in one Project. That defeats the point. Keep each Project focused so ChatGPT has the right context without dragging unrelated clutter into the conversation.

Prompt to use:

Help me design my ChatGPT Projects.

Here are the areas of my life or work where I use ChatGPT:
[list areas]

Recommend which Projects I should create. For each Project, include:
1. Project name
2. Purpose
3. What chats belong there
4. What files or context I should add
5. What instructions the Project should use
6. What should not go in that Project

This is how you stop treating ChatGPT like one giant junk drawer.

13. Add Project Instructions for Each Workflow

Your general Custom Instructions are for your whole account. Project Instructions are for a specific workflow. Your newsletter Project should not behave exactly like your tax prep Project. Your spreadsheet Project should not respond like your creative writing Project.

For each Project, write instructions that explain what the Project is for, what standards matter, what output formats you use, and how ChatGPT should help.

Prompt to use:

Write Project Instructions for my ChatGPT Project.

Project name:
[insert name]

Project purpose:
[describe purpose]

This Project will be used for:
[list use cases]

My goals for this Project:
[list goals]

Preferred output formats:
[articles, outlines, spreadsheets, checklists, scripts, dashboards, research briefs, etc.]

Quality standards:
[describe standards]

Things to avoid:
[list avoidances]

Write clear Project Instructions that ChatGPT can follow every time I work inside this Project.

This is where ChatGPT starts acting like a specialist instead of a general assistant.

14. Upload or Add Context Safely

If a Project supports files or context, use it carefully. Add documents that help ChatGPT do better work: brand guides, product descriptions, audience research, writing samples, SOPs, offer details, content pillars, client-safe briefs, and examples of finished work.

Do not upload sensitive private records just because you can. Redact first. Summarize when possible. If you would panic seeing the file forwarded to the wrong person, think twice before using it as context.

Prompt to use:

Help me decide what context to add to this ChatGPT Project.

The Project is for:
[describe project]

I have these possible files or notes:
[list files or context]

Tell me:
1. What I should add
2. What I should summarize instead
3. What I should redact
4. What should go in Project Instructions
5. What should stay out for privacy
6. What examples would improve output quality the most

Good context is leverage. Bad context is clutter. Sensitive context is risk.

15. Create Your “Ask Me First” Rule

This might be the most important prompt in the entire setup.

Before any serious task, ChatGPT should ask questions. Not always. Not for tiny things. But for strategy, writing, business, money, spreadsheets, legal-adjacent topics, health-adjacent topics, travel plans, big decisions, or anything with nuance.

Add this rule to your Custom Instructions or Project Instructions.

For complex tasks, do not start immediately.

First ask me the most important clarifying questions. Ask only what you need to produce a strong answer.

After I answer, summarize the goal, identify assumptions, and then begin.

This one rule saves time because it stops ChatGPT from confidently building the wrong thing.

Subscribe now

16. Create a Default Work Request Template

Most people write lazy prompts and then blame ChatGPT for lazy answers. The better move is to use a work request template.

This is the template you use when you want strong output.

Task:
[What do you want ChatGPT to do?]

Context:
[What does ChatGPT need to know?]

Goal:
[What outcome are you trying to achieve?]

Audience:
[Who is this for?]

Constraints:
[Time, budget, tone, length, format, tools, rules, etc.]

Inputs:
[Paste data, notes, examples, files, or links]

Output format:
[Table, article, checklist, spreadsheet plan, email, script, strategy, etc.]

Quality standard:
[What would make this excellent?]

Before you begin:
Ask me any missing questions.

Save this. Use it constantly. This is how you stop sending ChatGPT half-baked requests and getting half-baked answers.

17. Tell ChatGPT How to Challenge You

ChatGPT should not just agree with you. Agreement is nice. Accuracy is better.

Tell it when to push back. Tell it to find weak logic, missing assumptions, risky decisions, better alternatives, and lazy thinking. You do not need a cheerleader. You need a useful partner.

Prompt to use:

When I bring you an idea, plan, draft, or decision, do not just improve it.

First, challenge it.

Look for:
1. Weak assumptions
2. Missing context
3. Risks
4. Better alternatives
5. Unclear logic
6. Over complication
7. What I may be avoiding

Then give me the strongest version of the idea and your honest recommendation.

This makes ChatGPT more valuable immediately. Less applause. More clarity.

18. Set a Truth and Verification Rule

AI can be useful and still be wrong. That is why you need a verification rule.

For current events, laws, prices, product details, platform features, medical information, financial guidance, statistics, or anything that could change, ChatGPT should tell you what needs checking. If browsing or sources are available, it should use them. If not, it should say so.

Prompt to use:

Follow this truth and verification rule when helping me:

If something depends on current facts, laws, prices, platform features, product details, medical guidance, financial rules, or statistics, tell me that it needs verification.

If you have access to current sources, use them and cite them.

If you do not have access, clearly say what you are basing the answer on and what I should verify.

Do not make confident claims when the information may be outdated.

This is not about making ChatGPT boring. It is about making it trustworthy.

19. Create Your Output Formats

If you repeatedly ask ChatGPT for the same types of work, create default formats. This saves time and makes the output more consistent.

Examples: weekly plans, article drafts, spreadsheet blueprints, research briefs, social posts, meeting notes, client proposals, launch plans, sales pages, email sequences, content calendars, and decision memos.

Prompt to use:

Help me create reusable output templates for the work I do most often.

My recurring tasks are:
[list tasks]

For each task, create:
1. Best prompt to use
2. Ideal output structure
3. Quality checklist
4. Follow-up questions ChatGPT should ask
5. Common mistakes to avoid
6. A reusable template I can paste into future chats

This is how ChatGPT becomes a workflow system instead of a novelty.

20. Run a Final ChatGPT Setup Audit

Once your settings, memory, Custom Instructions, Projects, privacy rules, and starter prompts are ready, audit the whole setup. Do not assume it is good because it exists.

Ask ChatGPT to review everything like an operator.

Prompt to use:

Audit my ChatGPT setup.

Here is what I have configured:
Custom Instructions:
[paste]

Memory statements:
[paste]

Projects:
[list]

Privacy rules:
[paste]

Default work request template:
[paste]

Voice guide:
[paste]

Do-not-do list:
[paste]

Review this setup and tell me:
1. What is strong
2. What is missing
3. What is too vague
4. What could create bad outputs
5. What should be shorter
6. What should be added to memory
7. What should be removed for privacy
8. What I should add to Projects
9. What my first 3 saved prompts should be
10. The final optimized version of my setup

This is the final polish. Setup is not done when you add words to settings. Setup is done when ChatGPT can actually help you better because of those words.

Subscribe now

The First Prompt Everyone Should Use Before Anything Else

Use this before you ask ChatGPT to build your business, write your content, plan your life, or organize your work.

Before we work on anything else, I want you to understand me.

Interview me in sections so you can learn:
1. Who I am
2. What I do
3. What I am building
4. My top goals
5. My audience or customers
6. My strengths and weaknesses
7. How I like to work
8. How I like to communicate
9. What kind of help I want from ChatGPT
10. What I do not want from ChatGPT
11. What recurring projects we will work on together
12. What information should become Custom Instructions
13. What information should become saved memory
14. What information should stay private and never be saved

Ask one section at a time. After I answer everything, create:
1. Custom Instructions
2. Memory statements
3. Project recommendations
4. A personal AI user manual
5. A reusable work request template

That prompt alone can change everything.

The Main Point

ChatGPT is not supposed to be a stranger every time you open a new chat. It should know how to help you, what you are working toward, what voice you use, what formats you prefer, and what kind of answers are worth your time.

That does not happen automatically. You have to set the table.

Secure the account. Choose your data settings. Turn on personalization. Write Custom Instructions. Use memory intentionally. Create Projects. Add context. Teach it your voice. Tell it what not to do. Make it ask questions before big tasks. Give it standards. That is how ChatGPT stops feeling generic. That is how it starts working like your assistant.

Not a perfect assistant. Not a magical brain replacement. Not some all-knowing machine that never makes mistakes. A useful assistant. A fast assistant. An assistant that gets better because you trained it to understand you.

Most people will keep opening ChatGPT cold and wondering why the answers feel average. Do not do that. Set it up once. Then make it work.

Subscribe to Academy of AI for practical prompts, workflows, and strategies that help you use AI to work smarter, create faster, and build more freedom in your real life.

Most people ask ChatGPT for spreadsheet help like this: “Can you make me a budget spreadsheet?” Then they get a basic table, a few obvious columns, and maybe one formula that looks useful until they actually try to run their life or business on it.

That is not how you build a serious spreadsheet.

If you want ChatGPT to create spreadsheets that actually work, you need to stop asking for “a spreadsheet” and start asking for a system. A real spreadsheet has structure, assumptions, connected tabs, formulas, dashboards, validations, error checks, and a clean logic flow. It should not just look pretty. It should calculate correctly.

That is the difference between a cute template and a spreadsheet that can help you make million-dollar decisions.

ChatGPT can analyze uploaded files, answer questions about data, and create tables or charts when a structured view is useful. OpenAI also supports common spreadsheet file types like XLSX, XLS, CSV, and TSV, and ChatGPT for Excel and Google Sheets can help build, update, and explain multi-tab spreadsheets with formulas, references, and assumptions directly inside those spreadsheet tools.

But the tool is only as good as the instructions.

This guide will show you exactly what to say.

First, Know What ChatGPT Needs From You

A powerful spreadsheet starts before the formulas. It starts with context.

ChatGPT needs to know what the spreadsheet is supposed to do, who will use it, what platform you want, what data goes in, what outputs matter, and what decisions the spreadsheet needs to support. If you skip that part, ChatGPT will guess. And when AI guesses inside a spreadsheet, that is how you end up with broken formulas wearing a nice font.

Before you ask ChatGPT to build anything, give it the job, the platform, the data, the logic, and the success criteria. Don’t say, “Make me a financial model.” Say, “Build me an Excel workbook that forecasts monthly revenue, expenses, cash flow, profit margin, runway, and break-even point for a subscription business with three pricing tiers.”

That is a different request.

That gets a different spreadsheet.

The Primary Prompt: Start Here

Use this first. This prompt forces ChatGPT to slow down, gather requirements, and design the spreadsheet before building it.

Act as a senior spreadsheet architect and financial model builder.

I want to create a fully functional spreadsheet for: [describe the business, project, calculator, model, dashboard, tracker, or analysis].

Before you build anything, ask me the 10 most important questions you need answered to make this spreadsheet accurate, useful, and easy to maintain.

The final spreadsheet should include:
- Connected sheets
- Working formulas
- Clear assumptions
- Input cells separated from calculation cells
- A dashboard or summary page
- Data validation where useful
- Error checks
- Clear labels and formatting
- A README or instructions tab
- A QA checklist to verify the spreadsheet works

Platform: [Excel / Google Sheets / either]
Primary user: [me, my team, clients, investors, students, etc.]
Main decision this spreadsheet should support: [describe decision]
Complexity level: [simple, intermediate, advanced]

Do not create a generic template. Design a spreadsheet system that can handle real calculations and real decisions.

This is the move. You are not asking ChatGPT to throw columns on a page. You are asking it to architect the whole workbook.

Step 1: Make ChatGPT Define the Spreadsheet Blueprint

Don’t let ChatGPT build the file first. Make it map the system first.

A spreadsheet blueprint tells you what each tab does, what data belongs there, what formulas connect the sheets, and how the user should move through the model. This prevents the most common spreadsheet disaster: random tabs, random formulas, random chaos.

Use this after ChatGPT asks its clarifying questions.

Based on my answers, create a complete spreadsheet blueprint before building the workbook.

Include:
01. The name of every sheet
02. The purpose of each sheet
03. The inputs required on each sheet
04. The outputs produced by each sheet
05. How each sheet connects to the others
06. The formulas or calculations needed
07. The assumptions that must be separated from calculations
08. The dashboard metrics
09. The error checks
10. The recommended build order

Use this format:

Sheet Name:
Purpose:
Inputs:
Outputs:
Connected Sheets:
Key Formulas:
Notes:

Do not generate the spreadsheet yet. First give me the full blueprint so I can approve the structure.

This prompt makes ChatGPT think like a builder, not a decorator. The blueprint is where the spreadsheet starts becoming serious.

Step 2: Tell ChatGPT Which Platform You Need

Excel and Google Sheets are cousins, not twins.

Some formulas work in both. Some don’t. Excel has tools like XLOOKUP, LET, LAMBDA, Power Query, PivotTables, and dynamic arrays. Google Sheets has QUERY, IMPORTRANGE, ARRAYFORMULA, FILTER, and its own sharing and collaboration flow.

If you don’t name the platform, ChatGPT may give you formulas that look right but break when you paste them.

Use this prompt before formula creation.

Before writing any formulas, confirm the spreadsheet platform.

I am using: [Excel / Google Sheets]
Formula style: [Excel 365 dynamic arrays / older Excel / Google Sheets]
Locale: [US commas / semicolon separators if applicable]
Currency: [insert currency]
Date format: [MM/DD/YYYY or DD/MM/YYYY]
Number format preferences: [whole numbers, decimals, percentages, currency, etc.]

All formulas must be written for this platform only. Do not mix Excel and Google Sheets syntax.

If a formula would differ between Excel and Google Sheets, explain the difference and give me only the version for my platform.

This one detail saves hours. Spreadsheet formulas are not the place for vibes.

Step 3: Create the Workbook Architecture

Now you ask ChatGPT to design the actual tabs.

For serious spreadsheets, I like this structure: README, Inputs, Assumptions, Raw_Data, Calculations, Scenario_Manager, Dashboard, QA_Checks, and Change_Log. You may not need every tab, but you need the logic.

The biggest rule is simple: don’t bury assumptions inside formulas. Assumptions belong on an input or assumptions sheet. Formulas should reference them.

Use this command.

Create the workbook architecture for this spreadsheet.

Use separate sheets for:
- README
- Inputs
- Assumptions
- Raw_Data if needed
- Calculations
- Scenario_Manager if useful
- Dashboard
- QA_Checks
- Change_Log

For each sheet, define:
- Column headers
- Cell sections
- Required inputs
- Formula zones
- Output zones
- Formatting notes
- Data validation rules
- Which cells should be protected or locked

Make the workbook easy for a non-technical person to use without breaking the formulas.

This is how you make a spreadsheet that does not collapse the first time someone types over a formula cell.

Step 4: Build the Inputs and Assumptions First

Every great spreadsheet has a clean place for inputs.

This is where the user controls the model. Pricing, costs, dates, conversion rates, tax rates, headcount, inventory, interest rates, churn rates, ad spend, revenue targets, whatever matters. If those assumptions are scattered across random tabs, the spreadsheet becomes a haunted house.

Use this prompt.

Design the Inputs and Assumptions sheets.

The spreadsheet is for: [describe use case]

Create a complete list of all user-controlled inputs and assumptions. For each one, include:
- Input name
- Description
- Recommended cell location
- Data type
- Example value
- Allowed range
- Validation rule
- Whether it is required or optional
- Which formulas or sheets depend on it

Separate assumptions into logical categories. For example:
Revenue assumptions
Expense assumptions
Tax assumptions
Time assumptions
Growth assumptions
Risk assumptions
Scenario assumptions

Make sure no major calculation depends on a hardcoded number hidden inside a formula.

This is the boring part that makes the powerful part possible. Clean inputs create clean models.

Step 5: Ask ChatGPT for the Formula Map Before the Formulas

Most people ask for formulas too early.

Do not do that.

First, ask for a formula map. A formula map tells you what needs to be calculated, where it lives, and what inputs it depends on. This makes the logic traceable.

Use this prompt.

Create a complete formula map for this workbook.

For every calculated field, include:
- Sheet name
- Cell or column where the formula belongs
- Formula purpose
- Inputs used
- Connected sheets referenced
- Formula logic in plain English
- Final formula in [Excel / Google Sheets] syntax
- Expected output type
- Common errors to watch for

Do not skip intermediate calculations. If a dashboard metric depends on several steps, show each step clearly.

This prompt is the difference between “here is a formula” and “here is a model.”

Subscribe now

Step 6: Make ChatGPT Build Connected Sheets

Connected sheets are where the magic happens.

The Inputs sheet feeds the Calculations sheet. The Calculations sheet feeds the Dashboard. The Scenario_Manager changes the assumptions. The QA_Checks sheet flags broken logic. The README tells humans how to use the thing without destroying it.

Use this prompt.

Now create the connected sheet logic.

Show exactly how data should flow through the workbook:
Inputs → Assumptions → Calculations → Dashboard → QA_Checks

For each connection, tell me:
- Source sheet
- Source cell or range
- Destination sheet
- Destination cell or range
- Formula used
- What should happen if the source cell is blank
- What should happen if the source value is invalid

Make sure every dashboard number traces back to source inputs or raw data.

This is how you stop building spreadsheet islands. Every tab should have a reason to exist.

Step 7: Tell ChatGPT to Use Real Formulas, Not Placeholder Logic

ChatGPT will sometimes give you spreadsheet “concepts” instead of actual formulas. That is not good enough.

You want formulas that can be pasted into cells. You want the exact syntax. You want ranges. You want references. You want the actual work.

Use this prompt.

Now write the exact formulas for the workbook.

Requirements:
- Use real spreadsheet formulas, not pseudocode
- Use formulas compatible with [Excel / Google Sheets]
- Include exact cell references
- Use named ranges where they make the model easier to maintain
- Avoid hardcoded assumptions inside formulas
- Use error handling where appropriate
- Explain each formula in plain English after giving it

Format each formula like this:

Sheet:
Cell:
Formula:
What it does:
Inputs it references:
Expected result:
Potential error:
Fix if error appears:

This is where your spreadsheet starts becoming functional.

Step 8: Add Data Validation So People Cannot Break It

A powerful spreadsheet should protect users from themselves.

If a cell needs a percentage, don’t let someone enter “maybe.” If a dropdown should only include “Monthly,” “Quarterly,” and “Annual,” make that clear. If an input should be positive, validate it.

Use this prompt.

Add data validation rules to this workbook.

For every user input cell, define:
- Allowed data type
- Allowed range
- Dropdown options if needed
- Error message
- Help text
- Whether blank values are allowed
- What downstream formulas depend on this input

Also tell me which cells should be locked, which should be editable, and which should be visually highlighted for users.

This is how you make the spreadsheet feel professional. Not fancy. Professional.

Step 9: Build the Dashboard Last

The dashboard is not the spreadsheet. It is the front door.

Don’t start with the dashboard. Start with the logic. Then let the dashboard summarize what matters.

A good dashboard should answer the question: “What decision should I make now?” If it is just a bunch of numbers, it is decoration.

Use this prompt.

Design a dashboard for this workbook.

The dashboard should show the most important metrics for this decision:
[describe the decision]

Include:
- KPI cards
- Trend charts
- Scenario comparison
- Alerts or warnings
- Top risks
- Recommended next action
- Filters or dropdowns if useful

For each dashboard item, tell me:
- Metric name
- Why it matters
- Source sheet
- Source formula
- Display format
- Suggested chart type if relevant
- Warning threshold
- Interpretation guide

Make the dashboard useful for decision-making, not just visually busy.

That last sentence matters. A dashboard should earn its place.

Subscribe now

Step 10: Add Scenario Planning

Million-dollar spreadsheets need scenarios.

Base case. Best case. Worst case. Conservative case. Aggressive case. Custom case.

Scenarios help you see how the model changes when assumptions change. This is how a spreadsheet becomes a decision tool instead of a static report.

Use this prompt.

Add scenario planning to this workbook.

Create a Scenario_Manager sheet with at least these scenarios:
- Conservative
- Base Case
- Aggressive
- Custom

For each scenario, define which assumptions change and by how much.

Then create formulas that allow the user to select a scenario from a dropdown and automatically update the model.

Include:
- Scenario input table
- Dropdown selection cell
- Formulas that pull the selected scenario assumptions
- Dashboard comparison between scenarios
- Warning messages if a scenario creates unrealistic results

Use formulas compatible with [Excel / Google Sheets].

This is the part that makes clients, investors, and business owners lean in. They don’t just want one answer. They want to know what happens if reality changes.

Step 11: Ask ChatGPT to Create Error Checks

If your spreadsheet does not have error checks, it is not finished.

Error checks are the safety net. They catch missing inputs, broken formulas, mismatched totals, invalid dates, negative values, divide-by-zero problems, and numbers that look too weird to trust.

Use this prompt.

Create a QA_Checks sheet for this workbook.

The QA sheet should test for:
- Missing required inputs
- Invalid input values
- Broken formulas
- Negative values where they should not exist
- Totals that do not tie out
- Dates outside expected ranges
- Divide-by-zero risks
- Duplicate records
- Dashboard metrics that do not match calculation sheets
- Scenario outputs that look unrealistic

For each check, include:
- Check name
- What it tests
- Formula to use
- Expected result
- Warning message if failed
- How to fix it

Use simple PASS / FAIL outputs with conditional formatting recommendations.

This is how you build trust into the spreadsheet. A model that cannot be checked should not be trusted.

Step 12: Make ChatGPT Stress-Test the Spreadsheet

A spreadsheet can look perfect with normal numbers and fall apart with real ones.

Ask ChatGPT to test edge cases. What happens if revenue is zero? What if costs increase? What if a customer cancels? What if the tax rate is blank? What if inventory goes negative? What if dates are missing?

Use this prompt.

Stress-test this spreadsheet before finalizing it.

Create test cases for:
- Normal use
- Missing inputs
- Zero values
- Negative values
- Extremely high values
- Date errors
- Duplicate data
- Unexpected blanks
- Scenario changes
- Formula dependency breaks

For each test case, include:
- Test input
- Expected output
- Formula or sheet affected
- Whether the model should pass or fail
- How the workbook should alert the user

Then identify the 10 most likely ways a real user could break this spreadsheet and tell me how to prevent each one.

This is the prompt that separates a template from a tool.

Step 13: Ask ChatGPT to Build the Actual File

If your ChatGPT session has file creation or data analysis tools available, you can ask it to create the workbook file. ChatGPT’s data analysis capabilities can work with structured files and perform analysis or visualization, and OpenAI’s docs describe ChatGPT as able to run code in a secure environment for tasks like analyzing spreadsheets, cleaning data, and making projections.

Use this prompt when you are ready for the actual workbook.

Now create the actual spreadsheet file.

Build it as a downloadable [XLSX / CSV structure / Google Sheets implementation guide].

Requirements:
- Include all sheets from the approved blueprint
- Add all formulas using [Excel / Google Sheets] syntax
- Keep input cells separate from calculation cells
- Add data validation rules where possible
- Add conditional formatting where useful
- Add a dashboard sheet
- Add a QA_Checks sheet
- Add a README sheet explaining how to use the workbook
- Add a Change_Log sheet
- Freeze header rows
- Use clear formatting
- Make the workbook easy to audit

After creating it, review the workbook structure and tell me what you built, what formulas are included, and what I should verify manually after opening it.

Important: still check the file. Open it. Test it. Change inputs. Recalculate. Try to break it. A spreadsheet that handles messy reality is the one you want.

Step 14: Use ChatGPT Inside Excel or Google Sheets

If you are using ChatGPT for Excel or Google Sheets, you can work inside the spreadsheet itself instead of only prompting in a chat. OpenAI describes this as a spreadsheet-native experience in a sidebar that can help create spreadsheets from scratch, ask questions about existing spreadsheets, and make updates using natural language.

That means you can give commands like this inside the spreadsheet.

Review this workbook and identify every formula that references another sheet.

Check whether the references are logical, whether any formulas are inconsistent across rows, and whether any dashboard values do not match their source calculations.

Then suggest fixes before changing anything.

Or this:

Create a new sheet called QA_Checks.

Add checks for missing required inputs, duplicate rows, broken references, totals that do not tie out, and dashboard metrics that do not match the calculation sheet.

Use PASS / FAIL labels and conditional formatting.

Or this:

Add a scenario dropdown to the Inputs sheet.

The options should be Conservative, Base Case, Aggressive, and Custom.

Update the formulas on the Calculations sheet so they pull the correct assumptions based on the selected scenario.

This is where ChatGPT becomes less like a tutor and more like a spreadsheet operator.

Step 15: Have ChatGPT Write the README Tab

Don’t skip the instructions tab.

A spreadsheet without instructions is a trap. The person who built it understands it. Everyone else is one accidental overwrite away from chaos.

Use this prompt.

Write a README sheet for this workbook.

Include:
- What this spreadsheet does
- Who should use it
- What each sheet is for
- Which cells users should edit
- Which cells users should not touch
- How to update assumptions
- How to read the dashboard
- How to use scenario planning
- How to troubleshoot common errors
- What should be reviewed before making decisions from the model

Make it clear enough that someone else could use the spreadsheet without asking me questions.

This is a small step with a big payoff. Documentation is not boring when it saves the model from being destroyed.

Subscribe now

Step 16: Create a Formula Audit Command

Once the workbook exists, make ChatGPT audit it.

This is not optional. Even strong spreadsheet builders make mistakes. AI can make mistakes too. So the workflow is not “generate and trust.” The workflow is “generate, audit, test, revise.”

Use this prompt.

Audit this spreadsheet like a senior financial model reviewer.

Look for:
- Broken references
- Incorrect ranges
- Formulas that are inconsistent across rows
- Hardcoded numbers inside calculation formulas
- Missing error handling
- Circular references
- Unclear assumptions
- Dashboard values that do not tie back to source data
- Overly complex formulas that should be simplified
- Places where named ranges would make the workbook easier to maintain

Return:
1. Issues found
2. Why each issue matters
3. Exact fix
4. Revised formula if needed
5. Priority level: high, medium, or low

This is how you make the spreadsheet stronger after the first draft.

Step 17: Turn the Spreadsheet Into a Reusable Business Asset

A million-dollar spreadsheet is not just a one-time file. It is an asset.

You should be able to reuse it, update it, hand it to a client, sell it as a template, train a team on it, or turn it into a dashboard system. That means it needs standards.

Use this prompt.

Help me turn this spreadsheet into a reusable business asset.

Create:
- A clean naming convention for sheets, tables, and key ranges
- A version control system
- A Change_Log format
- A user guide
- A QA checklist
- A client handoff checklist
- A list of assumptions that must be reviewed monthly or quarterly
- A process for updating the workbook without breaking formulas

Also recommend what parts of the spreadsheet could become a paid template, internal tool, client dashboard, or automated reporting system.

This is where the spreadsheet stops being a file and starts becoming leverage.

The Perfect Spreadsheet Prompt Stack

If you want the short version, here is the whole workflow.

Start with the primary prompt. Make ChatGPT ask questions. Approve the blueprint. Confirm the platform. Build inputs and assumptions. Create the formula map. Build connected sheets. Add real formulas. Add validation. Build the dashboard. Add scenarios. Add QA checks. Stress-test the model. Generate the file. Audit the formulas. Write the README. Turn it into a reusable asset.

That is the system.

Not “make me a spreadsheet.”

Not “give me a formula.”

Not “create a tracker.”

Those prompts get you beginner spreadsheets. This workflow gets you actual models.

The Final Command

When you want ChatGPT to do the whole thing from start to finish, use this.

Act as a senior spreadsheet architect, financial modeler, and QA analyst.

I want you to help me build a fully functional spreadsheet system for: [describe use case].

Platform: [Excel / Google Sheets]
Primary user: [describe user]
Main business decision: [describe decision]
Data sources: [describe data]
Required outputs: [describe outputs]
Complexity level: [simple / intermediate / advanced]
Currency, date format, and locale: [insert details]

Workflow:
1. Ask me the 10 most important clarifying questions first.
2. Create a full workbook blueprint.
3. Wait for my approval.
4. Create the sheet architecture.
5. Define all inputs and assumptions.
6. Create the formula map.
7. Write exact formulas for my platform.
8. Connect the sheets logically.
9. Add data validation and formatting rules.
10. Build a dashboard.
11. Add scenario planning.
12. Add QA checks.
13. Stress-test the workbook.
14. Create a README tab.
15. If file creation is available, build the actual spreadsheet file.
16. After building, audit the workbook and tell me what to verify manually.

Rules:
- Do not use generic placeholder formulas.
- Do not hardcode assumptions inside calculations.
- Do not mix Excel and Google Sheets syntax.
- Do not create decorative dashboards with no decision value.
- Every dashboard metric must trace back to source data.
- Every major formula must be explained.
- Every important input must have validation.
- Every model must include error checks.

Start by asking your clarifying questions.

Save that prompt. That is the one.

Final Thoughts

ChatGPT can help you build serious spreadsheets, but only if you ask for serious work.

The mistake is treating spreadsheets like tables. A real spreadsheet is a decision engine. It should take inputs, run logic, show outputs, compare scenarios, flag errors, and help someone make a better move.

That is what makes a spreadsheet valuable.

The million-dollar part is not the file. It is the decision the file helps you make.

A pricing model that prevents undercharging. A cash flow forecast that saves a business. A hiring calculator that shows when to scale. A revenue dashboard that catches a problem early. A real estate model that stops a bad deal. A client-facing calculator that helps sell a premium offer.

That is the point.

Don’t ask ChatGPT for a spreadsheet.

Ask it to build the system.

Subscribe to Academy of AI for practical prompts, workflows, and strategies that help you use AI to work smarter, build faster, and create more freedom in your real life.

Cute. But no.

That is like buying a full kitchen and only using the microwave.

Claude can do a lot more than answer random questions. It can help you think, write, plan, analyze, learn, build, edit, organize, and make better decisions. But it only gets truly useful when you stop treating it like a search bar and start treating it like a personalized work partner.

The difference is setup.

Claude has features like Projects, project instructions, profile instructions, styles, artifacts, memory, and extended thinking. Projects let you create focused workspaces with their own chat histories and knowledge bases, and project instructions let you tailor how Claude responds inside that workspace.

That matters because the best AI results do not come from magic prompts. They come from context. Claude needs to know who you are, what you are building, how you think, what you hate, what you love, and what kind of output actually helps you.

So let’s set it up like we mean it.

Here are 20 ways to actually use Claude.

1. Create Projects for Different Parts of Your Life

Do not dump your whole life into one endless Claude chat. That is how context gets messy, answers get weird, and your “business strategy” conversation starts remembering your grocery list.

Create separate Projects for your major lanes. You might have one for your business, one for writing, one for personal finance, one for travel planning, one for learning, and one for content creation. Claude Projects are designed as self-contained workspaces where you can upload documents, add context, and keep focused chats together.

The key is this: a Project is not magic memory. Claude does not automatically know every detail from every chat unless that information is added to the Project Knowledge or included in instructions. Anthropic’s own docs say context is not shared across project chats unless it is added to the project knowledge base.

Try this setup:

Create a Project for this area of my life: [business, writing, personal finance, travel, learning, etc.]

Help me decide what should belong in this Project, what files or context I should upload, what instructions I should add, and what types of chats I should keep separate.

2. Build a “User Manual” for Yourself

Claude gets better when it understands you. Most people skip this and then complain that the output feels generic. That is like hiring an assistant and refusing to explain the job.

Write a short user manual for Claude. Tell it who you are, what you do, what you are trying to build, how you like information, and what kind of responses make you want to throw your laptop into a lake.

Copy this prompt:

Help me create a personal user manual for Claude.

Ask me questions first about who I am, what I do, my goals, my work style, my communication preferences, my audience, my projects, and what I do not want in AI responses.

After I answer, turn my responses into a clear user manual I can add to my Claude Project Knowledge.

This is one of the highest-return AI moves you can make. Set it up once. Benefit every time.

3. Turn Your User Manual Into Project Instructions

Your user manual gives Claude context. Project instructions tell Claude how to behave.

That is the difference.

Project instructions should define the role Claude plays, the tone it should use, the formats you prefer, the things it should avoid, and the standards it should follow. Claude supports project instructions that apply across chats inside a Project.

Copy this prompt:

Based on my user manual below, write Project Instructions for Claude.

The instructions should tell Claude:
- Who I am
- What this Project is for
- How to communicate with me
- What tone and format to use
- What to avoid
- What quality standards to follow
- What questions to ask before complex tasks
- How to make outputs practical and specific

Write it as instructions Claude can follow. Keep it under 500 words.

Here is my user manual: [paste user manual]

Paste the final version into your Project Instructions. Now Claude has a default operating mode instead of starting every chat like a confused intern on day one.

4. Use Profile Instructions for Your Global Preferences

Project instructions are for one workspace. Profile instructions are broader.

Claude’s personalization features include profile instructions, project instructions, and styles. Profile instructions apply across your conversations, while project instructions are best for specific workflows or focused tasks.

Use profile instructions for things that are always true. For example, you might tell Claude to be concise, avoid corporate language, use plain English, ask clarifying questions before big tasks, and never bury the answer.

Copy this prompt:

Help me write account-wide profile instructions for Claude.

These should apply to all my conversations, not just one project.

I want Claude to know:
[describe your general preferences]

Write instructions that cover tone, structure, level of detail, what to avoid, and how to handle uncertainty.

This is how you stop correcting the same annoying habits over and over again.

5. Create a Custom Style From Your Own Writing

Claude can write. But without your style, it often writes like a polite robot that just discovered LinkedIn.

Fix that.

Claude lets users create custom styles from writing examples or by describing the style they want. The official docs say writing samples help Claude understand and match your preferred communication approach.

Give Claude three to five examples of your work. Then ask it to analyze the patterns. Do not just say, “Write like me.” That is too vague. Make Claude study your rhythm, sentence length, humor, vocabulary, paragraph style, and the stuff you never do.

Copy this prompt:

I want you to study my writing style so future drafts sound more like me.

Here are 3 to 5 writing samples:

Sample 1:
[paste]

Sample 2:
[paste]

Sample 3:
[paste]

Analyze my style in detail. Look at sentence length, rhythm, tone, vocabulary, humor, structure, paragraph length, openings, endings, emotional energy, and what I avoid.

Then create a reusable writing style guide I can save in Claude.

This is how you keep AI from sanding off your personality. Your weirdness is the asset.

Subscribe now

6. Feed Claude Examples of Great Outputs

Writing samples show Claude your voice. Great output examples show Claude your standards.

This is different.

If you want Claude to help with sales pages, upload sales pages you love. If you want it to write newsletters, show it newsletters that work. If you want it to create reports, show it the kind of report you would actually send.

Copy this prompt:

I am going to give you examples of outputs I like.

Your job is to analyze what makes them effective. Study the structure, pacing, format, tone, level of detail, and reader experience.

After that, create a checklist you will use whenever you help me make something similar.

Examples:
[paste examples]

Claude performs better when it can see the target. Do not make it guess.

7. Stop Using Claude Like Google

Claude is not just a place to ask, “What is this?”

That is the lowest-value use.

Ask Claude to help you think through something. Give it context, goals, constraints, and a decision to help you make. The better question is not, “What is an email funnel?” The better question is, “I sell a $99 digital product to new creators. Help me design a five-email funnel that builds trust before asking them to buy.”

See the difference? One asks for a definition. The other asks for work.

Use this format:

I am trying to accomplish: [goal]

Here is the context: [details]

Here are my constraints: [time, budget, audience, tools, experience]

Here is what I need from you: [analysis, plan, draft, decision, critique, etc.]

Ask me any missing questions first. Then help me solve it.

Context is the difference between “fine” and “holy shit, this is useful.”

8. Make Claude Interview You Before It Starts

Most bad AI output comes from missing context. Claude fills the gaps with assumptions, then you waste time fixing them.

Make it ask questions first.

This works for writing, strategy, planning, research, product creation, sales copy, travel, budgeting, and basically any task with nuance.

Copy this prompt:

Before you start, ask me the 7 most important questions you need answered to do this well.

Do not create the final output yet.

After I answer, summarize what you learned, identify any remaining assumptions, and then begin.

This one habit will instantly improve your results. It makes Claude gather the ingredients before trying to bake the cake.

9. Ask Claude to Write the Prompt for You

You do not always need to know the perfect prompt. Claude can help you write it.

This is one of the easiest power moves. Tell Claude what you want done, then ask it to design the best prompt for that outcome.

Copy this prompt:

I need Claude to help me with this task: [describe task]

Write the best possible prompt for this task.

Include:
- The role Claude should play
- The context it needs
- The exact output format
- Important constraints
- Questions it should ask first
- Quality standards for the final result

Then ask me for any missing details before running the prompt.

Prompting is a skill. Let Claude teach you the skill while doing the work.

10. Use Claude as a Sparring Partner, Not a Cheerleader

Claude is very good at helping. Sometimes too good.

If you ask it to build on your idea, it will usually build. If you ask it to improve your plan, it will usually improve. But sometimes you need the opposite. You need Claude to challenge the idea before you spend money, time, or emotional energy on it.

Use Claude to stress-test your thinking.

Copy this prompt:

Here is my idea or plan: [paste plan]

Act as a ruthless strategic sparring partner.

Find the weak points, false assumptions, missing details, unrealistic expectations, and ways this could fail. Be direct and specific.

Then do the opposite. Build the strongest possible case for why this could work.

After both sides, give me your honest recommendation and the 3 changes that would make this plan stronger.

You do not need AI to clap for you. You need AI to help you win.

Subscribe now

11. Use Extended Thinking for Hard Problems

Some tasks need quick output. Others need deeper reasoning.

Claude’s extended thinking is designed for complex tasks that benefit from more step-by-step reasoning, including math, coding, and analysis. (Claude API Docs)

Use it when the stakes are higher. Strategy, financial planning, business decisions, code architecture, legal research summaries, data analysis, and complex tradeoffs all deserve more thought.

Copy this prompt:

Think carefully before answering.

I do not need a fast answer. I need a useful one.

Analyze the problem, identify assumptions, compare options, explain tradeoffs, flag uncertainty, and then give me a clear recommendation.

Problem:
[paste problem]

Do not ask Claude to reveal hidden chain-of-thought. Ask for assumptions, tradeoffs, uncertainty, and a clear conclusion. That gets you the value without turning the answer into a messy reasoning diary.

12. Ask for Assumptions and Uncertainty

AI can sound confident even when it is guessing. That is dangerous and deeply annoying.

Build uncertainty into your prompts. Make Claude tell you what it knows, what it assumes, and what needs verification.

Copy this prompt:

Before giving me the answer, separate your response into:

1. What you know from the information I provided
2. What you are assuming
3. What you are uncertain about
4. What I should verify
5. Your best recommendation based on the current information

This is especially useful for money, health, legal, travel, business, and technical topics. Confidence is cute. Accuracy is better.

13. Control the Output Before Claude Writes Too Much

Claude will often give you more than you need. That sounds helpful until you are reading 900 words for a 30-word answer.

Tell it exactly what you want.

Length. Format. Tone. Number of options. No filler. No summary. No extra explanations.

Copy this prompt:

Answer in this format:

Length: [under 150 words / 5 bullets / 3 paragraphs / one-page plan]
Tone: [direct, warm, strategic, casual, etc.]
Format: [table, checklist, email draft, outline, decision memo, etc.]
Do not include: [preamble, summary, disclaimers, repeated context, generic advice]

Task:
[paste task]

This saves time, tokens, and your attention span.

14. Ban Preambles and Generic Filler

You do not need “Great question.” You do not need “Let me break this down.” You do not need a four-line summary of the question you just wrote.

Put that rule in your instructions.

Add this to Claude:

Do not start responses with affirmations, preambles, or restatements of my question.

Go directly to the answer.

Do not add a closing summary unless I ask for one.

Avoid generic advice. Give me specific, useful output.

This one is small but mighty. Claude gets sharper when you remove the fluff.

15. Start a New Chat When the Topic Changes

Long chats can get messy. The more you discuss, the more old context can influence new answers.

If you are switching from sales copy to travel planning, start a new chat. If you are switching from newsletter ideas to personal finance, start a new chat. Keep it inside the same Project if the broad context still matters, but stop dragging irrelevant history into unrelated work.

Use this rule:

New task, same project = new chat.

New life area = new project.

That little rule keeps Claude cleaner, faster, and less confused.

Subscribe now

16. Use Project Knowledge Like a Brain Dump With Standards

Project Knowledge is where Claude gets truly personal. You can upload documents, text, code, and other files for Claude to use as context inside that Project.

For a writing Project, upload your voice guide, past essays, headlines, brand rules, audience notes, and content pillars. For a business Project, upload offers, FAQs, customer research, product details, SOPs, and launch plans. For a learning Project, upload notes, syllabi, papers, or study goals.

Copy this prompt:

I want to build the best possible Project Knowledge base for this Claude Project.

The Project is for: [describe purpose]

Tell me:
1. What documents I should upload
2. What context I should write from scratch
3. What examples would improve output quality
4. What instructions should live in Project Instructions instead
5. What information I should avoid uploading for privacy

Claude does not need your private passwords, account numbers, or sensitive identity details. It needs useful context. Keep it smart and safe.

17. Use Artifacts for Things You Want to Keep

If Claude creates something substantial, ask for it as an Artifact.

Artifacts are designed for standalone content like documents, code snippets, websites, SVGs, diagrams, flowcharts, and interactive components. They appear in a dedicated space separate from the conversation, which makes them easier to edit, reuse, and build on later.

Use Artifacts for things like content calendars, sales pages, dashboards, calculators, landing pages, course outlines, operating manuals, and decision frameworks.

Copy this prompt:

Create this as an Artifact so I can edit and reuse it later.

I want: [document, checklist, landing page, calculator, content calendar, workflow, etc.]

Purpose: [explain purpose]
Audience: [describe audience]
Style: [describe style]
Must include: [list requirements]

Chats are for conversation. Artifacts are for assets.

18. Learn Anything With the “Explain, Test, Adjust” Method

Claude is an incredible tutor if you stop asking for textbook explanations.

Ask it to explain a concept simply, test your understanding, then adjust based on your answer. This turns learning into a conversation instead of a lecture.

Copy this prompt:

Teach me [topic] like I am smart but new to it.

Use plain English, analogies, and everyday examples.

After each section, ask me one question to test whether I understood.

If my answer is weak, explain it a different way. If my answer is strong, go one level deeper.

Keep going until I can explain the topic back without jargon.

This works for AI, investing, coding, marketing, history, science, taxes, business models, and anything else that usually gets explained by people trying to sound important.

19. Use Claude as a Clarity Coach for Real Life

Claude can help you think through messy life stuff too.

Not as therapy. Not as a replacement for support, care, or real humans. But as a structured reflection tool when your brain feels like a browser with 47 tabs open.

Use it for decisions, conflict, priorities, overwhelm, habits, work stress, creative blocks, or anything you need to untangle.

Copy this prompt:

I want to think through something.

Do not give advice right away.

First, ask me questions to understand what is happening, what I feel, what I have already tried, what I am afraid of, and what outcome I want.

After I answer, reflect back what you hear. Then identify the real decision or tension underneath the situation.

Only then give me your honest perspective and 3 next steps.

Sometimes the win is not getting an answer. It is finally understanding the real question.

20. Stress-Test a Business Idea Before You Build It

This is one of my favorite ways to use Claude.

Most people fall in love with an idea too early. Then they spend weeks building something nobody asked for. Claude can help you pressure-test the idea before it eats your time, money, and confidence.

Copy this prompt:

I have a business idea I want to stress-test before I build it.

Here is the idea:
[paste idea]

Here is the target customer:
[describe customer]

Here is how it would make money:
[explain model]

Here is why I think it could work:
[explain reasoning]

Analyze this like a sharp business strategist.

Tell me:
1. The assumptions that could be wrong
2. Why the customer might not pay
3. Who already competes with this
4. What would make the idea hard to execute
5. What proof I need before building
6. The simplest test I could run in 7 days
7. What the idea would need to become to actually work

This is how AI saves you from expensive delusion. Not by killing your ideas, but by making them stronger before you bet on them.

Bonus: Build Custom Skills for Repeat Workflows

Once you know your repeat workflows, you can go deeper with Claude Skills.

Skills are folders of instructions, scripts, and resources that Claude can load for specialized tasks. Anthropic describes them as a way to improve consistency and performance for repeatable workflows, including brand guidelines, document creation, data analysis, and personal workflows.

This is more advanced, but it is powerful. A creator could build a Skill for newsletter editing. A business owner could build one for customer support replies. A teacher could build one for lesson planning. A media founder could build one for SEO article production.

Copy this prompt:

Help me design a custom Claude Skill for a repeat workflow.

The workflow is: [describe workflow]
I use it for: [describe purpose]
The output should always include: [list requirements]
The output should never include: [list avoidances]
My style or standards are: [describe standards]
Examples of good outputs are: [paste examples]

Create the Skill instructions, required resources, example inputs, example outputs, and rules for when Claude should use this Skill.

The goal is simple: stop repeating instructions that Claude could learn once.

The Point of These Prompts

Claude is not smarter than you. It does not replace your taste, instincts, lived experience, or ambition.

But it does have patience. It can hold context. It can compare options. It can critique ideas without getting tired. It can turn messy thoughts into clean drafts. It can help you learn faster, write better, plan smarter, and make decisions with more clarity.

That is the opportunity.

Most people will keep using Claude like a slightly better Google. They will ask one-line questions, accept average answers, and wonder why AI feels overhyped.

Do not do that.

Set up Projects. Add context. Create instructions. Build your style. Ask better questions. Use Artifacts. Stress-test your ideas. Make Claude interview you before it starts. Give it examples. Teach it your standards.

This is how Claude stops feeling generic.

This is how it starts working like you.

Start Here

Do not do all 20 steps at once.

Start with three moves: create one Project, write your user manual, and turn that into Project Instructions. Then add your writing samples and one workflow you want Claude to help with this week.

That is enough.

One smart setup can change the way you work every day.

Subscribe to Academy of AI for practical prompts, workflows, and strategies that help you use AI to work smarter, create faster, and build more freedom in your real life.

Flight prices can make you feel personally attacked. One minute a ticket is $349. Five minutes later it is $812. Then the airline wants more money for a seat, a bag, a carry-on, a snack, oxygen, vibes, and whatever else they can turn into a fee.

I am exaggerating. Barely.

Here is the good news: you do not need to be a travel hacker with 19 credit cards and a spreadsheet named “Operation Travel.” You need a smarter way to compare dates, routes, fees, policies, and risk before you click buy.

That is where Claude can help.

Claude is not a magic airline loophole machine. It cannot guarantee live prices unless you are using a version with web search enabled, or you paste in current results from Google Flights, airline websites, Skyscanner, Kayak, Expedia, or another search tool. Anthropic’s documentation says Claude’s web search tool can access real-time web content and provide citations when that feature is available, but you should still verify fare prices and policies directly before booking.

Think of Claude as your travel strategy assistant. You bring the destination, dates, budget, and current flight options. Claude helps you think through the tradeoffs. It can spot cheaper date patterns, compare layovers, calculate total costs, evaluate fees, check flexibility, and make the decision feel less chaotic.

The goal is not to “beat” airlines with tricks. The goal is to book smarter.

Let’s get your next flight together.

How to Use Claude for Flight Research

Before we get into the prompts, here is the move: use Claude after you gather current flight data. Search your route first. Copy flight options, prices, fare rules, baggage policies, cancellation terms, and airport details into Claude. Then ask it to compare everything.

This is important because, as you know, flight prices change fast. A good prompt cannot fix old data. If Claude does not have live browsing in your setup, it needs you to provide current information. Give it real numbers, not vibes.

Also, do not paste private information into Claude. No passport numbers, confirmation codes, login details, birthdates, loyalty account numbers, or payment information. Claude needs travel options, not your whole identity.

1. Claude Prompt to Find the Cheapest Travel Dates

The easiest way to overpay for a flight is to get married to one exact date. Airlines love that. Flexibility is where the savings usually hide.

This prompt helps Claude compare nearby dates and explain why some combinations may be cheaper. Maybe Tuesday is better than Sunday. Maybe returning one day later avoids a demand spike. Maybe your target date falls near a holiday, conference, festival, or school break.

Use this when your dates are flexible by even a few days.

Copy this Claude prompt:

Act as a flight pricing analyst. Help me find cheaper travel dates for this trip.

Origin airport or city: [insert origin]
Destination airport or city: [insert destination]
Target departure date: [insert date]
Target return date: [insert date]
Flexible date window: [insert number of days before and after]
Travelers: [insert number]
Cabin: [economy, premium economy, business, etc.]
Current flight search results: [paste current results if Claude cannot browse]

Compare the best departure and return combinations within my flexible window. Find the 5 strongest options based on price, total travel time, airline reliability, layover quality, and convenience.

For each option, explain the dates, approximate price, travel time, likely reason it is cheaper, and the tradeoff I would make by choosing it.

End with a clear recommendation for the best value option, not just the cheapest option.

Do not chase the lowest price blindly. A $70 savings is not always worth a 9-hour layover in an airport where joy goes to die. Best value beats cheapest.

2. Claude Prompt to Compare Airports, Not Just Cities

A lot of people search one airport and call it done. That can cost real money.

Some cities have multiple airports. Some nearby airports offer cheaper flights, better schedules, or lower fees. Sometimes flying into a nearby city and taking a train, shuttle, or rideshare can save money. Sometimes it is a disaster wrapped in a discount.

This prompt helps Claude compare airport options with the full trip in mind.

Copy this Claude prompt:

Act as an airport comparison strategist. Help me find the smartest airport options for this trip.

My starting location is: [insert city or airport]
My destination is: [insert city or region]
My travel dates are: [insert dates]
My budget is: [insert budget]
My priority is: [lowest price, fastest route, least stress, best value, family-friendly, etc.]
Airports I am considering: [list airports]
Current flight options and prices: [paste results]
Ground transportation details if known: [paste train, shuttle, rideshare, parking, or rental car info]

Compare flying from and into nearby airports. Include ticket price, baggage fees if visible, airport transfer cost, total travel time, arrival convenience, risk of delays, and stress level.

Tell me which airport combination gives the best overall value and which one only looks cheap but probably is not.

This is the prompt that saves you from “cheap flight, expensive headache” energy. A lower fare means nothing if the ground transportation eats the savings.

3. Claude Prompt to Find Better Routes With Smarter Layovers

Direct flights are lovely. They are also not always worth the premium. A good layover can save money without ruining your life.

The key word is good. Not every layover is created equal. Some are short but risky. Some are long but manageable. Some require terminal changes, customs, extra security, or a sprint through an airport in shoes not built for emotional resilience.

This prompt helps Claude compare routes like a grown-up.

Copy this Claude prompt:

Act as a flight routing expert. Help me find lower-cost routes with reasonable layovers.

Origin: [insert origin]
Destination: [insert destination]
Travel dates: [insert dates]
Maximum budget: [insert amount]
Maximum total travel time: [insert hours]
Preferred layover length: [insert range]
Airports or airlines I want to avoid: [insert if any]
Current route options: [paste options]

Find 5 possible route options, including direct flights and 1-stop or 2-stop routes if they make sense.

For each route, compare total price, total travel time, layover length, airport quality, missed-connection risk, baggage transfer risk, and overall comfort.

Label each option as best for price, best for comfort, best for speed, or best overall value.

A smart layover can save money. A dumb layover can ruin the trip before you arrive. Let Claude help you see the difference.

4. Claude Prompt to Check Promo Codes, Sales, and Real Discounts

Airline promotions are messy. Some are real. Some are expired. Some only work on specific routes. Some exclude the exact dates you need, because of course they do.

Use this prompt to make Claude verify deals instead of just collecting random coupon codes from the internet. If Claude has web search, ask for sources. If it does not, paste the promo details you found and let Claude analyze the fine print.

Copy this Claude prompt:

Act as a travel deal verification assistant. Help me verify whether these flight deals are actually useful.

Route or airline: [insert route or airline]
Travel dates: [insert dates]
Promo codes, sale pages, or deal links I found: [paste details]
My trip requirements: [baggage, seat selection, flexibility, nonstop, etc.]

For each deal, check whether it appears valid, current, and relevant to my trip. Explain the source of the deal, expiration date, eligible routes, blackout dates, fare restrictions, required booking method, and whether it applies before or after taxes and fees.

Then rank the deals by real usefulness. Ignore anything expired, suspicious, too vague, or not actually relevant to my route.

The word “sale” does not mean “good deal.” It just means someone in marketing got a calendar invite.

5. Claude Prompt to Calculate the Real Ticket Price With Fees

This is where airlines get cute.

A fare can look cheap until you add bags, seat selection, boarding fees, change fees, service fees, payment fees, and whatever else is hiding behind the checkout button. The only price that actually matters is the total.

This prompt helps Claude expose the difference between the base fare and the actual cost of getting your body and luggage to the destination.

Copy this Claude prompt:

Act as a fare and fee analyst. Help me calculate the real total cost of this flight.

Flight option: [paste airline, route, dates, fare class, and base price]
Fare rules: [paste fare details if available]
Baggage needs: [personal item, carry-on, checked bag, overweight bag, etc.]
Seat needs: [standard seat, extra legroom, sitting together, family seating, etc.]
Other needs: [priority boarding, flexibility, refundability, etc.]

Break down the full expected cost, including base fare, taxes, mandatory fees, baggage, seat selection, boarding upgrades, payment fees, service fees, and any likely add-ons.

Then compare the real total cost against these other options: [paste other flight options].

Tell me which option is cheapest after fees and which option is the best value overall.

This prompt is especially useful for budget airlines. Sometimes the “cheap” ticket is only cheap if you travel with one sock and no dignity.

Subscribe now

6. Claude Prompt to Compare Refund, Change, and Cancellation Risk

A flight is not just a price. It is a contract.

If your plans change, the cheapest ticket can become the most expensive mistake. Some fares are flexible. Some are refundable. Some turn into credits. Some come with restrictions that make you wonder if a lawyer wrote them during a breakup.

The U.S. Department of Transportation says domestic airlines generally are not required to compensate passengers for delays or cancellations unless the passenger is involuntarily bumped from an oversold flight, though separate refund rules can apply when flights are canceled or significantly changed. (Department of Transportation)

Use this prompt before you book anything nonrefundable.

Copy this Claude prompt:

Act as a travel policy risk analyst. Help me compare the financial risk of these flight options if my plans change.

Trip details: [insert route and dates]
Flight options: [paste 2 to 5 options]
Refund rules: [paste rules]
Change rules: [paste rules]
Cancellation rules: [paste rules]
No-show rules: [paste rules]
My likelihood of changing plans is: [low, medium, high]
My priority is: [cheapest price, flexibility, refundability, low stress, etc.]

Compare each option based on what I would lose if I cancel, change dates, miss a flight, or need a refund.

Create a simple table showing the ticket price, flexibility level, worst-case loss, best-case refund or credit, and hidden clauses to verify.

End with this format:
If I care most about price, choose: [option]
If I care most about flexibility, choose: [option]
If I want the best balance, choose: [option]

This is not sexy travel planning. This is adult travel planning. And adult travel planning saves money.

7. Claude Prompt to Write a Polite Price Match or Goodwill Request

Not every airline or booking platform will price match. Many will not. But sometimes you can ask for a fare adjustment, goodwill credit, refund review, voucher, baggage help, or loyalty benefit.

The trick is to be clear, polite, specific, and not weirdly aggressive. Customer support agents are people. Treat them like humans and make your request easy to understand.

Use this when you found a better price, experienced a service issue, or want to ask whether a current policy helps you.

Copy this Claude prompt:

Act as a polite but confident customer support writing assistant. Help me draft a travel request email.

Company or airline: [insert name]
My situation: [found a lower fare, need a refund review, want a goodwill credit, had a service issue, etc.]
Original booking details: [do not include confirmation number unless you want to add it later]
Original price: [insert price]
Competing or updated price: [insert price]
Relevant policy details: [paste policy if available]
My loyalty history: [optional]
What I want: [price adjustment, credit, refund review, fee waiver, seat help, baggage help, etc.]

Write a short, respectful email that explains the situation, includes the relevant details, asks for a specific outcome, and keeps the tone warm but firm.

Give me 3 versions:
1. Very polite
2. Firm but professional
3. Short customer support chat version

This prompt will not make every company say yes. But it will help you ask like someone who has their shit together.

8. Claude Prompt to Evaluate Risky “Travel Hacks” Before You Try Them

Some flight hacks are harmless. Some are risky. Some can violate airline rules. Hidden-city ticketing, also called point-beyond ticketing, is one of those tactics people love to hype online.

Here is the honest version: you should understand the risk before even considering it. United’s Contract of Carriage says hidden-cities or point-beyond ticketing is prohibited, and Delta’s Contract of Carriage also lists hidden-city or point-beyond ticketing among prohibited practices intended to circumvent published fares. (United Airlines)

So this prompt is not “how to do hidden-city ticketing.” It is “help me understand why this could blow up in my face.”

Copy this Claude prompt:

Act as an aviation policy explainer. I want to understand the risks of hidden-city ticketing and other risky flight booking tactics before making a decision.

My route is: [insert origin and destination]
The cheaper itinerary I am considering is: [paste itinerary]
The airline is: [insert airline]
My baggage situation is: [personal item only, carry-on, checked bag, etc.]
My loyalty status with the airline is: [none, basic member, elite, etc.]
My risk tolerance is: [low, medium, high]

Explain whether this tactic appears to violate airline policies. Do not give me instructions for exploiting the policy. Instead, explain the risks, including canceled return flights, checked baggage problems, loyalty account issues, rebooking problems, and contract-of-carriage concerns.

Then suggest safer legal alternatives that could reduce the fare, such as date flexibility, nearby airports, open-jaw routing, one-way comparisons, fare alerts, or different cabin/fare classes.

The best travel hack is not the one that gets you banned from your favorite airline. Let’s not be dramatic for $86.

9. Claude Prompt to Plan a Multi-City Trip Without Wasting Money

Multi-city trips can be amazing. They can also become expensive chaos if you visit cities in the wrong order.

Sometimes swapping the order saves money. Sometimes flying into one city and out of another is smarter. Sometimes a train or budget regional carrier makes more sense than forcing every leg through one airline.

This prompt helps Claude design the route before you book.

Copy this Claude prompt:

Act as a multi-city travel planner and flight strategy assistant. Help me design the smartest route for this trip.

Starting city: [insert city]
Cities I want to visit: [list cities]
Trip length: [insert number of days or weeks]
Preferred travel dates: [insert dates]
Budget: [insert budget]
Travel style: [fast-paced, relaxed, luxury, budget, family, solo, etc.]
Must-see priorities: [insert priorities]
Current flight or train prices I found: [paste if available]

Create 3 possible route orders. For each one, include suggested city order, number of days in each place, recommended airports or train connections, estimated transportation costs, total travel time, and why this order may save money or reduce stress.

Then tell me which route is best for price, which is best for convenience, and which is best overall.

This is where Claude becomes your “wait, why are we flying backward across Europe?” friend. Very useful. Mildly judgmental if prompted correctly.

10. Claude Prompt to Estimate the Real Total Trip Cost

A flight can be cheap and still make the trip expensive.

A late arrival can mean a pricier transfer. A far airport can mean a $90 rideshare. A “deal” with no bag included can cost more than the regular fare. A red-eye can save money but wreck the first day of your trip.

This prompt helps Claude compare the full travel cost, not just the ticket.

Copy this Claude prompt:

Act as a total trip cost analyst. Help me compare the real cost of these flight options.

Destination: [insert destination]
Travel dates: [insert dates]
Flight options: [paste options]
Travelers: [insert number]
Baggage needs: [insert details]
Arrival times: [insert arrival times]
Departure times: [insert departure times]
Airport transfer options and costs: [paste if known]
Hotel or lodging details: [insert if arrival time affects lodging]
Local transportation needs: [insert details]
My priority is: [lowest total cost, least stress, best arrival time, best value, etc.]

For each flight option, estimate the total trip cost including airfare, baggage, seat fees, airport transfers, likely local transport, extra hotel costs if relevant, food during layovers, and time/stress tradeoffs.

Then rank the options by:
1. Lowest total cost
2. Best value
3. Lowest stress

Tell me which flight I should book based on my stated priority.

This is the prompt that keeps you from celebrating a cheap ticket that secretly costs more by the time you get to the hotel.

Bonus Claude Prompt: Build a Flight Booking Decision Matrix

When you are stuck between three decent options, stop staring at tabs like the answer will reveal itself through emotional fatigue. Use a decision matrix.

This prompt helps Claude score each option based on what’s important to you.

Copy this Claude prompt:

Act as a travel decision coach. Help me choose between these flight options.

My options are: [paste flight options]
My priorities are:
Price importance: [1 to 10]
Travel time importance: [1 to 10]
Flexibility importance: [1 to 10]
Baggage importance: [1 to 10]
Comfort importance: [1 to 10]
Low-stress travel importance: [1 to 10]

Create a weighted decision matrix. Score each flight option from 1 to 10 for price, schedule, travel time, layovers, fees, flexibility, comfort, and risk.

Then calculate the best overall option based on my priorities. Explain the recommendation in plain English and point out any deal-breakers I should verify before booking.

This is the grown-up version of “which tab feels best?” Use it.

The Smart Flight Booking Formula

You do not save money on flights by refreshing the same search 37 times and hoping the airline gets generous.

You save money by changing the question.

Instead of asking, “What is the cheapest ticket?” ask, “What is the best total value for my dates, route, baggage, flexibility, and actual trip cost?”

That question changes everything.

Claude can help you compare nearby dates, alternate airports, layover options, promo codes, baggage fees, refund rules, risky tactics, multi-city routes, and real total costs. It can turn flight research from a chaotic tab explosion into a clean decision.

That does not mean you should trust AI blindly. Always verify final prices, baggage rules, refund terms, and cancellation policies directly with the airline or booking platform before you pay. The U.S. Department of Transportation says passengers may be entitled to refunds in specific situations, including canceled or significantly changed flights, and fees for services not provided, but the details are important. (Department of Transportation)

Use Claude to think smarter. Use official sources to confirm. Then book like someone who knows what they are doing.

Start With One Prompt Before Your Next Flight

Do not run all 10 prompts unless you are planning a big trip or you enjoy turning travel research into a competitive sport. Start with the one that matches your biggest pain point.

If your dates are flexible, use the date prompt. If the fare looks suspiciously cheap, use the fee prompt. If your plans might change, use the policy prompt. If you are visiting multiple cities, use the route prompt. If you are stuck between options, use the decision matrix.

One prompt can save you money. More importantly, it can save you from booking a flight that looks cheap and feels terrible.

That is the real travel win.

Subscribe to Academy of AI for practical prompts, workflows, and strategies that help you use AI to work smarter, spend smarter, and create more freedom in your real life.

Retirement planning sounds boring until you realize what it actually means.

It means freedom. It means options. It means not waking up at 67 and realizing your future self got stuck with every bill your present self avoided. That is not cute. That is expensive.

Most people do not avoid retirement planning because they are irresponsible. They avoid it because it feels like a giant money maze. You have 401(k)s, IRAs, Roth accounts, brokerage accounts, inflation, tax brackets, Social Security, market risk, withdrawal rates, and enough acronyms to make a normal person want to scream into a throw pillow.

Claude can help.

Not because Claude is your financial advisor. It is not. It cannot replace a fiduciary planner, CPA, tax professional, or investment advisor who knows your full situation. But Claude can help you organize your numbers, understand the moving parts, compare scenarios, and walk into professional conversations with better questions.

That matters. Retirement planning has rules that change, and details matter. The IRS updates retirement plan and IRA contribution limits, Social Security claiming depends on your birth year and claiming age, and investment planning needs to account for time horizon, risk tolerance, diversification, and inflation. (IRS)

Before you use these prompts, do one important thing: protect your private information. Do not paste Social Security numbers, account numbers, login details, addresses, full tax IDs, or anything that could expose your identity. Redact the sensitive stuff. Claude needs numbers and context, not your entire financial soul.

Now let’s build a smarter retirement plan.

How to Use Claude for Retirement Planning

The key is to treat Claude like a planning assistant, not a magic oracle. Give it clean inputs, ask it to label assumptions, and make it show the math. Then ask follow-up questions until the plan feels clear.

You can use Claude to calculate savings targets, compare account strategies, review your portfolio mix, stress-test your withdrawal plan, and understand Social Security options. You can also ask it to turn everything into a checklist for your CPA or financial advisor.

That is where AI becomes useful. It does not replace your judgment. It helps you stop guessing.

1. The Retirement Blueprint Prompt

This is the starting point. Before you obsess over Roth conversions, ETFs, or Social Security timing, you need the full picture. How much do you have? How much do you need? How far away is retirement? What accounts are you using? What gap are you trying to close?

This prompt helps Claude turn scattered numbers into a clear retirement roadmap. It gives you a savings target, account priority plan, and decade-by-decade strategy. This is the kind of clarity most people never create because they assume retirement planning has to be painful. It does not.

Copy this Claude prompt:

Act as a retirement planning education assistant. Help me build a clear retirement blueprint. This is for education and planning only, not final financial advice.

Before you create the plan, ask me up to 10 clarifying questions if any important details are missing.

Here is my situation:

Age: [insert age]
Country and state or region: [insert location]
Annual income: [insert income]
Current retirement savings: [insert amount]
Current accounts: [401(k), IRA, Roth IRA, brokerage, pension, HSA, etc.]
Account balances: [insert balances]
Current monthly contribution: [insert amount]
Employer match: [insert match details]
Target retirement age: [insert age]
Desired monthly retirement income: [insert amount]
Current monthly expenses: [insert amount]
Dependents: [insert number]
Debt: [insert debt details]
Current emergency fund: [insert amount]
Risk tolerance: [conservative, moderate, aggressive]
Other income sources: [rental income, business income, pension, etc.]

Build me a retirement blueprint that includes:

1. My estimated retirement savings goal in today's dollars and future inflated dollars
2. The monthly amount I may need to save to reach that goal
3. Which accounts I should prioritize and why
4. How my employer match should fit into the plan
5. How inflation affects my retirement income target
6. A decade-by-decade plan from now until retirement
7. What my portfolio should generally focus on during each decade
8. The biggest risks in my current plan
9. A simple 12-month action plan
10. Questions I should ask a fiduciary financial advisor before making final decisions

Show your assumptions clearly. Use plain English. Be specific, but do not pretend the numbers are guaranteed.

Use this first. Seriously. This prompt creates the foundation for everything else. Without a blueprint, every retirement decision feels random.

2. The Tax-Smart Retirement Strategy Prompt

Taxes can quietly wreck a retirement plan if you ignore them. The question is not just, “How much should I save?” It is also, “Where should I save it, when should I pay taxes, and how should I withdraw money later?”

That is where traditional versus Roth accounts, Roth conversion windows, backdoor Roth strategies, taxable brokerage accounts, required distributions, and state taxes come into the picture. Contribution limits and tax rules change, so use this prompt as a planning tool, not a final tax answer. The IRS maintains current retirement plan limits and lists common retirement account types, so always verify the latest rules before acting. (IRS)

Copy this Claude prompt:

Act as a retirement tax planning education assistant. Help me think through tax-smart retirement strategies. This is for planning and discussion only, not final tax advice.

My country and state or region: [insert location]
Filing status: [single, married filing jointly, etc.]
Age: [insert age]
Annual gross income: [insert income]
Income type: [salary, freelance, business, investments, mixed]
Current estimated tax bracket: [insert bracket or say unknown]
Current retirement accounts: [401(k), traditional IRA, Roth IRA, HSA, brokerage, SEP IRA, Solo 401(k), etc.]
Current annual contributions: [insert contribution amounts]
Employer match: [insert details]
Expected retirement age: [insert age]
Expected retirement income sources: [portfolio, Social Security, pension, rental income, business income, etc.]
Expected retirement tax bracket: [if known, insert estimate]
My main goal: [lower taxes now, lower taxes later, flexibility, early retirement, wealth transfer, etc.]

Create a tax-smart retirement strategy that explains:

1. Whether traditional or Roth contributions may make more sense for me right now
2. What assumptions affect that recommendation
3. Whether a Roth conversion strategy might be worth exploring
4. Whether a backdoor Roth may be relevant to my situation
5. Which tax-advantaged accounts I might be underusing
6. How taxable brokerage accounts could fit into the plan
7. A possible withdrawal order in retirement
8. Tax risks or rule changes I should verify
9. A prioritized action list for this year
10. Questions to bring to a CPA or qualified tax professional

Do not invent current contribution limits. If limits matter, tell me exactly what I need to verify with the IRS or my tax professional.

This prompt is a sanity saver. It helps you stop making retirement decisions one account at a time. You start seeing the whole tax picture.

3. The Investment Allocation Prompt

Your retirement accounts need a job. They are not just random buckets where money goes to vibe. Your investments should match your time horizon, risk tolerance, goals, and need for liquidity.

Investor.gov explains that time horizon matters because people with longer timelines may tolerate more volatility, while shorter timelines often call for less risk. It also notes that diversification can help manage risk, but it cannot guarantee you will avoid losses. (Investor.gov)

This prompt helps Claude review your current investment mix and build a glide path. That means your portfolio can gradually shift as you move closer to retirement. Less chaos. More intention.

Copy this Claude prompt:

Act as an investment allocation education assistant. Help me review my retirement portfolio and create a long-term allocation plan. This is for education only, not personalized investment advice.

My age: [insert age]
Target retirement age: [insert age]
Total investable assets: [insert amount]
Current accounts: [401(k), IRA, Roth IRA, brokerage, HSA, etc.]
Current holdings and percentages: [paste holdings, fund names, tickers, and allocation percentages]
Monthly contribution amount: [insert amount]
Risk tolerance: [conservative, moderate, aggressive]
Emergency fund status: [insert details]
Time horizon: [insert years until retirement]
Any major upcoming expenses: [home, tuition, business, healthcare, etc.]
My investing preference: [simple index funds, target-date funds, ESG, dividend focus, etc.]

Analyze my current portfolio and explain:

1. What looks strong
2. What looks risky or overconcentrated
3. Whether my allocation matches my age, goals, and risk tolerance
4. A suggested target allocation by asset class
5. How that allocation might shift every 5 years until retirement
6. How to think about stocks, bonds, cash, and international exposure
7. Whether my accounts have unnecessary overlap
8. How often I should consider rebalancing
9. A simple rebalancing checklist
10. Low-cost fund categories I could research, plus example tickers to verify myself

Do not present example funds as recommendations. Label them as research examples only. Tell me what fees, expense ratios, risks, and tax considerations I should verify before making changes.

This is the prompt to use when your portfolio feels like a junk drawer. It helps you see whether your investments actually match your life.

4. The Retirement Risk Stress-Test Prompt

A retirement plan that only works when everything goes perfectly is not a plan. It is a fantasy with a spreadsheet.

You need to know what happens if the market drops early in retirement. You need to know how inflation affects your buying power. You need to understand withdrawal risk, healthcare risk, longevity risk, and what happens if your expenses rise.

This prompt asks Claude to stress-test your plan. It will not produce a perfect actuarial model, but it can help you see where the plan feels fragile.

Copy this Claude prompt:

Act as a retirement risk education assistant. Help me stress-test my retirement plan. This is a scenario exercise, not a guarantee or final financial advice.

Planned retirement age: [insert age]
Current age: [insert age]
Expected retirement portfolio: [insert amount]
Current portfolio allocation: [stocks, bonds, cash, real estate, etc.]
Expected monthly withdrawal need: [insert amount]
Expected annual expenses in retirement: [insert amount]
Expected Social Security or pension income: [insert amount and start age]
Expected retirement length: [insert years]
Healthcare assumptions: [insert known costs or say unknown]
Inflation assumption: [insert rate or ask Claude to model 3 rates]
My risk tolerance in retirement: [low, moderate, high]

Run a retirement risk stress test. Include:

1. What happens if the market drops 30% to 40% in my first retirement year
2. How sequence-of-returns risk could affect me
3. Whether my withdrawal rate looks conservative, moderate, or aggressive
4. How my plan changes under good, average, and poor market scenarios
5. How inflation at 3%, 4%, and 5% affects my purchasing power
6. How long my money might last under each scenario
7. What expenses or assumptions create the most risk
8. Guardrails I could use if markets perform poorly
9. Cash buffer or income floor strategies to consider
10. A specific risk reduction plan I can discuss with a fiduciary advisor

Clearly label every assumption. Do not promise that I will not run out of money. Show me what needs deeper professional analysis.

This prompt is not the most glamorous one. It might be the most important. Retirement planning is not just about growth. It is about resilience.

5. The Social Security Strategy Prompt

Social Security is one of the biggest retirement decisions many people make, and claiming timing matters. The SSA says you can compare retirement estimates at 62, full retirement age, and 70 through its calculators. It also explains that claiming before full retirement age reduces benefits, while delayed retirement can increase benefits up to age 70. (Social Security)

For married couples, things can get even more layered. Spousal benefits may be available, but early claiming can reduce them, and the maximum spouse benefit is generally tied to 50% of the worker’s benefit at full retirement age. (Social Security)

This prompt helps you understand the tradeoffs before you make a claiming decision.

Copy this Claude prompt:

Act as a Social Security retirement income education assistant. Help me compare claiming strategies. This is for education only, not final claiming advice.

My age: [insert age]
My full retirement age: [insert FRA if known]
My estimated benefit at age 62: [insert amount]
My estimated benefit at full retirement age: [insert amount]
My estimated benefit at age 70: [insert amount]

If married:
My spouse’s age: [insert age]
My spouse’s full retirement age: [insert FRA if known]
Spouse benefit at age 62: [insert amount]
Spouse benefit at full retirement age: [insert amount]
Spouse benefit at age 70: [insert amount]

Health status: [good, average, below average]
Family longevity history: [brief description]
Planned retirement age: [insert age]
Portfolio amount: [insert amount]
Other income sources: [pension, rental income, business income, etc.]
Monthly income need in retirement: [insert amount]

Compare Social Security claiming strategies. Include:

1. Claiming early
2. Claiming at full retirement age
3. Delaying until age 70
4. If married, one spouse claims earlier while one delays
5. If married, both claim at full retirement age
6. If married, both delay where possible

For each strategy, explain the monthly income, estimated lifetime income, break-even ages, survivor considerations, portfolio withdrawal impact, and tax questions to verify.

Also explain spousal benefits in plain English and tell me what information I should confirm directly with the Social Security Administration before making a decision.

This prompt helps you slow down. Social Security is not just about getting checks earlier. It is about lifetime income, survivor planning, tax impact, and how much pressure your portfolio has to carry.

Bonus Prompt: Turn This Into Questions for a Professional

This is the prompt I wish more people used. Once Claude gives you a plan, ask it to turn that plan into questions for a human professional.

That is how you use AI responsibly. You do not outsource your future to a chatbot. You use the chatbot to get smarter before the meeting.

Copy this Claude prompt:

Review everything we have created about my retirement plan so far. Turn it into a meeting prep document for a fiduciary financial advisor, CPA, or retirement specialist.

Include:

1. A one-page summary of my situation
2. My biggest retirement goals
3. My current savings and account setup
4. The main assumptions in the plan
5. The biggest risks or unknowns
6. The top 10 questions I should ask
7. Documents I should bring
8. Decisions I should not make without professional review
9. Potential tax issues to verify
10. A clean action checklist after the meeting

Make it clear, organized, and easy to bring into a real appointment.

This is where Claude becomes a power tool. It helps you stop walking into financial conversations confused, embarrassed, or underprepared.

Subscribe now

What Claude Can and Cannot Do

Claude can help you organize your retirement numbers. It can help you compare options, understand concepts, draft questions, and see gaps in your plan. It can turn financial chaos into a clean first draft.

But Claude cannot know everything about your life unless you tell it. It cannot guarantee market returns. It cannot verify your full tax situation. It cannot understand every state, country, employer plan, pension rule, beneficiary issue, or estate planning detail without accurate inputs.

So use it wisely. Let Claude help you get clear. Then verify the important stuff with qualified professionals and official sources.

That is not less powerful. That is how adults with money build actual security.

Start With the Blueprint

Do not run all five prompts today unless you want to turn your afternoon into a retirement planning dungeon. Start with the first prompt. Build the blueprint. Then move through the tax, investment, risk, and Social Security prompts one at a time.

The goal is not to become a financial expert overnight. The goal is to stop avoiding your future.

Retirement planning is not about being rich, boring, or perfect. It is about building options. It is about making sure future you has choices. It is about creating a life where work becomes something you choose, not something you are trapped inside forever.

That is freedom.

And yes, AI can help you plan for it.

Subscribe to Academy of AI for practical prompts, workflows, and strategies that help you use AI to work smarter, build faster, and create more freedom in your real life.

Money stress loves confusion. It grows when you avoid your bank statement, ignore your subscriptions, guess where your paycheck went, and tell yourself you will “figure it out later.” Later gets expensive.

Claude will not magically fix your finances while you sip coffee and pretend your credit card balance is a personality trait. But Claude can help you see what is happening, organize the mess, ask better questions, and build a plan that feels less terrifying.

That matters, because most people do not need more shame around money. They need clarity. They need a simple way to look at their income, spending, debt, goals, and choices without spiraling.

That is what these prompts are for.

Use them to turn Claude into a money clarity assistant. Not your banker. Not your accountant. Not your investment advisor. A smart assistant that helps you understand your own numbers, find patterns, compare options, and prepare better questions before making real decisions.

A quick safety note before we get into it: never paste private information like account numbers, Social Security numbers, full addresses, card numbers, tax IDs, or login details into any AI tool. Redact anything sensitive first. Also, use Claude for education and organization, not final financial, tax, legal, or investment decisions. The CFPB recommends tracking your income and expenses to understand your money patterns before making changes, and that is exactly the kind of clarity these prompts are built to support. (Consumer Financial Protection Bureau)

How to Use These Claude Prompts for Personal Finance

The prompts below work best when you give Claude real context. That means your income range, expense categories, goals, country, debt details, and timeline. You do not need to share every private detail. You can summarize.

For example, instead of pasting a full bank statement, you can paste a cleaned list of transactions with merchant names, dates, categories, and amounts. Instead of giving your exact address or employer, say your country, state, job type, and income structure. Clean data is safer and usually more useful.

After Claude responds, do not accept everything blindly. Ask follow-up questions. Ask it to explain the math. Ask it what assumptions it made. Ask it what could go wrong. AI can help you think, but your judgment still runs the show.

1. Analyze Your Spending Without the Shame Spiral

This prompt helps you understand where your money is actually going. Not where you think it is going. Not where you wish it were going. The real numbers.

Use this when you have a list of monthly expenses and want Claude to find patterns, spending leaks, recurring charges, and realistic ways to save. This is not about cutting every joy out of your life. That is boring and unsustainable. This is about finding the expenses that do not match your priorities.

Copy this Claude prompt:

Act as a personal finance coach and expense analyst. I am going to paste a redacted list of my monthly expenses.

My goal is: [save more money, reduce spending, pay off debt, build an emergency fund, understand my habits, etc.]
My monthly income is: [insert income or say unknown]
My expenses are: [paste cleaned expense list]

Please analyze my expenses and group them into clear categories. Show me the total spent in each category, the percentage of my spending each category represents, my top 10 largest expenses, recurring charges, possible fees, and any spending patterns I should notice.

Then give me a realistic action plan with 5 specific ways I could save money this month without making my life miserable. Include what to cut, what to negotiate, what to cancel, and what to keep because it supports my quality of life.

This prompt works because it removes the emotional fog. Money gets less scary when you can see it clearly. You may find one subscription you forgot, one habit that quietly got expensive, or one category that needs a boundary.

2. Decode a Bank or Credit Card Statement

Bank statements are not exactly written to make you feel powerful. They are full of dates, codes, fees, merchants, balances, and transactions that can blur together fast.

This prompt helps Claude translate a statement into plain English. It is especially useful if you want to understand your biggest expenses, spot weird charges, review fees, or summarize a messy month.

Copy this Claude prompt:

Act as a financial statement translator. I am going to paste a redacted bank or credit card statement. Do not assume anything is fraud. Instead, flag anything that looks unusual and tell me what I should verify.

Statement type: [bank account, credit card, business account, etc.]
Month or date range: [insert date range]
My main goal is: [understand spending, find fees, spot subscriptions, check for unusual charges, etc.]
Redacted statement: [paste cleaned statement text]

Please explain this statement in simple language. Include total money in, total money out, ending balance if shown, my 10 largest transactions, recurring payments, fees or interest charges, possible duplicate charges, and anything that looks unusual.

Then give me a short monthly summary and 5 questions I should ask myself or my bank before making decisions.

Use this prompt like a flashlight. It will not know your full life, but it can help you notice what deserves attention. That alone can save you money, time, and a few “wait, what the hell is this charge?” moments.

3. Build a Budget That Fits Your Actual Life

A budget should not feel like punishment. A good budget gives your money a job before chaos grabs it. It helps you decide what matters, what can wait, and what needs to stop draining your account.

This prompt uses your real numbers to create a budget that balances needs, wants, savings, debt, and goals. You can ask Claude to use the 50/30/20 rule as a starting point, but the key is adapting it to your reality.

Copy this Claude prompt:

Act as a practical budgeting coach. Help me create a monthly budget that fits my real life.

My monthly take-home income is: [insert amount]
My country or region is: [insert country or region]
My fixed expenses are: [rent, utilities, insurance, debt payments, subscriptions, etc.]
My variable expenses are: [groceries, dining, shopping, transportation, pets, travel, etc.]
My current savings are: [insert amount]
My debts are: [insert debts or say none]
My main financial goal is: [emergency fund, debt payoff, saving for a home, investing, travel, etc.]

Build a monthly budget with current spending vs target spending. Use needs, wants, savings, and debt categories. Show me where my current numbers are out of balance and what I should adjust first.

Then tell me how much I should save each month to reach my goal in [insert timeline], and give me a 30-day budget reset plan.

This is where money starts to feel less random. The goal is not perfection. The goal is to make your money easier to understand and harder to accidentally waste.

4. Create a Debt Payoff Plan That Makes Sense

Debt can feel like a monster when everything is floating around in your head. The fastest way to shrink the monster is to list the numbers and choose a strategy.

Two common approaches are the snowball method, which focuses on smaller balances first, and the highest-interest method, often called avalanche, which focuses on the most expensive debt first. The CFPB describes both as basic debt reduction strategies, and Claude can help compare them for your specific situation. (Consumer Financial Protection Bureau)

Copy this Claude prompt:

Act as a debt payoff strategist. Help me compare the debt snowball method and the debt avalanche method for my specific situation.

Here are my debts:
Debt 1: [name, balance, interest rate, minimum payment]
Debt 2: [name, balance, interest rate, minimum payment]
Debt 3: [name, balance, interest rate, minimum payment]

My extra monthly amount available for debt payoff is: [insert amount]
My goal is: [pay off debt fastest, save the most interest, get emotional wins, improve cash flow, etc.]

Create two payoff plans: one using the snowball method and one using the avalanche method. For each plan, show the payment order, estimated payoff timeline, estimated interest impact, first 3 months of payments, and pros and cons.

Then recommend the best strategy for me based on math, motivation, and cash flow.

This prompt is powerful because it gives you options. Some people need the math win. Some people need the emotional win. The best plan is the one you will actually follow.

5. Compare Financial Products Without Getting Played

Financial products can look shiny on the surface. A credit card offers rewards. A loan promises a low payment. A savings account advertises a big rate. A payment plan says “easy.” Then the fees, penalties, teaser terms, and fine print show up.

Claude can help you compare financial products in plain English. It will not replace reading the actual terms, but it can help you know what to look for before signing anything.

Copy this Claude prompt:

Act as a financial product comparison analyst. Help me compare these options clearly and honestly.

My profile is: [age range, income range, country, credit situation if relevant, risk tolerance, goal]
My goal is: [borrow money, save money, earn interest, choose a credit card, refinance, etc.]
Products I am comparing: [paste product names, terms, links, or summaries]

Create a comparison table with the following categories: interest rate or return, fees, penalties, promotional terms, hidden costs to look for, flexibility, risks, who this product is best for, and who should avoid it.

Then explain the real benefits versus the marketing claims. End with a recommendation, the top 5 questions I should ask before choosing, and any red flags I should verify with the provider.

This prompt helps you slow down before you say yes. That is often where the money is. Not in being paranoid, but in being awake.

Subscribe now

6. Decide Whether to Rent or Buy

Renting can feel like “throwing money away,” but buying can come with hidden costs that people conveniently forget when they are romanticizing countertops. Mortgage payments are only one piece of the picture.

This prompt helps Claude compare renting and buying with your real numbers. It should include mortgage costs, maintenance, taxes, closing costs, insurance, flexibility, liquidity, and how long you plan to stay.

Copy this Claude prompt:

Act as a rent-vs-buy decision coach. Help me compare renting and buying using real numbers and practical tradeoffs.

My current rent is: [insert amount]
The property price is: [insert amount]
My down payment available is: [insert amount]
Estimated mortgage rate is: [insert rate]
Loan term is: [insert years]
Monthly income is: [insert amount]
How long I plan to live there: [insert years]
My country or region is: [insert country or region]
Other details: [HOA, taxes, insurance, maintenance, closing costs, etc.]

Compare renting vs buying over 3, 5, and 10 years. Include monthly cost estimates, upfront costs, hidden ownership costs, flexibility, liquidity, risk, and lifestyle factors.

Then give me a clear recommendation based on the numbers and tell me what information I still need before making a final decision.

This is not just a math decision. It is a life decision. Claude can help with the numbers, but you still need to think about freedom, stability, stress, and how long you actually want to stay put.

7. Explain Any Financial Concept Like You Are Smart, But New

Financial education often sounds like someone swallowed a textbook and then got mad at you for not understanding compound interest. We are not doing that here.

This prompt helps Claude explain financial concepts in plain English without talking down to you. Use it for APR, APY, credit utilization, compound interest, index funds, inflation, refinancing, escrow, tax deductions, or anything else that makes your brain briefly leave the room.

Copy this Claude prompt:

Explain this financial concept to me clearly: [insert concept]

Assume I am smart, but new to this topic. Do not use unnecessary jargon. Explain what it means, how it works, why it matters, and how it could affect my money.

Include one simple example with numbers, one situation where this concept can help me, one situation where it could hurt me, the biggest myth people believe about it, and 5 questions I should ask before making a decision related to it.

This is financial literacy without the ego. Once you understand the language, you can make better decisions. Nobody gets to intimidate you with vocabulary anymore.

8. Simulate Investment Scenarios Without Pretending the Future Is Guaranteed

Investing conversations can get weird fast. Some people act like every market dip is the apocalypse. Others act like every asset only goes up. Both are exhausting.

Claude can help you compare scenarios, but it should never pretend it can predict the future. Investment risk is real, inflation affects purchasing power, and diversification can help manage risk without guaranteeing protection from losses. Investor.gov explains diversification as spreading money across investments, while also noting it cannot guarantee investments will not suffer in a market drop. Investor.gov also notes that inflation reduces purchasing power, which matters when comparing investments to cash savings. (Investor)

Copy this Claude prompt:

Act as an investment education assistant. Help me think through possible scenarios, but do not present predictions as guarantees.

I am considering investing: [insert amount]
Investment type or asset: [index fund, ETF, stock, bond, real estate, crypto, retirement account, etc.]
Time horizon: [insert timeline]
My risk tolerance is: [low, medium, high]
My current savings situation is: [emergency fund, debt, cash reserves, etc.]
My country or region is: [insert country or region]

Create 3 scenarios: optimistic, realistic, and pessimistic. Clearly label all assumptions. Show possible ending values, potential downside, liquidity concerns, fees to research, tax considerations to verify, and how inflation could affect real purchasing power.

Compare this against leaving the money in a traditional savings account. End with risk warnings, questions to ask a licensed financial advisor, and what information I need before deciding.

This prompt is not about chasing returns. It is about thinking like a grown-up before moving money. Sexy? Maybe not. Useful? Absolutely.

9. Prepare for Taxes Without Panic

Taxes are country-specific, situation-specific, and deeply allergic to vague advice. Claude can help you get organized, but it should not be your final tax authority.

Use this prompt to create a tax prep checklist, organize deductible expenses, prepare questions for a professional, and build better recordkeeping habits for next year. The IRS says good records help track deductible expenses, prepare tax returns, and support items reported on those returns, which is exactly why organizing early matters. (IRS)

Copy this Claude prompt:

Act as a tax organization assistant. Help me prepare for a conversation with a qualified tax professional. Do not give final tax advice.

My country and state or region are: [insert location]
My work situation is: [employee, freelancer, creator, business owner, investor, etc.]
My income types are: [salary, freelance, business, dividends, royalties, rental income, etc.]
My possible deductible expenses are: [list expenses]
My financial goal is: [reduce stress, stay compliant, organize records, understand deductions, plan for next year, etc.]

Create a tax prep checklist for me. Include documents to gather, expenses to organize, deductions or credits I should ask a professional about, questions to bring to my tax preparer, and a simple monthly recordkeeping system for next year.

Also tell me what not to assume and what I should verify based on my local tax rules.

This prompt can save you from the “April panic pile,” which is where receipts go to die. Future you deserves better. Future you wants folders.

10. Build a 12-Month Personal Money Roadmap

A money plan should not just be “spend less.” That is too vague to be useful. You need a roadmap with specific goals, timelines, habits, and metrics.

This prompt helps Claude turn your current financial life into a quarterly plan. It is great when you know you want to do better, but you need a clear next step.

Copy this Claude prompt:

Act as my personal financial roadmap coach. Help me build a 12-month money plan that is realistic and specific.

My age range is: [insert age range]
My monthly take-home income is: [insert amount]
My debts are: [insert debts]
My current savings are: [insert amount]
My main financial goal is: [emergency fund, debt payoff, investing, buying a home, starting a business, travel, etc.]
My biggest money challenge is: [overspending, inconsistent income, debt, no savings, unclear goals, etc.]
My country or region is: [insert country or region]

Create a 12-month roadmap divided into 4 quarters. For each quarter, give me one main objective, 3 specific actions, the metric I should track, the habit I should build, and one mistake to avoid.

Then give me a weekly 20-minute money review routine I can follow to stay on track.

This is where clarity becomes momentum. You stop floating through the year and start making money decisions on purpose.

The Real Power of These Prompts

Claude is not the hero of your financial life. You are. Claude is just the tool that helps you stop avoiding the numbers and start asking better questions.

That is the real win here. The first time you understand your spending, spot a fee, cancel a useless subscription, choose a smarter debt strategy, or build a budget that actually fits your life, money gets less mysterious. It becomes something you can work with.

Not perfectly. Not overnight. Not without effort.

But with more clarity.

And clarity is power.

Start With One Prompt Today

Do not use all ten prompts at once and turn your afternoon into a financial therapy dungeon. Start with the prompt that matches your biggest pain point right now.

If you feel broke but do not know why, start with the spending analysis prompt. If debt is stressing you out, use the debt payoff prompt. If your bank statement looks like a haunted document, use the statement decoder. If tax season makes you sweat, start organizing now.

One prompt. One answer. One better decision.

That is how you build financial confidence. Not through shame, not through panic, and definitely not through pretending your money will organize itself.

Use the tools. Ask better questions. Make the next move.

Subscribe to Academy of AI for practical prompts, workflows, and strategies that help you use AI to work smarter, build faster, and create more freedom in your real life.

Claude can help with all of that.

Not because AI magically turns you into a bestselling writer overnight. That is not the game. The game is using AI to think sharper, write faster, organize your ideas, study your audience, and build a newsletter that feels impossible to ignore.

Most creators do not fail because they lack talent. They fail because their publication feels vague. Their About page is thin. Their post ideas are random. Their calls to action are weak. Their paid offer is unclear. Their reader does not know why they should subscribe, keep reading, or upgrade.

That is fixable.

Your Substack does not need to be perfect. It needs to be clear, useful, and alive. It needs to tell readers, “This is for you. This will help you. This is worth coming back to.”

That is where Claude becomes a serious creative partner. You can use it to pressure-test your positioning, plan better posts, build stronger reader trust, and create a simple growth system that does not require you to lose your mind.

Here are 10 Claude prompts to help Substack creators become bestseller-worthy.

How to Use These Claude Prompts for Substack Growth

Do not paste these prompts once and accept the first answer like it came down from the heavens. Claude is powerful, but the real magic happens in the follow-up.

Give Claude real context. Add your publication name, topic, audience, voice, goals, current subscriber count, paid offer, and what you are struggling with. Then ask it to refine, simplify, challenge, or improve the answer.

Think of Claude like a very smart strategist who needs your lived experience. It can help you see patterns, shape ideas, and build systems. But your taste, voice, and point of view still matter most.

That is the whole point. We are not using AI to erase the creator. We are using AI to make the creator sharper.

1. Claude Prompt to Clarify Your Substack Positioning

Most Substacks are too vague. They sound like they are “about culture” or “about business” or “about living better,” which is cute until nobody knows why they should subscribe.

A strong Substack needs a clear identity. Readers should know what you write, who you write for, and what they get from subscribing. If they cannot explain your publication in one sentence, you have a positioning problem.

Use this prompt when your publication feels broad, messy, or hard to describe.

Act as a Substack positioning strategist. Help me clarify my publication so readers immediately understand why they should subscribe.

My publication name is: [insert name]
My topic is: [insert topic]
My target reader is: [insert audience]
My current description is: [insert description]
My voice and tone are: [insert voice]
My goal is: [free subscribers, paid subscribers, authority, community, business growth, etc.]

Give me 5 sharper positioning options for my Substack. For each option, include the core promise, ideal reader, emotional hook, practical value, one-line description, and why someone would subscribe.

Then tell me which positioning option has the strongest bestseller potential and why.

The goal is not to sound clever. The goal is to sound clear. Clever gets skipped. Clear gets subscribed to.

2. Claude Prompt to Define Your Ideal Substack Reader

You cannot build a bestselling newsletter for “everyone.” Everyone is too busy, too distracted, and too impossible to write for.

You need a specific reader. You need to know what they want, what frustrates them, what they are afraid of, what they secretly hope for, and what would make them say, “Oh damn, this was written for me.”

This prompt helps you stop writing into the void and start writing to a real person.

Act as an audience research strategist for Substack creators. Help me define the ideal reader for my newsletter.

My Substack topic is: [insert topic]
My publication promise is: [insert promise]
My current audience is: [describe current audience or say I am starting from zero]
My goal is: [grow free subscribers, convert paid subscribers, build authority, create community, etc.]

Create a detailed ideal reader profile. Include their demographics, goals, frustrations, fears, daily problems, secret desires, buying triggers, content preferences, and reasons they would subscribe.

Then give me 10 article ideas this reader would immediately care about, 10 paid post ideas they might upgrade for, and 10 phrases that would make them feel seen.

This is one of the most important prompts in the whole list. If you understand your reader, everything gets easier. Titles get better. Posts get sharper. Offers get cleaner. Growth stops feeling like a mystery.

3. Claude Prompt to Audit Your Substack Setup Like a New Reader

Before people fall in love with your writing, they judge your setup. That includes your profile, publication name, description, homepage, About page, Welcome page, navigation, and overall brand vibe.

This matters because your setup is the first trust signal. If your Substack feels unfinished, confusing, or generic, readers may leave before they ever read your best post.

Use this prompt after you have your basic Substack setup in place.

Act as a brutally honest Substack growth consultant. I want you to audit my Substack like a brand-new reader deciding whether to subscribe.

Here is my publication information:
Publication name: [insert name]
One-line description: [insert description]
Target reader: [insert audience]
About page copy: [paste copy]
Welcome page copy: [paste copy]
Navigation links: [paste links or labels]
Public profile bio: [paste bio]
Brand vibe: [describe colors, imagery, tone, and style]

Review my setup for clarity, trust, personality, reader appeal, and subscription potential. Tell me what feels strong, what feels confusing, what feels generic, and what could stop someone from subscribing.

Then give me a prioritized fix list with the 10 highest-impact improvements I should make first.

This prompt is not about making your Substack pretty for the sake of pretty. It is about making the reader experience feel intentional. A polished setup tells people you are serious.

4. Claude Prompt to Write a Better About Page and Welcome Page

Your About page and Welcome page are not boring admin tasks. They are conversion pages.

A great About page tells readers what your publication is, who it is for, why you are the right person to write it, and what they can expect. A great Welcome page makes the first reader experience feel warm, clear, and worth joining.

This prompt helps you write both without sounding stiff or desperate.

Act as a Substack conversion copywriter. Help me write a stronger About page and Welcome page that make readers want to subscribe.

My publication name is: [insert name]
My topic is: [insert topic]
My ideal reader is: [insert audience]
My voice is: [insert voice and tone]
My personal background is: [insert relevant bio]
Readers can expect: [insert frequency, topics, formats, free or paid benefits]
My main call to action is: [subscribe, upgrade, share, join community, etc.]

Write an About page that includes what the publication is about, who it is for, why I created it, what readers will get, and a strong subscribe CTA.

Then write a Welcome page that feels warm, clear, and exciting for a brand-new reader. Make both pages human, confident, and not corporate.

Do not skip this. If your posts are the product, your About and Welcome pages are the front door. Make the front door feel good.

5. Claude Prompt to Build Content Pillars That Can Grow

Random posting is not a strategy. It is a panic response with a publish button.

A strong Substack needs content pillars. These are the core themes you return to again and again. They help readers understand what you stand for, and they help you avoid the weekly “what the hell do I write?” spiral.

Use this prompt to create a repeatable editorial foundation.

Act as an editorial strategist for a Substack creator who wants to build a bestselling newsletter.

My publication topic is: [insert topic]
My ideal reader is: [insert reader]
My publication promise is: [insert promise]
My voice and tone are: [insert voice]
My free subscriber goal is: [insert goal]
My paid subscriber goal is: [insert goal]

Create 5 content pillars for my Substack. For each pillar, explain the reader need it serves, the type of posts I should write, why it supports subscriber growth, and how it could support paid conversion.

Then give me 5 recurring series ideas I could publish weekly or monthly.

Content pillars give your publication structure without making it boring. You still get to be creative. You just stop reinventing the whole damn newsletter every week.

Subscribe now

6. Claude Prompt to Generate Bestseller-Worthy Substack Post Ideas

A strong idea does half the work before you write a word. Weak ideas make you compensate with too much effort, too much explanation, and too much “please care about this.”

This prompt helps you generate ideas with a better chance of getting opened, read, shared, and remembered. It also helps separate content that is interesting from content that is useful.

Act as a Substack editor known for developing viral, high-converting newsletter ideas.

My publication is about: [insert topic]
My ideal reader is: [insert audience]
My content pillars are: [insert pillars]
My voice is: [insert voice]
My goal is: [grow subscribers, get shares, convert paid readers, build authority, etc.]

Give me 30 Substack post ideas with bestseller potential. For each idea, include a title, subtitle, reader problem, emotional hook, why it would get opened, whether it should be free or paid, and the best call to action.

Score each idea from 1 to 10 on urgency, originality, shareability, and paid conversion potential. Then choose the top 5 ideas I should write first.

Do this before you write. It saves time and makes your editorial calendar much stronger. The best newsletters are not just well-written. They are built on ideas people actually want to read.

7. Claude Prompt to Improve Your Headlines and Subtitles

Your headline is the front line. If it does not make people curious, they will not get to your beautiful intro, your brilliant argument, or your gorgeous little mic drop at the end.

Substack titles need clarity and pull. They should tell readers what they will get, why it matters, or why they should care right now.

Use this prompt after you draft a post idea.

Act as a Substack headline editor. Help me create stronger titles and subtitles for a post.

My draft title is: [insert title]
My post topic is: [insert topic]
My ideal reader is: [insert audience]
The main takeaway is: [insert takeaway]
The emotional hook is: [insert emotion or tension]
My voice is: [insert voice and tone]

Give me 20 title options and 20 subtitle options. Organize them by style: clear and practical, bold and provocative, emotional and personal, SEO-friendly, and paid-subscriber worthy.

For each of the top 5 title and subtitle combinations, explain why it works and what kind of reader it would attract.

This is where Claude can save you from being too soft. A lot of creators bury the good part. Make the title do its job.

8. Claude Prompt to Turn One Post Into a Subscriber Growth Engine

A post should not live once and disappear. That is leaving money and growth on the table.

One strong Substack post can become a Notes post, social post, email teaser, paid upsell, discussion question, podcast outline, short video script, and lead magnet idea. You do not need more work. You need better reuse.

This prompt helps you turn one post into a growth machine.

Act as a newsletter growth strategist. Help me turn one Substack post into a full subscriber growth engine.

Here is my post draft or outline: [paste draft or outline]
My publication is about: [insert topic]
My ideal reader is: [insert audience]
My main goal is: [free subscribers, paid subscribers, shares, comments, referrals, etc.]
My platforms are: [Substack Notes, Instagram, TikTok, LinkedIn, Threads, email, podcast, etc.]

Create a growth plan for this post. Include a stronger title if needed, a sharper subtitle, SEO keywords, a free subscriber CTA, a paid subscriber CTA, 5 social captions, 3 Substack Notes posts, 3 discussion questions, and 3 ways to repurpose the post into future content.

Make the strategy feel natural, not spammy.

This is how creators get more mileage from the work they already did. You do not need to create from scratch every day. You need to build loops.

9. Claude Prompt to Convert Free Subscribers Into Paid Subscribers

Free subscribers are not failed paid subscribers. They are future buyers, loyal readers, sharers, fans, and proof that your work is landing.

But if you want paid subscribers, you need a clear paid promise. People need to know what they get, why it matters, and why upgrading makes sense.

This prompt helps you design a paid strategy that feels valuable, not pushy.

Act as a paid newsletter strategist. Help me create a free-to-paid conversion strategy for my Substack.

My publication topic is: [insert topic]
My ideal reader is: [insert reader]
My free content includes: [insert free content]
My paid content could include: [insert ideas or say I need help]
My current subscriber count is: [insert number]
My paid subscription price is: [insert price or say undecided]
My voice is: [insert voice]

Create a paid subscription strategy. Define what should stay free, what should be paid, and why readers would upgrade.

Give me 5 paid content formats, 10 paid post ideas, 5 upgrade CTA examples, 3 launch email ideas, and 5 ways to talk about paid subscriptions without sounding desperate or salesy.

Also tell me what objections readers might have and how to answer them.

Paid conversion is not about begging people to upgrade. It is about making the value obvious. If readers know what they get and why it helps, the ask feels natural.

10. Claude Prompt to Build Your Weekly Substack Bestseller System

Bestselling creators do not just write when inspiration floats through the window wearing a little silk robe. They build a rhythm.

You need a weekly system for ideas, writing, publishing, promotion, reader engagement, and review. That does not mean you need to become a productivity robot. It means you need a simple structure that helps you keep going.

Use this prompt to create your weekly operating system.

Act as my Substack operations coach. Help me build a weekly system to grow my publication and move toward bestseller-level consistency.

My publication is: [insert name]
My topic is: [insert topic]
My ideal reader is: [insert audience]
My publishing frequency is: [insert frequency]
My available writing time each week is: [insert hours]
My current subscriber count is: [insert number]
My main goal this month is: [free growth, paid growth, better posts, consistency, engagement, etc.]

Build me a weekly Substack workflow. Include when to brainstorm, draft, edit, publish, promote, engage with readers, review metrics, and plan the next issue.

Also create a weekly review template I can paste into Claude every week. The template should help me analyze what worked, what flopped, what readers responded to, and what I should publish next.

This prompt helps you build momentum. Momentum matters because newsletters are not built in one heroic writing session. They are built through repeatable effort, honest review, and tiny improvements over time.

The Real Secret to Becoming a Substack Bestseller

Claude can help you get clearer, faster, and more strategic. It can help you write better headlines, plan stronger posts, understand your reader, and build a paid subscription strategy that actually makes sense.

But Claude cannot care for you.

It cannot replace your taste. It cannot fake your lived experience. It cannot build trust with your readers if you never show up. It cannot turn a vague publication into a beloved one unless you are willing to make real decisions.

That is the secret most people avoid. Bestseller energy comes from clarity and consistency. You need a real point of view. You need a reader you understand. You need a promise you can keep. You need posts that solve problems, spark emotion, or make people feel less alone.

AI can help you build all of that faster.

But you still have to publish.

Start With One Prompt Today

Do not use all 10 prompts at once unless you want to create a giant strategy document and then avoid your actual newsletter for three weeks.

Start with the prompt that matches your biggest bottleneck. If your publication feels vague, use the positioning prompt. If you do not know who you are writing for, use the ideal reader prompt. If your setup feels messy, use the audit prompt. If your posts are not getting opened, use the headline prompt. If you want paid subscribers, use the conversion prompt.

One prompt. One improvement. One clearer decision.

That is how you build a better Substack.

Not through perfection. Not through panic. Not through watching everyone else publish while you keep “getting ready.”

You build it by doing the work.

Claude can help.

Now make the damn thing worth subscribing to.

Subscribe to Academy of AI

Academy of AI helps everyday people use AI to work smarter, create faster, grow online, and build more freedom. Subscribe for practical prompts, tools, workflows, and strategies you can use without the jargon.

Let’s be honest about the phrase “pay you everyday.” Claude is not going to magically drop $500 into your bank account while you sit around drinking iced coffee. That is not the game, and I am not here to sell you that fantasy.

But can Claude help you turn your skills into digital products, offers, content, and sales systems that create income? Absolutely. That is where things get exciting. If you have a laptop, Wi-Fi, time, and one useful skill, you can start building something people might actually pay for.

Most people overcomplicate online income. They think they need a perfect website, a giant audience, a fancy funnel, and a 47-step business plan before they can sell anything. Usually, they need something much simpler: one problem they can solve, one audience that needs it, and one product that makes life easier.

That is where Claude becomes powerful. You can use it like a business strategist, product coach, market researcher, copywriter, and launch planner. The magic is not in asking random questions. The magic is giving Claude enough context to help you make smarter decisions.

These ten prompts will help you find profitable ideas, validate demand, build digital products, price them, choose where to sell, and create a daily sales plan. They are built for real people with real skills, not tech bros trying to turn every idea into venture capital cosplay.

How to Use These Claude Prompts

Before you copy and paste anything, remember this: Claude works better when you give it real details. Replace every bracket with your actual skill, audience, experience level, time availability, and goals. The more honest you are, the better your output gets.

Do not treat these prompts like magic spells. Treat them like business conversations. After Claude gives you an answer, push back. Ask for simpler options. Ask what could fail. Ask what someone would actually pay for. Ask how to launch it this week.

AI does not replace your judgment. It sharpens it. Used well, these prompts can help you move from “I have no idea where to start” to “I know what to build next.”

Prompt 1: Find Profitable Digital Product Ideas From One Skill

The easiest place to start is with something you already know. You do not need to invent a new skill from scratch. You need to look at your knowledge differently and ask, “What could this become?”

This prompt helps Claude turn one skill into digital product ideas. It also forces the ideas to connect to a real buyer, a real problem, and a realistic launch path. That matters because vague ideas do not pay. Useful products do.

Copy this Claude prompt:

Act as my digital product strategist. I want to turn one skill into online income.

My skill is: [insert skill]
My experience level is: [beginner, intermediate, or expert]
My target audience is: [insert audience]
My goal is: [extra income, full-time business, side hustle, audience growth, etc.]

Give me 15 digital product ideas I could create from this skill. For each idea, explain what the product is, who would buy it, what problem it solves, how difficult it would be to create, how quickly I could launch it, and where I should sell it.

Then rank the ideas in two ways: easiest to launch first and highest long-term income potential.

Use this when you feel stuck or scattered. It gives you a full menu of options, which helps you stop obsessing over one perfect idea. The goal is not to build all 15. The goal is to find the one idea that feels useful, simple, and sellable right now.

Prompt 2: Turn Your Skill Into Beginner-Friendly Products

A lot of people avoid digital products because they think they need advanced tech skills. They imagine complicated courses, custom software, giant membership sites, and expensive platforms. That is usually where momentum dies.

Simple products sell too. A checklist, guide, template, swipe file, workbook, Notion dashboard, spreadsheet, or mini-training can solve a real problem. People do not always need the biggest product. They often need the fastest path to a result.

Copy this Claude prompt:

Help me turn my skill into simple digital products that are beginner-friendly to create and sell.

My skill is: [insert skill]
My audience is: [insert audience]
I want products I can make with simple tools like Google Docs, Canva, Notion, spreadsheets, Loom, or basic PDFs.

Give me 10 product ideas. For each one, include a product name, format, target buyer, problem solved, suggested price range, simple creation steps, and why someone would pay for it.

Prioritize products that are easy to create, easy to explain, and easy for a beginner to sell.

This prompt is perfect when you want to start lean. You do not need to build a huge offer first. In fact, your first product should probably be simple as hell. Simplicity helps you finish, launch, learn, and improve.

Prompt 3: Build a Product Ladder From Low-Ticket to Premium

One digital product is great. A connected product ladder is better. A product ladder gives your audience a clear path from a small first purchase to a bigger transformation.

Think of it like this: someone might buy a $19 template before they trust you enough for a $299 course. They might join a $29 monthly membership after they see your free content works. The ladder creates momentum.

Copy this Claude prompt:

Act as a product ecosystem strategist. I want to build a simple product ladder around my skill.

My skill is: [insert skill]
My audience is: [insert audience]
My current audience size is: [insert audience size or say none yet]
My main transformation is: [what I help people achieve]

Create a 4-level product ladder for me. Include a low-ticket offer, a mid-ticket offer, a premium digital offer, and a recurring offer.

For each level, explain what the product is, the price range, the delivery format, the ideal buyer, the main promise, and how it naturally leads to the next offer.

This prompt helps you think like a business owner instead of a one-off seller. You are not just creating random products. You are building a path people can follow as they grow.

Prompt 4: Find the Fastest Product You Can Launch in 7 Days

Speed matters. Not because rushing is cute, but because overthinking kills more businesses than bad ideas do. A seven-day launch forces you to focus on a product you can actually finish.

This prompt is for people who need momentum. It helps you find a realistic product based on your available time, skill, and audience. It also gives you a day-by-day plan, which removes a lot of the guesswork.

Copy this Claude prompt:

I want to create and launch a digital product in 7 days.

My skill is: [insert skill]
My audience is: [insert audience]
I can work on this for: [insert hours per day]
My preferred product format is: [PDF, template, mini-course, workbook, Notion template, spreadsheet, etc.]
My goal is: [first sale, testimonials, fast cash, audience growth, etc.]

Give me 7 product ideas I could realistically finish in one week. For each idea, include the product concept, tools needed, estimated price, difficulty level, and a simple day-by-day creation plan.

At the end, choose the best option for speed, simplicity, and first sales.

This prompt is a momentum machine. It helps you stop asking, “What should I build?” and start asking, “What can I finish this week?” That shift matters.

Prompt 5: Validate What People Will Actually Pay For

Here is where a lot of creators mess up. They build the thing they want to make, then hope someone wants to buy it. That is backwards.

Validation helps you avoid wasting time. It does not guarantee sales, but it makes your product smarter before you build. You want to know if the problem feels urgent, if the buyer cares, and if the product feels easy to understand.

Copy this Claude prompt:

Act as a market validation researcher. I want to sell a digital product based on my skill, but I do not want to build something nobody wants.

My skill is: [insert skill]
My audience is: [insert audience]
The problem I think they have is: [insert problem]
My product ideas so far are: [insert ideas or say I need ideas]

Give me 10 possible digital product ideas. Score each idea from 1 to 10 on demand, urgency, ease of creation, uniqueness, and likelihood of purchase.

Then identify the top 3 ideas most likely to generate revenue quickly. Explain why each one has potential, what could make it fail, and how I could test demand before building it.

This prompt gives you a reality check. That is a good thing. You do not need Claude to hype every idea. You need it to help you make better bets.

Prompt 6: Build Products From What You Already Know

You probably have more product ideas in your head than you realize. They are hiding in the tasks you repeat, the questions people ask you, the mistakes you help others avoid, and the shortcuts you use without thinking.

This prompt helps you mine your existing knowledge. That is powerful because your best product may not come from learning something new. It may come from packaging something you already do naturally.

Copy this Claude prompt:

Help me turn my existing knowledge into digital products. I do not want to start from zero.

My skill or area of expertise is: [insert skill]
My audience is: [insert audience]

First, ask me 10 questions about the tasks I repeat, the advice I give often, the mistakes I help people avoid, the shortcuts I use, the frameworks I follow, and the results I know how to create.

After I answer, turn my responses into 10 digital product ideas. For each idea, include a product title, format, ideal customer, problem solved, and why it could sell.

This one works because it starts with your real life. You are not forcing some random idea into existence. You are turning your experience into something useful, structured, and sellable.

Prompt 7: Create a Complete Digital Product Outline

Once you choose an idea, you need structure. This is where people often freeze. They know what they want to teach, but they do not know how to organize it into something worth buying.

Claude can help you shape the product from messy idea to clear outline. This prompt works for guides, mini-courses, templates, workbooks, workshops, and resource kits. It helps you create something practical instead of bloated.

Copy this Claude prompt:

I want to create a digital product and need a complete outline.

Product type: [guide, workbook, template, mini-course, workshop, Notion dashboard, spreadsheet, etc.]
Topic: [insert topic]
Audience: [insert audience]
Main promise: [what the product helps people do]
Skill level of buyer: [beginner, intermediate, expert]
Desired length or size: [short, medium, comprehensive]

Build the full product outline. Include the product title, subtitle, promise, sections or modules, what belongs inside each section, quick-win elements, examples to include, bonus ideas, and final deliverable structure.

Make it practical, simple, and worth paying for. Avoid fluff and academic theory.

This prompt helps you build a product that feels complete without becoming overwhelming. Remember, people are not paying for more information. They are paying for a clearer path.

Prompt 8: Price Your Digital Product With Confidence

Pricing can make people spiral. Too low, and you might undervalue the work. Too high, and you might scare off early buyers. The right starting price depends on your audience, product depth, transformation, and trust level.

This prompt helps you compare pricing options without guessing. It gives you a low, mid, and premium approach so you can see what changes at each level.

Copy this Claude prompt:

Help me choose the right price for my digital product.

My product idea is: [insert product idea]
My audience is: [insert audience]
The problem it solves is: [insert problem]
The result it helps create is: [insert result]
My current audience size and trust level is: [insert details]
My goal is: [early sales, testimonials, profit, premium positioning, etc.]

Compare three pricing options: low-ticket, mid-ticket, and premium. For each option, explain what should be included, what type of buyer it attracts, the likely conversion logic, and the pros and cons.

Then recommend the best starting price for my current situation and explain how I should raise the price later.

This is not just about picking a number. It is about matching the price to the value, buyer, and launch goal. Early on, a smart price can help you get traction faster.

Prompt 9: Choose the Best Platform to Sell Your Product

A product needs a home. That does not mean you need to build a complicated website on day one. Depending on your product, audience, and goals, you may be better off starting with a simple platform.

Some creators need a marketplace. Some need a checkout page. Some need a full store. Some need a simple link they can send to buyers. The best platform is the one you can actually use without getting stuck for three weeks.

Copy this Claude prompt:

Help me choose the best platform to sell my digital product.

My product type is: [insert product type]
My skill or topic is: [insert skill or topic]
My audience is: [insert audience]
My goal is: [fast setup, marketplace traffic, brand control, low fees, subscriptions, bundles, etc.]
My tech comfort level is: [low, medium, high]
My budget is: [insert budget]

Compare platforms such as Gumroad, Payhip, Etsy, Shopify, Notion marketplaces, Stan Store, Beacons, and my own website.

For each option, explain ease of setup, fees, traffic potential, customization, beginner friendliness, and best use case. Then recommend the best platform for my situation and give me the first 5 setup steps.

This prompt saves you from platform paralysis. Do not spend a month choosing software before you have a product. Pick the cleanest option, launch, and improve from there.

Prompt 10: Create a Daily Sales System

This is the prompt that connects the whole thing. A product does not pay you daily because it exists. It pays when people see it, understand it, trust it, and buy it.

You need a simple daily sales system. That does not mean spamming people or posting desperate “buy my thing” content all day. It means creating a repeatable rhythm for education, proof, storytelling, and clear calls to action.

Copy this Claude prompt:

Act as my launch strategist and daily sales coach. I have a digital product I want to sell consistently.

My product is: [insert product]
My audience is: [insert audience]
The main problem it solves is: [insert problem]
The result it helps create is: [insert result]
My selling platforms are: [Substack, Instagram, TikTok, email, website, Etsy, Gumroad, etc.]
My audience size is: [insert size]
My goal is: [daily sales, first 10 buyers, $500/day, testimonials, etc.]

Build me a 14-day daily sales system. Include daily content ideas, email topics, social post angles, call-to-action examples, testimonial collection ideas, and simple ways to talk about the product without sounding spammy.

Also give me a weekly repeatable version I can keep using after the first 14 days.

This is where daily income becomes less mysterious. You need visibility, consistency, and a product people understand. Claude can help you build the rhythm, but you still have to show up.

The $500-a-Day Math

A $500 day is not magic. It is math, positioning, traffic, and trust working together. You could reach $500 with 25 sales of a $20 product, 10 sales of a $50 product, 5 sales of a $100 product, or 2 sales of a $250 product.

That does not mean every product will hit those numbers. It means the goal gets less scary when you break it down. Instead of asking, “How do I make $500 a day?” ask, “What product can I sell, at what price, to which buyer, through what daily system?”

That is a much better question. Claude can help you answer it, but you need to bring the skill, the audience insight, and the follow-through.

Start With One Prompt, Not Ten

Do not try to use all ten prompts in one sitting. That is how you create a 47-page strategy document and still launch nothing. Start with one prompt based on where you are right now.

If you do not know what to sell, start with Prompt 1. If you need something simple, use Prompt 2. If you already have an idea, validate it with Prompt 5. If you know what you are building, outline it with Prompt 7. If the product is ready, use Prompt 10 and start selling.

The goal is not to become a prompt collector. The goal is to become a person who uses AI to take action faster.

Claude Can Help You Build, But You Have to Launch

AI is not the business. You are still the business. Claude can help you think, organize, create, price, plan, and sell, but it cannot care more than you do.

That is the real lesson. The people who win with AI will not be the people who hoard the most prompts. They will be the people who use prompts to build real things, solve real problems, and serve real audiences.

Start small. Pick one skill. Choose one audience. Build one product. Sell it clearly. Improve it as you learn.

That is how online income starts. Not with perfection. Not with hype. Not with some guru promising you passive income by Friday.

It starts with one useful thing.

And a decision to launch.

Subscribe to Academy of AI for practical AI prompts, workflows, and strategies that help you work smarter, build faster, and create more freedom with the tools already changing the world.

AI is not some futuristic tech trend anymore. It is in our inboxes, search results, creative tools, workplaces, phones, schools, businesses, and daily decisions. It is here, and it is evolving fast.

That can feel exciting, but it can also feel overwhelming. Most people are not apprehensive of AI because they are lazy or afraid. They are apprehensive because nobody has explained it in a way that feels clear, useful, and human.

That is why I created Academy of AI. It’s for ordinary people who know AI can help them achieve extraordinary things, but do not know where to start. It is for creators, business owners, freelancers, employees, students, teachers, parents, artists, writers, entrepreneurs, and anyone who wants to stop feeling confused by the future.

You do not need to become a programmer. You do not need to memorize every AI tool. You do not need to speak in startup jargon or pretend you understand every update. You just need to learn how to use AI in real life.

Subscribe now

What Is AI Literacy?

AI literacy means knowing how to work with artificial intelligence in a practical way. It means understanding what these tools can do, where they fall short, and how to use them with good judgment. It means learning how to ask better questions, get better answers, and turn messy thoughts into clear action.

AI literacy is not about replacing your brain. It is about expanding what your brain can do. You can use AI to write faster, plan smarter, summarize information, brainstorm ideas, organize your day, research a topic, build systems, create content, make decisions, and save time.

But you — the human — still matter. Your voice matters, your taste matters, your lived experience matters, and your instincts matter. AI can help you move faster, but you still choose the direction.

Why AI Is the Ultimate Digital Skill

Every generation gets a new skill that changes the game. Reading changed access to knowledge. Computers changed how we work. The internet changed how we learn and connect. Social media changed how we build audiences, brands, and businesses.

Now AI is changing how we think, create, work, and earn. That does not mean everyone needs to panic. It means everyone needs access, because the gap between people who know how to use AI and people who do not is already growing.

The people who learn AI now will have more options. They will move quicker, save time, build better systems, and see opportunities earlier. They will understand how to use these tools instead of feeling intimidated by them, and that is the whole point of Academy of AI.

Why I Created Academy of AI

I did not create this newsletter to make AI sound fancy. I created it to make AI feel useful. There is already enough noise, hype, and confusion around artificial intelligence, and most of it makes people feel more behind than empowered.

My lane is transparency. I want to help people understand AI without shame, fear, or gatekeeping. I want to show you how to use it for your actual life, not some imaginary future version of yourself with unlimited time and a perfect productivity system.

You have real problems. You have work to do, ideas to build, money to make, and time you want back. AI can help with that, but only if you know how to use it.

What You Can Expect From Academy of AI

Academy of AI will teach practical AI skills in plain English. Every post will help you understand a tool, an idea, a workflow, or an opportunity you can use right away. This will not be theory for theory’s sake. It will be helpful, direct, and built for real life.

You can expect simple lessons on how AI works, how to write better prompts, how to choose the right tools, and how to get results that actually sound like you. You can expect prompts you can steal, customize, and use in your own life or business. You can also expect honest breakdowns of what is useful, what is confusing, what is overhyped, and what is worth your time.

We will also talk about the risks. AI is powerful, and powerful tools deserve clear thinking. We will cover privacy, accuracy, bias, copyright, misinformation, job changes, and the moments when you should not rely on AI.

AI for Work

AI can help you work smarter without turning you into a robot. It can draft emails, summarize long documents, prepare meeting notes, organize projects, build outlines, research faster, and help you make sense of information. That matters whether you work for yourself or someone else.

If you are an employee, AI can help you become more valuable. If you are a freelancer, AI can help you serve clients faster. If you are a founder, AI can help you build without hiring a giant team. If you are a creator, AI can help you stay consistent without burning out.

This is not about doing lazy work. It is about getting out of the busywork trap, so your energy goes toward the work only you can do. AI can help clear the clutter, and that kind of clarity is powerful.

AI for Money

Let’s talk about money, because we should. AI can help people make more of it, but not through scammy “press one button and get rich” nonsense. I am talking about real leverage.

AI can help you package your knowledge, build better offers, write stronger sales pages, research your audience, create content, test ideas, improve products, and automate repetitive tasks. Money loves speed, clarity, and execution. AI helps with all three.

That does not mean AI replaces effort. It means your effort can go further. For everyday people, that kind of leverage can be life-changing.

AI for Creativity

AI is not the enemy of creativity. Bad taste is the enemy. Lazy execution is the enemy. Copy-paste thinking is the enemy.

Used well, AI can help you brainstorm, outline, remix, explore, edit, and get unstuck. It can help when the blank page is staring back at you. It can help you turn a messy idea into a real starting point, which is often the hardest part.

But AI should never erase you. Your voice is the asset, your perspective is the asset, and your youness is the asset. Academy of AI will show you how to use AI as a creative partner, not a replacement.

AI Tools Without the Overwhelm

There are already too many AI tools. Every day, some new app promises to change your life by Thursday, and most of them will not. Some will be genuinely useful, but part of learning AI is knowing the difference.

Academy of AI will help you build a simple, useful toolkit. We will look at tools for writing, research, productivity, automation, design, video, audio, education, and business. We will not chase every shiny thing, because that is exhausting.

The goal is not to use every tool. The goal is to use the right tools for your life. A good AI toolkit should save time, reduce friction, and help you create better results with less chaos.

Subscribe now

Learning AI Should Feel Accessible

I believe AI education should be easy to understand. Not watered down, not basic, and not boring. Just clear.

You should not need a computer science degree to understand tools that are already changing the world around you. You should not need to be wealthy, technical, or perfectly prepared to start learning. You should be able to open a newsletter, learn one useful thing, and apply it that day.

That is what Academy of AI is here to do. One lesson at a time, one tool at a time, and one useful win at a time. Small wins build confidence, and confidence turns into momentum.

The Future Should Belong to All of Us

A lot of people are waiting. They are waiting for AI to get easier, waiting for their job to train them, waiting until they have more time, or waiting until they feel less intimidated. That makes sense, but waiting has a cost.

The world is not slowing down so everyone can feel ready. Still, here is the good news: you are not too late. You do not need to master everything overnight, and you do not need to understand every model, tool, update, or trend.

You just need to start. That is how literacy works. You learn by using the language, and AI is quickly becoming the new language of work, creativity, business, and opportunity.

Your First AI Assignment

Open an AI tool and ask it this: “Help me identify three ways AI could save me time in my work or life this week. Ask me questions first so your suggestions are specific.” Start with one real problem, let AI help with one task, and notice what changes.

That first small win matters. The first time AI saves you time, clears your thinking, or helps you create something faster, the fear starts to fade. Confidence grows through action.

Subscribe to Academy of AI

Academy of AI is where we turn confusion into clarity. It is where we turn tools into skills, curiosity into power, and overwhelm into action. This newsletter will help you learn the AI tools already changing work, money, creativity, and freedom.

No panic. No jargon. No gatekeeping. Just practical AI education for real people with real lives.

Subscribe to Academy of AI. Bring your questions, your ambition, and your beautiful, messy, human brain. We have work to do.