I am a big fan of Robert Graham designer shirts which are pretty expensive but like wearing art. And one of the things you can do with ChatGPT is just give it a prompt and a web site link and it can make you the model for that fashion item or brand.

I want you to create 8 images where I am the model for Robert Graham's top selling shirts https://www.robertgraham.us/collections/button-down-shirts

Give this a try with any brand you love. Lets see what you can create in the comments.

TLDR: Most teams treat AI like a writing assistant. The teams pulling ten hours back every week treat it like a coworker with a job description. Here are the 20 Claude Cowork prompts that turn calendar triage, report drafting, deck building, CRM updates, and end-of-day wrap-up from multi-hour grinds into 20-minute workflows.

You have five hours of admin in front of you on a Tuesday morning. Calendar to triage. Three reports due. A deck to build from rough notes. A CRM that has not been touched in three weeks. The honest question is not whether AI can help. The honest question is whether you know what to ask it to do.

I have been building in this space for a long time and the single biggest unlock I have watched, across both individual operators and entire teams, has nothing to do with model upgrades or longer context windows. The unlock is more boring than that. It is knowing exactly what to ask on a Tuesday morning when the admin pile is taller than the strategic work.

The gap is not capability. It is specificity.

Claude can read your calendar, draft your follow-ups, summarize your PDFs, build your deck, and write your CRM updates. None of that is in dispute. What separates the teams saving real time from the teams still bouncing around tabs is that the time-saving teams have a list. A list of specific prompts for specific recurring jobs.

When a new request comes in, they do not stare at a blank prompt box trying to figure out how to phrase it. They open the playbook, copy the prompt for that exact job, fill in the brackets, and ship it. Five minutes from request to result.

The teams still struggling with AI usually have one of three problems. First, they ask Claude vague questions like help me with this report instead of giving it a structure to follow. Second, they keep starting from scratch every time, so the same email draft request takes them ten different prompts across the week. Third, they never wire AI into the recurring workflows that actually eat their week. So AI lives in a browser tab while admin still lives in their day.

What changed with Cowork

Cowork is built around the idea that AI should not just sit there waiting to answer questions. It should be doing real work against your real files, your calendar, your inbox, your spreadsheets, your folders.

That changes what a good prompt looks like. A good Cowork prompt is not a clever turn of phrase. It is a job description with inputs and outputs. Read this folder. Pull these contacts. Compare these contracts. Write this output to that location. Done.

If you have not yet built your own personal library of these, here are 20 that cover the workflows that eat real time across most professional roles. I have grouped them by where the time goes.

Morning and end-of-day rituals

Start and close the day with structured Cowork prompts and you will recover roughly 90 minutes a day before you even touch a strategic task.

1. Morning Briefing. Check your Google Calendar or Outlook, unread emails in Gmail or Outlook, and Slack or Teams mentions from the last 12 hours. Summarize everything you need to know before your first meeting at a specific time. Keep it under 200 words. Flag anything that needs a reply today. This is the single highest leverage prompt in this list. It turns the first 30 minutes of your day from inbox triage into actual context.

20. End-of-Day Wrap-Up and Tomorrow's Plan. At a set time each day, check what files were created or edited in a specific folder today, pull your calendar for tomorrow, and check for unread emails or Slack messages flagged as urgent. Write a short end-of-day wrap-up covering what you got done today and a prioritized to-do list for tomorrow. Save it as a daily note. This closes the loop. You leave nothing dangling.

Folder, file, and data hygiene

Most teams lose hours every week to file chaos. These five prompts fix it.

2. Folder Cleanup and File Organization. Rename all files in a folder using a clear format like DATE - TOPIC - FILE TYPE. Group them into subfolders by category, month, client name, or project. List what was moved and ask before deleting anything.

11. Duplicate File Detection and Cleanup. Scan a folder and identify duplicates based on file name similarity or identical file size. List all duplicates with their full paths, the date each was created, and which one appears to be the more recent or complete version. Ask before deleting.

16. Data Cleaning and Formatting in Excel. Open a messy spreadsheet. Describe the mess: inconsistent date formats, missing values, duplicate rows, merged cells. Clean it by standardizing date formats, removing duplicates, filling blanks with N/A, and adding a summary row at the bottom. Save the cleaned version with a clear file name.

14. Scheduled Recurring File Report. Every Monday morning or Friday at 5pm, go into a specific folder and check for new files added in the past seven days. List each file by name, size, and what it appears to contain based on the file name and first few lines. Send a summary so you know what came in during the week.

19. PDF to Structured Summary Pipeline. Open all PDFs in a folder. For each, produce a structured summary with these sections: Purpose, Key Findings or Terms, Action Items or Red Flags, and a Confidence Rating on how complete the document appears. Compile all summaries into a single Word document.

Document and deliverable creation

This is where AI used to feel impressive but unreliable. With specific prompts, you get structured output every time.

3. Report Draft from Source Files. Read all PDF, Word, or text files in a folder. These are research notes, meeting transcripts, or raw data. Produce a structured report with Executive Summary, Key Findings, and Recommendations. Save as a Word document. Three hours of synthesis collapses to 20 minutes of review.

4. Contract or Proposal Comparison Table. Open multiple PDF contracts or vendor proposals. Compare across price, scope of work, payment terms, renewal clause, and cancellation policy. Produce a comparison table in Excel.

8. PowerPoint Presentation from Notes. Read a file containing raw notes or a document outline. Turn it into a 10, 15, or 20 slide deck. Each slide gets a headline, three to five bullet points, and a speaker note. Save as a pptx ready to present.

15. Onboarding Document Pack Creation. Using files in a folder as source material, create an onboarding document pack for a new role joining the team. The pack should include a welcome overview, a glossary of key terms, a list of tools they will need and access steps, and a 30-day plan outline. Save as a single Word document.

17. Social Media or Content Batch Drafting. Read a file containing a product brief, campaign notes, or topic list. Use it to write 10, 15, or 20 LinkedIn post drafts on a specific topic. Each post should be 150 to 200 words, start with a strong hook, and end with a question or call to action. Save all drafts in a single Word document.

Communication and CRM

These are the prompts that keep relationships warm and pipeline current without you living in the CRM.

5. Meeting Preparation Brief. For an upcoming meeting with a specific contact at a specific company, pull recent files from a folder, check recent emails using a Gmail connector, and write a one-page prep brief covering background context, open questions, and talking points.

9. Email Follow-up Drafts. Read the email thread saved in a file or pull the last three to five emails with a contact. Draft a follow-up email that references the last conversation, summarizes what was agreed, or asks for a status update. Keep it under 150 words, professional in tone, ready to send.

18. CRM or Sales Notes Update via Connector. Using a Salesforce or HubSpot connector, pull all deals you own that are in a specific stage and have not been updated in the past 14 or 30 days. For each, check recent emails with that contact and write a one-sentence update on where things stand. Save a summary report.

Operations and back-office time sinks

These five prompts solve the boring but expensive workflows that compound across a year.

6. Weekly Newsletter or Internal Update. Read files from the past seven or 14 days covering project updates, team activity, or campaign performance. Draft a weekly newsletter or update email with a summary at the top, bullet points per section, and a next steps section at the end.

7. Expense and Receipt Processing. Open all image and PDF expense receipts in a folder. Extract merchant name, date, amount, and category for each one. Compile everything into an Excel spreadsheet with a total row and save it.

10. Research Synthesis from Multiple Sources. Use web search to find the 5 or 10 most relevant and recent articles on a topic from the past 30 or 90 days. Summarize each one in two to three sentences. Then write a 400-word synthesis that pulls out key trends, disagreements, and open questions.

12. Client or Project Status Update. Read all files in a folder related to a client or project. These include meeting notes, deliverables, or email exports. Produce a one-page status update covering what has been completed, what is in progress, what is blocked, and what is due next.

13. Job Application Batch Processing. This one is for the people in transition. With a number of job description files in a folder and a resume in another file, compare each job to the resume and write a tailored cover letter in your voice. Save each cover letter as a separate Word file.

The pattern under all 20

Every prompt above follows the same shape. Specific input location. Specific structure for the output. Specific destination for the saved file. That is the whole edge.

Vague prompts get vague answers. The same person asking write me a status update will get something generic and forgettable. The same person asking read all files in this folder, produce a one-page update with these four sections, save it as a Word doc with this name will get something usable on the first try.

The other pattern worth noticing is that every prompt does one job. Not three. The temptation when you first start using Cowork is to chain everything into one mega-prompt. Resist it. Build 20 narrow prompts that each do one thing well. Run them in sequence when you need to. You will get cleaner output and you will be able to debug any one of them when something looks off.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

My prompt was "How I feel when I get that signed contract I have been working on for months"

The Comprehensive Guide to Answer Engine Optimization (AEO)

• Why Reddit is currently outranking your 50k a month content strategy in AI search
• The 20-year SEO era is dead and marketing isn't ready for what comes next

TLDR

• The Shift: AEO (Answer Engine Optimization) is the non-negotiable evolution of SEO, moving from "blue link" visibility to becoming the grounded, cited source for Large Language Models (LLMs).
• The Blueprint: The Webflow AEO Maturity Model provides a four-pillar framework—Content, Technical Structure, Authority, and Measurement—to navigate the transition from traditional search to AI-driven discovery.
• The Strategy: Success hinges on Information Density and structured data that allows LLM crawlers to ingest, parse, and cite your brand with high confidence.
• The Authority: AI models prioritize community-validated truth; third-party platforms like Reddit now dictate your brand's authority in the eyes of an LLM.

The Crisis in Search: Why Marketers Are Worried Traditional SEO is rapidly becoming a legacy play, and for many brands, it is currently incinerating CAC. The unsettling reality for marketing leadership is that zero-click saturation is no longer a fringe theory; it is the new baseline. When users ask an AI for a recommendation, they aren’t clicking through to your carefully crafted landing page—they are receiving a synthesized answer. CMOs are rightfully anxious because the metrics that defined the last two decades are bleeding out. The shift from browsing a list of links to receiving a definitive AI response is a structural change in human behavior. Transitioning to AEO is not a "nice-to-have" experiment; it is the only way to remain visible in a landscape where LLMs act as the primary gatekeepers of information. While the landscape is shifting, the core objective remains the same: being the most credible answer in the room.

Defining AEO: Evolution vs. Replacement AEO is not a pivot away from SEO; it is its high-authority progression. Abandoning SEO fundamentals would be a tactical error, as AEO is essentially good SEO done right, but optimized for a new type of consumer: the LLM crawler. The strategic differentiator is the target. While SEO focuses on ranking for a specific keyword string, AEO focuses on becoming the definitive, "grounded" answer for an LLM's Retrieval-Augmented Generation (RAG) process. You are no longer just competing for a spot on a page; you are competing to be the "source of truth" that the AI uses to build its response. This requires a shift from keyword density to semantic relevance, ensuring your brand is the primary noun associated with the user’s intent.

The Technical Foundation: How LLM Crawlers Work In an AI-first world, site architecture is your most critical growth lever. If your site structure is opaque, your brand effectively does not exist to GPTBot, OAI-Search, or ClaudeBot. These crawlers aren't just looking for text; they are looking for "facts" they can tokenize and ground in reality. To be discoverable, your site must move beyond basic indexability toward high Information Density. This means leveraging structured data—specifically JSON-LD and Schema.org—to provide explicit context that LLMs can parse without ambiguity. A logical, flat hierarchy and semantic HTML are no longer just "best practices"; they are the technical requirements that allow an AI to accurately cite your content. If the crawler can't map the relationship between your data points, the LLM will hallucinate a competitor's answer instead.

Content Strategy: Optimizing for Questions over Keywords The era of high-volume, low-utility content is over. LLMs are trained to filter out fluff in favor of precision. This necessitates a strategic shift from keyword-chasing to question-based optimization. AI citations are driven by how effectively a piece of content answers specific user queries ("Who," "How," "Why") with authoritative clarity. However, do not mistake precision for automation. In a sea of AI-generated noise, LLMs are increasingly prioritizing authentic, human-led authority and unique perspectives. They look for the "human in the loop"—the unique insights, data, and expertise that a generic model cannot synthesize on its own. To win citations, your content must be the most useful, high-fidelity answer available for a specific prompt.

The Reddit Effect: Authority and Community Influence The AEO ecosystem extends far beyond your own domain. AI models don't just "read" your website; they "listen" to the community to determine if you are actually an authority. This is why Reddit and other community platforms now have an outsized influence on LLM training data. If real humans are discussing your brand as a solution in a high-trust forum, the LLM recognizes that consensus as a signal of credibility. 

Pro-Tip: Focus on "Inverted Citations." Don't just post links; build a presence where your brand becomes the primary noun for a solution within community discussions. When Reddit users consistently name your product as the answer to a problem, you are effectively training the LLMs to cite you as the definitive source.

Measurement: The Three-Bucket Framework Traditional search metrics are failing to capture AEO success. If a user gets the answer they need from an AI without clicking, your "sessions" might drop, but your brand influence is actually growing. To prove value to executive leadership, we utilize a three-bucket framework:

• Bucket 1: Share of Model (SoM) and Prompt Visibility: Using tools like Perplexity or custom API scripts to track how often your brand is the "first-choice" answer for specific industry prompts.
• Bucket 2: Citation Depth and Grounding: Measuring the frequency and accuracy of citations. Is the AI linking to your primary research, or just mentioning your name in passing?
• Bucket 3: Indirect Brand Lift and Secondary Search: Analyzing the correlation between AI mentions and branded search volume. High AEO visibility should drive users to seek out the brand directly after the AI introduces them.

The Webflow AEO Maturity Model: Best Practices Based on the principles pioneered by Webflow’s Brett Domeny, this model serves as a roadmap for the top 1% of marketers who want to dominate the next decade of search.

• Content (Precision over Volume): Move from keyword-stuffing to direct answer frameworks.
  • Pro-Tip: Use the "Inverted Pyramid" for AI: provide the direct, unambiguous answer in the first 100 words to ensure easy tokenization by the crawler.
• Technical Structure (Machine-Readability): Transition to an API-first content mindset.
  • What most people miss: Your XML sitemaps and robots.txt must be specifically curated for LLM discovery. Ensure your JSON-LD is rich enough to "ground" the AI in your specific data.
• Authority (Community Validation): Treat third-party sentiment as a primary ranking factor.
  • Pro-Tip: Monitor Reddit for "unbranded" queries where your brand should be the answer, and ensure you are part of the conversation that trains the next model update.
• Measurement (The New KPI Suite): Stop reporting on clicks alone.
  • What most people miss: Show leadership the "Mindshare" within AI prompts. If you are the "Answer" 70% of the time for a high-intent prompt, you are winning, regardless of what Google Search Console says.

The shift from SEO to AEO is a fundamental evolution in how value is exchanged on the web. We are moving from a world of "search" to a world of "answers." While the underlying LLM technology is complex, the goal remains unchanged: providing the best possible utility to the user. By optimizing your technical foundations for machine-readability and your content for human authority, you ensure your brand isn't just a link in a list, but the answer to the question. Assess your AEO maturity today. Are you building a legacy archive, or are you becoming the source of truth for the AI era? The future belongs to those who provide the answers.

TL;DR: Alphabet just reported Q1 2026 ($109.9B revenue, +22% YoY) and ran I/O the same week. Gemini app MAU went from 350M to ~900M in 12 months. Token usage is up roughly 100x in 24 months — they're now processing about 2 quadrillion tokens per month. Google Cloud hit a $80B run-rate with a $462B backlog and 33% operating margin. Sundar Pichai said the business is "compute constrained" — demand exceeds supply. CapEx guidance for 2026 was raised to $185B. At I/O they shipped Gemini 3.5 Flash, Gemini Omni Video Model to replace Veo, Antigravity 2.0, an Agent OS called Gemini Spark to compete with Open Claw / Codex / Claude Cowork, two new TPU generations, and a $100/mo AI Ultra tier. Gemini 3.5 is now #1 on LMArena and WebDev Arena.

With the Apple deal it is likely 2 Billion people will be using Gemini by the end of the year.

Google is running away with this race.

The "Google is losing AI" narrative is officially dead.

I spent the last few days pulling data from the earnings call, the 10-Q, the I/O keynote, CB Insights, and Statista. Here's what stood out.

Gemini is now a billion-user product (basically).

• 350M MAU in April 2025 → ~900M MAU in Q1 2026
• On track to hit 1B by Q3 2026
• AI Overviews already reach 2B monthly users
• AI Mode has 100M+ users
• For comparison: ChatGPT mobile is at 557M

Token usage is the stat nobody is talking about enough.

• April 2024: 9.7 trillion tokens/month
• April 2025: 480 trillion
• November 2025: 1.3 quadrillion
• Q1 2026: ~2 quadrillion tokens/month
• Direct API alone: 16B tokens/minute (up from 10B last quarter)
• 330 customers process >1T tokens; 35 customers process >10T

That's roughly 100x growth in 24 months. Whatever you think the demand for AI is, it's bigger than that.

Google Cloud is now a real hyperscaler business.

• Q1 revenue: $20.02B (+63% YoY)
• Annualized run-rate: $80B+
• Operating income: $6.6B (3x YoY)
• Operating margin: 32.9% (up from 17.8%)
• Enterprise AI revenue: +800% YoY
• Backlog (RPO): $462B — nearly doubled in one quarter
• Gemini Enterprise paid MAU: +40% QoQ (Bosch, Citi, Merck, Mars are named customers)

Pichai said the quiet part out loud.
On the earnings call he said Google is "compute constrained" — meaning they can't build data centers and TPUs fast enough to meet demand. Hence:

• Q1 CapEx: $35.7B
• 2026 full-year guidance raised to $180–190B
• 60% goes to servers, 40% to data centers

For context, that's more than Microsoft, Meta, and Amazon's individual AI CapEx budgets.

I/O 2026 highlights (May 19-20):

• Gemini 3.5 Flash — 1,500 tokens/sec, 4x faster than other frontier models
• Gemini Omni — fully multimodal (text, image, audio, video from one input)
• Antigravity 2.0 — desktop agent app. Demo ran 93 sub-agents in parallel, 15K model requests, 2.6B tokens processed in 12 hours
• Gemini Spark — agent OS that operates across apps, browser, Android, and laptops
• TPU 8t (~3x compute) and TPU 8i (1,500 tok/s inference, scales to 1M+ TPUs)
• New AI Ultra $100/mo tier; top tier dropped from $250 to $200
• Build with Gemini XPRIZE — $2M prize pool
• Android XR + audio glasses shipping fall 2026

The developer ecosystem moat:

• 13 Million developers building on Gemini
• 2.4M monthly active API developers (+118% YoY)
• 85B API requests in January 2026
• 60%+ of gen-AI startups are on Google Cloud
• Lyria 3 has generated 150M songs, Nano Banana 2 has generated 1B images, Gemma 4 hit 50M downloads (500M total open-model downloads)

Per CB Insights: Google leads with 46 agent partnerships — 2x the nearest competitor. They're also driving the A2A (agent-to-agent) protocol. Microsoft Copilot is at ~15M users. Amazon's strategy is investing in 16 agent startups via AWS credits rather than building first-party.

Why this matters:
A year ago the consensus was that Google had lost AI to OpenAI. Today they have the best benchmarked model, the largest user base, the fastest-growing cloud business in absolute dollars, custom silicon nobody else has, and they're literally telling Wall Street they need to spend $185B just to keep up with demand.

Looks like Google is going to win the AI race.

Claude for Small Business is here. After a week of testing, here are the use cases that actually save time

TL;DR: Anthropic launched Claude for Small Business inside Claude Cowork. It connects Claude to the tools you already pay for (QuickBooks, PayPal, HubSpot, Canva, DocuSign, Google Workspace, Microsoft 365) and handles the recurring admin grind: payroll prep, monthly close, invoice follow-ups, cash flow checks, campaign planning, lead triage. The catch that actually isn't a catch: every action gets queued for your approval before anything sends, posts, or pays. You stay in the loop. Permissions still apply. On Team and Enterprise plans, it doesn't train on your data by default. Below is what I'd actually use it for, the pro tips nobody mentions in launch posts, and the things most people are going to miss in week one.

What it is, in one paragraph

You toggle on Claude for Small Business inside Claude Cowork, connect the tools you already use, and then describe the job you want done in plain English. Claude drafts the action (send these invoice reminders, prep this payroll run, post this campaign, summarize this month's books) and queues it for your review. Nothing fires until you say so. That last part is the whole point.

Top Use Cases (ranked by how much time they actually save)

1. Invoice follow-ups. Pulls aging receivables from QuickBooks, drafts polite-but-firm follow-up emails per customer, schedules them. The thing that takes you a full Friday afternoon every two weeks.
2. Monthly close prep. Reconciles, flags weird transactions, drafts the management summary. Doesn't replace your bookkeeper. Makes the handoff to your bookkeeper take 20 minutes instead of three days.
3. Cash flow visibility. Daily or weekly check-ins that actually look at your accounts and tell you what's coming, not generic dashboards you stop opening after week two.
4. Payroll planning. Pulls hours, flags anomalies, preps the run for your review. You still approve. You just don't have to assemble it.
5. Campaign execution. Drafts copy in Canva, schedules across channels, drafts customer update emails in HubSpot. Review and send.
6. Lead triage. Sorts new HubSpot leads by intent signals, drafts personalized first replies, queues them.
7. Customer insights. Reads through support threads or CRM notes and surfaces patterns. "Three customers complained about shipping in the last two weeks" type stuff.
8. Contract routing. DocuSign drafts pre-filled from your standard templates, ready to send.

How it works

1. Turn on Claude for Small Business inside Claude Cowork.
2. Connect the tools you already use (QuickBooks, PayPal, HubSpot, Canva, DocuSign, Google Workspace, Microsoft 365).
3. Describe what you want done.
4. Review the draft action.
5. Approve. Or don't. Nothing happens without you.

Pro tips

• Connect QuickBooks and your email on day one, even if you're not sure what you'll use it for. The invoice-follow-up flow alone pays for the subscription.
• Don't try to automate everything in week one. Pick the single most annoying recurring task you do and start there. Once you trust the approval queue, expand.
• Give it your standard operating procedures as context. If you have a "how we follow up on overdue invoices" doc, paste it in. The output quality jumps immediately.
• Use it as a second set of eyes on the monthly close before your bookkeeper sees it. Cheaper than billable hours catching mistakes you already made.
• For Canva and campaign work, give it the last three pieces of content that performed well. It picks up your voice fast.

Best practices

• Treat the approval queue like email triage. Block 15 minutes twice a day to clear it. Don't let it become its own pile.
• Keep tool permissions tight at first. You can always grant more access. Pulling it back after something weird happens is harder.
• Write your prompts like you're briefing a new hire, not querying a database. "Pull this week's overdue invoices and draft follow-ups in the same tone as the last three I sent" beats "follow up on invoices."
• Audit what it did once a week. Not because you don't trust it. Because that's how you learn what to delegate next.

Things most people are going to miss

• The data training default. On Team and Enterprise plans, Claude doesn't train on your data by default. This matters more than people realize, especially if you're plugging it into financial data and customer records. Check the setting anyway.
• It respects your existing permissions. If a team member can't see payroll in QuickBooks, Claude can't surface payroll info to them through Cowork either. This is the difference between an AI tool that's useful in a business and one that's a compliance nightmare.
• The approval gate is a feature, not friction. The reflex when you see "review before sending" is to wish it would just send. Resist that. The review is what lets you give it access to real money and real customers without losing sleep.
• It works best on recurring jobs, not one-offs. If you're doing something once, just do it. If you're doing something every Monday, every month-end, every customer onboarding, that's where this earns its keep.
• It's not a replacement for your accountant, your marketer, or your operations person. It's the layer that makes each of those people 30 to 40 percent more leveraged. Frame it that way to your team and adoption goes smoother.

The "AI for small business" pitch has been mostly vapor for two years. This is the first version I've used where the connectors are the ones I actually use, the approval model is sane, and the use cases line up with the work that actually piles up on Friday afternoons. Worth a week of real testing if you run a small business.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

Claude for Small Business is here. After a week of testing, here are the use cases that actually save time

TL;DR: Anthropic launched Claude for Small Business inside Claude Cowork. It connects Claude to the tools you already pay for (QuickBooks, PayPal, HubSpot, Canva, DocuSign, Google Workspace, Microsoft 365) and handles the recurring admin grind: payroll prep, monthly close, invoice follow-ups, cash flow checks, campaign planning, lead triage. The catch that actually isn't a catch: every action gets queued for your approval before anything sends, posts, or pays. You stay in the loop. Permissions still apply. On Team and Enterprise plans, it doesn't train on your data by default. Below is what I'd actually use it for, the pro tips nobody mentions in launch posts, and the things most people are going to miss in week one.

What it is, in one paragraph

You toggle on Claude for Small Business inside Claude Cowork, connect the tools you already use, and then describe the job you want done in plain English. Claude drafts the action (send these invoice reminders, prep this payroll run, post this campaign, summarize this month's books) and queues it for your review. Nothing fires until you say so. That last part is the whole point.

Top Use Cases (ranked by how much time they actually save)

1. Invoice follow-ups. Pulls aging receivables from QuickBooks, drafts polite-but-firm follow-up emails per customer, schedules them. The thing that takes you a full Friday afternoon every two weeks.
2. Monthly close prep. Reconciles, flags weird transactions, drafts the management summary. Doesn't replace your bookkeeper. Makes the handoff to your bookkeeper take 20 minutes instead of three days.
3. Cash flow visibility. Daily or weekly check-ins that actually look at your accounts and tell you what's coming, not generic dashboards you stop opening after week two.
4. Payroll planning. Pulls hours, flags anomalies, preps the run for your review. You still approve. You just don't have to assemble it.
5. Campaign execution. Drafts copy in Canva, schedules across channels, drafts customer update emails in HubSpot. Review and send.
6. Lead triage. Sorts new HubSpot leads by intent signals, drafts personalized first replies, queues them.
7. Customer insights. Reads through support threads or CRM notes and surfaces patterns. "Three customers complained about shipping in the last two weeks" type stuff.
8. Contract routing. DocuSign drafts pre-filled from your standard templates, ready to send.

How it works

1. Turn on Claude for Small Business inside Claude Cowork.
2. Connect the tools you already use (QuickBooks, PayPal, HubSpot, Canva, DocuSign, Google Workspace, Microsoft 365).
3. Describe what you want done.
4. Review the draft action.
5. Approve. Or don't. Nothing happens without you.

Pro tips

• Connect QuickBooks and your email on day one, even if you're not sure what you'll use it for. The invoice-follow-up flow alone pays for the subscription.
• Don't try to automate everything in week one. Pick the single most annoying recurring task you do and start there. Once you trust the approval queue, expand.
• Give it your standard operating procedures as context. If you have a "how we follow up on overdue invoices" doc, paste it in. The output quality jumps immediately.
• Use it as a second set of eyes on the monthly close before your bookkeeper sees it. Cheaper than billable hours catching mistakes you already made.
• For Canva and campaign work, give it the last three pieces of content that performed well. It picks up your voice fast.

Best practices

• Treat the approval queue like email triage. Block 15 minutes twice a day to clear it. Don't let it become its own pile.
• Keep tool permissions tight at first. You can always grant more access. Pulling it back after something weird happens is harder.
• Write your prompts like you're briefing a new hire, not querying a database. "Pull this week's overdue invoices and draft follow-ups in the same tone as the last three I sent" beats "follow up on invoices."
• Audit what it did once a week. Not because you don't trust it. Because that's how you learn what to delegate next.

Things most people are going to miss

• The data training default. On Team and Enterprise plans, Claude doesn't train on your data by default. This matters more than people realize, especially if you're plugging it into financial data and customer records. Check the setting anyway.
• It respects your existing permissions. If a team member can't see payroll in QuickBooks, Claude can't surface payroll info to them through Cowork either. This is the difference between an AI tool that's useful in a business and one that's a compliance nightmare.
• The approval gate is a feature, not friction. The reflex when you see "review before sending" is to wish it would just send. Resist that. The review is what lets you give it access to real money and real customers without losing sleep.
• It works best on recurring jobs, not one-offs. If you're doing something once, just do it. If you're doing something every Monday, every month-end, every customer onboarding, that's where this earns its keep.
• It's not a replacement for your accountant, your marketer, or your operations person. It's the layer that makes each of those people 30 to 40 percent more leveraged. Frame it that way to your team and adoption goes smoother.

The AI for small business pitch has been mostly vapor for two years. This is the first version I've used where the connectors are the ones I actually use, the approval model is sane, and the use cases line up with the work that actually piles up on Friday afternoons. Worth a week of real testing if you run a small business.

Claude Cowork is easy to misunderstand.

Most people will look at it and think, “Cool, Claude can organize my files now.”

That is true, but it undersells the shift.

Cowork is not just another chatbot tab. It can work across local folders, use project context, create outputs directly on your machine, research topics, organize documents, build reports, and keep going on longer tasks without the normal stop-start feeling of a chat thread.

That is why it feels powerful.

It is also why you should not treat it like a normal chatbot.

Once an AI agent can read, write, create, move, and in some cases delete files, your workflow needs a few basic operating rules. The goal is not to avoid using it. The goal is to use it like a careful operator, not a magic intern with the keys to your whole laptop.

Here are the 25 tips I would give anyone starting with Claude Cowork.

#	Tip	Why it matters
1	Use Cowork inside Claude Desktop.	Open Claude Desktop and switch into the Cowork / Tasks area before assigning work. Cowork is built for delegated tasks, not normal back-and-forth chat.
2	Know the big caveat.	Cowork is agentic. It can interact with files, tools, and desktop resources in ways that have real consequences.
3	Limit folder access.	Create a dedicated Cowork folder and only share the files it actually needs. Do not hand it your entire desktop or documents folder by default.
4	Modify the working folder deliberately.	Cowork can read and create files in a selected folder, so pick the workspace like you would pick a staging area for a human assistant.
5	Back up first.	Before file cleanup, renaming, deduping, or conversion tasks, make a copy. File operations are where small misunderstandings become annoying fast.
6	Ask for a plan before execution.	Use this prompt: “Show your plan and the exact files you’ll touch. Wait for my approval before making changes.”
7	Keep the app open.	Cowork depends on your desktop being awake and Claude Desktop being open. If the app closes or your computer sleeps, work can stop or be delayed.
8	Limit web access.	Only extend browser or network access to trusted sites. A browser-capable AI agent is useful, but the web is messy.
9	Treat web pages as untrusted.	Web content can contain hidden or indirect instructions. Prompt injection is not theoretical when the model can act on your files or apps.
10	Avoid sensitive financial documents.	Use scrubbed exports, redacted copies, or fake data whenever possible. Do not casually expose bank statements, tax records, payroll, legal docs, or credentials.
11	Create outputs directly to real files.	Cowork is valuable because it can produce the actual deliverable: a spreadsheet, memo, report, CSV, folder structure, or presentation draft.
12	Use it for close-pack hygiene.	Month-end folders, download dumps, exported reports, receipt folders, and messy screenshots are perfect Cowork jobs.
13	Batch rename for audit trails.	Ask it to standardize filenames with dates, vendors, entities, project names, or document types so files become searchable later.
14	Convert formats in batch.	Try tasks like: “Convert all CSV exports into one consolidated CSV and create a summary markdown file explaining columns, row counts, and anomalies.”
15	Turn scattered notes into a report.	Drop meeting notes, research notes, links, and rough docs into a folder. Ask Cowork to synthesize them into a structured brief.
16	Turn transcripts into actions.	Feed it meeting transcripts and ask for themes, decisions, risks, owners, next steps, and follow-up drafts.
17	Turn images into spreadsheet-style outputs.	If you have screenshots of tables, dashboards, receipts, or lists, ask Cowork to extract the useful fields into a spreadsheet.
18	Use research-to-presentation workflows.	Cowork can combine research, local notes, and structured output into a presentation outline, spreadsheet, or report.
19	Use it for research synthesis.	The strongest use case is not “search the web.” It is “combine web research with the messy internal notes already sitting in my folder.”
20	Use it for long-running tasks.	Give Cowork work that benefits from persistence: file cleanup, research briefs, recurring reports, dataset prep, and document organization.
21	Use sub-agent style coordination carefully.	For complex jobs, ask Cowork to divide the task into research, analysis, drafting, and QA passes. Still require a plan and approval gates.
22	Remember isolated execution is not total isolation.	Some work may run in a VM-like environment, but changes can still affect real files if you granted access. Treat the shared folder as live.
23	Connect tools intentionally.	Connectors are useful because they are often faster and more reliable than screen-clicking. But every connector expands the blast radius.
24	Be careful with local plugins and MCPs.	Extensions and MCP servers can expand what Claude can do. Install only what you trust and understand.
25	Use admin controls if you are on a team.	Team and Enterprise owners should think about Cowork access, web access, connectors, telemetry, scheduling rules, and training before rolling it out broadly.

The simplest way to use Cowork safely is to build a Cowork workspace folder.

Inside it, create a few subfolders:

Folder	Purpose
/input	Put only the files Claude is allowed to read or modify.
/working	Let Cowork create drafts, intermediate files, and transformed data here.
/output	Ask Cowork to place finished reports, summaries, spreadsheets, and exports here.
/archive	Move original source files here after the task is complete.
/do-not-touch	Keep reference files here if Claude should read but not modify them.

Then start with a prompt like this:

I want you to work only inside this folder. First inspect the files and summarize what you see. Then show me your plan, including the exact files you intend to read, create, rename, move, edit, or delete. Do not modify anything until I approve the plan.

For finance workflows, I would be even stricter:

Use only the redacted files in this folder. If a file appears to contain bank account numbers, tax IDs, payroll details, full card numbers, passwords, private contracts, or personal health data, stop and ask before reading or processing it.

For transcript workflows:

Review these meeting transcripts and create three files: an executive summary, a decisions-and-open-questions table, and an action-items list with owner, due date, and confidence level. Do not invent owners or dates. Mark missing information as unknown.

For cleanup workflows:

Propose a folder structure and filename convention first. Do not delete files. Do not overwrite originals. Create a mapping table showing old filename, new filename, destination folder, and reason.

That last detail matters.

The power move is not “let the AI do everything.”

The power move is giving it a narrow workspace, a clear outcome, and a checkpoint before it touches anything important.

Cowork can absolutely make you faster. It can turn file piles into structured outputs. It can convert scattered notes into reports. It can help with recurring research and admin-heavy workflows that would normally eat an afternoon.

But the best users will pair automation with control.

Claude Cowork is not a chatbot you prompt. It is a work agent you supervise.

That difference changes how you should use it.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

Claude Cowork is easy to misunderstand.

Most people will look at it and think, “Cool, Claude can organize my files now.”

That is true, but it undersells the shift.

Cowork is not just another chatbot tab. It can work across local folders, use project context, create outputs directly on your machine, research topics, organize documents, build reports, and keep going on longer tasks without the normal stop-start feeling of a chat thread.

That is why it feels powerful.

It is also why you should not treat it like a normal chatbot.

Once an AI agent can read, write, create, move, and in some cases delete files, your workflow needs a few basic operating rules. The goal is not to avoid using it. The goal is to use it like a careful operator, not a magic intern with the keys to your whole laptop.

Here are the 25 tips I would give anyone starting with Claude Cowork.

#	Tip	Why it matters
1	Use Cowork inside Claude Desktop.	Open Claude Desktop and switch into the Cowork / Tasks area before assigning work. Cowork is built for delegated tasks, not normal back-and-forth chat.
2	Know the big caveat.	Cowork is agentic. It can interact with files, tools, and desktop resources in ways that have real consequences.
3	Limit folder access.	Create a dedicated Cowork folder and only share the files it actually needs. Do not hand it your entire desktop or documents folder by default.
4	Modify the working folder deliberately.	Cowork can read and create files in a selected folder, so pick the workspace like you would pick a staging area for a human assistant.
5	Back up first.	Before file cleanup, renaming, deduping, or conversion tasks, make a copy. File operations are where small misunderstandings become annoying fast.
6	Ask for a plan before execution.	Use this prompt: “Show your plan and the exact files you’ll touch. Wait for my approval before making changes.”
7	Keep the app open.	Cowork depends on your desktop being awake and Claude Desktop being open. If the app closes or your computer sleeps, work can stop or be delayed.
8	Limit web access.	Only extend browser or network access to trusted sites. A browser-capable AI agent is useful, but the web is messy.
9	Treat web pages as untrusted.	Web content can contain hidden or indirect instructions. Prompt injection is not theoretical when the model can act on your files or apps.
10	Avoid sensitive financial documents.	Use scrubbed exports, redacted copies, or fake data whenever possible. Do not casually expose bank statements, tax records, payroll, legal docs, or credentials.
11	Create outputs directly to real files.	Cowork is valuable because it can produce the actual deliverable: a spreadsheet, memo, report, CSV, folder structure, or presentation draft.
12	Use it for close-pack hygiene.	Month-end folders, download dumps, exported reports, receipt folders, and messy screenshots are perfect Cowork jobs.
13	Batch rename for audit trails.	Ask it to standardize filenames with dates, vendors, entities, project names, or document types so files become searchable later.
14	Convert formats in batch.	Try tasks like: “Convert all CSV exports into one consolidated CSV and create a summary markdown file explaining columns, row counts, and anomalies.”
15	Turn scattered notes into a report.	Drop meeting notes, research notes, links, and rough docs into a folder. Ask Cowork to synthesize them into a structured brief.
16	Turn transcripts into actions.	Feed it meeting transcripts and ask for themes, decisions, risks, owners, next steps, and follow-up drafts.
17	Turn images into spreadsheet-style outputs.	If you have screenshots of tables, dashboards, receipts, or lists, ask Cowork to extract the useful fields into a spreadsheet.
18	Use research-to-presentation workflows.	Cowork can combine research, local notes, and structured output into a presentation outline, spreadsheet, or report.
19	Use it for research synthesis.	The strongest use case is not “search the web.” It is “combine web research with the messy internal notes already sitting in my folder.”
20	Use it for long-running tasks.	Give Cowork work that benefits from persistence: file cleanup, research briefs, recurring reports, dataset prep, and document organization.
21	Use sub-agent style coordination carefully.	For complex jobs, ask Cowork to divide the task into research, analysis, drafting, and QA passes. Still require a plan and approval gates.
22	Remember isolated execution is not total isolation.	Some work may run in a VM-like environment, but changes can still affect real files if you granted access. Treat the shared folder as live.
23	Connect tools intentionally.	Connectors are useful because they are often faster and more reliable than screen-clicking. But every connector expands the blast radius.
24	Be careful with local plugins and MCPs.	Extensions and MCP servers can expand what Claude can do. Install only what you trust and understand.
25	Use admin controls if you are on a team.	Team and Enterprise owners should think about Cowork access, web access, connectors, telemetry, scheduling rules, and training before rolling it out broadly.

The simplest way to use Cowork safely is to build a Cowork workspace folder.

Inside it, create a few subfolders:

Folder	Purpose
/input	Put only the files Claude is allowed to read or modify.
/working	Let Cowork create drafts, intermediate files, and transformed data here.
/output	Ask Cowork to place finished reports, summaries, spreadsheets, and exports here.
/archive	Move original source files here after the task is complete.
/do-not-touch	Keep reference files here if Claude should read but not modify them.

Then start with a prompt like this:

I want you to work only inside this folder. First inspect the files and summarize what you see. Then show me your plan, including the exact files you intend to read, create, rename, move, edit, or delete. Do not modify anything until I approve the plan.

For finance workflows, I would be even stricter:

Use only the redacted files in this folder. If a file appears to contain bank account numbers, tax IDs, payroll details, full card numbers, passwords, private contracts, or personal health data, stop and ask before reading or processing it.

For transcript workflows:

Review these meeting transcripts and create three files: an executive summary, a decisions-and-open-questions table, and an action-items list with owner, due date, and confidence level. Do not invent owners or dates. Mark missing information as unknown.

For cleanup workflows:

Propose a folder structure and filename convention first. Do not delete files. Do not overwrite originals. Create a mapping table showing old filename, new filename, destination folder, and reason.

That last detail matters.

The power move is not “let the AI do everything.”

The power move is giving it a narrow workspace, a clear outcome, and a checkpoint before it touches anything important.

Cowork can absolutely make you faster. It can turn file piles into structured outputs. It can convert scattered notes into reports. It can help with recurring research and admin-heavy workflows that would normally eat an afternoon.

But the best users will pair automation with control.

Claude Cowork is not a chatbot you prompt. It is a work agent you supervise.

That difference changes how you should use it.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

I tested 9 research prompts on the new version of ChatGPT 5.5 this week.

A content idea is cheap.

A researched angle is different.

A researched angle tells you what people are already talking about, what competitors already covered, what nobody has explained well, what the data says, what experts disagree on, what Reddit users complain about, and which claims you should verify before publishing.

That is the real use case.

Not “write me a post about this topic”

More like:

“Before I write, show me what is true, what is recent, what is disputed, what is missing, and what my audience actually cares about.”

That is where these prompts helped.

OpenAI’s own Deep Research materials describe the feature as a research agent that scans many sources, synthesizes findings, and produces structured reports with citations. That is useful. But the same workflow still needs a human editor. Citations help you trace claims, but they do not remove the need to open the source and check the claim yourself. Library guidance has also warned for years that AI systems can produce fake or mismatched citations when prompted loosely.

So I rebuilt the prompts around one rule:

No claim without a source. No source without a date. No stat without context. No angle without a reason it matters.

Here is the full set.

The 9-Prompt Content Research Stack

Step	Prompt	What it does	Best use case
1	Niche Trend Scanner	Finds current topics gaining momentum.	Picking what to write about this week.
2	Competitive Gap Finder	Shows what ranking content covers and misses.	Finding a non-generic angle.
3	Stat and Data Hunter	Pulls recent numbers with sources and context.	Making posts more credible.
4	Expert Consensus Miner	Summarizes expert agreement and disagreement.	Adding authority without pretending certainty.
5	Deep Research Briefer	Builds a full source-backed briefing.	Replacing a long research session.
6	Reddit Pain Point Finder	Finds recurring complaints and questions.	Writing from lived pain, not assumptions.
7	Academic Source Builder	Finds peer-reviewed or authoritative research.	Adding rigor to bigger claims.
8	Fresh Angle Generator	Finds overlooked or counterintuitive angles.	Escaping the same post everyone else writes.
9	Pre-Publish Fact Checker	Checks claims before publishing.	Protecting trust and credibility.

1. Niche Trend Scanner

Most people use ChatGPT to brainstorm topics.

That is too broad.

A better move is asking it to find topics that are already showing movement, then asking for the underexplored angle.

Act as a content trend analyst for [NICHE]. Use live web research only. Find the top 5 topics in [NICHE] gaining traction in the last 30 days. For each topic, return:

1. Trend name.
2. One-sentence explanation.
3. Why it is gaining traction now.
4. Evidence of momentum, including source name, URL, publication date, and the exact signal you used.
5. The audience most likely to care.
6. One obvious angle everyone will cover.
7. One underexplored angle I can cover instead.
8. One Reddit-style post hook. 9. Confidence score from 1–5. Rules:
   - Do not include evergreen topics unless there is fresh evidence from the last 30 days.
   - Do not use vague signals like “many people are discussing.” Name the source and signal.
   - If evidence is weak, say so.
   - End with the single strongest topic to write about this week and explain why.

Why this works

This prompt forces the model to separate topic popularity from topic momentum. Those are not the same thing. Popular topics are crowded. Momentum topics still have room.

Pro tip

Ask for “one obvious angle” and “one underexplored angle” in the same prompt. That contrast is where the post often appears.

2. Competitive Gap Finder

This is the prompt I would use before writing any SEO post, LinkedIn longform, Reddit guide, or newsletter.

Most content repeats because writers only research the topic.

They do not research the existing conversation.

PROMPT:

You are an SEO strategist and editorial researcher.

Keyword/topic: [KEYWORD]

Target audience: [AUDIENCE]
Content format I want to create: [REDDIT POST / LINKEDIN POST / NEWSLETTER / BLOG POST / VIDEO SCRIPT]

Search the live web for the top 10 high-ranking or highly shared pieces about this keyword. Create a table with:

1. Title.
2. Publisher or author.
3. URL.
4. Publication or update date.
5. Main thesis.
6. Key subtopics covered.
7. Evidence used.
8. What the piece does well.
9. What it ignores, oversimplifies, or leaves unsupported. Then synthesize:
   - The 5 themes everyone repeats.
   - The 5 questions almost nobody answers.
   - The 3 strongest content gaps.
   - The best contrarian or overlooked angle for my audience.
   - The ideal format for that angle. - A sharper headline for the piece I should create.
   Rules:
   - Cite every source with URL and date.
   - Do not invent rankings. If ranking position is uncertain, label it “visible result,” not “rank.”
   - Prioritize gaps that matter to the audience, not trivia.

Why this works

If 10 pieces already say the same thing, your job is not to write the 11th version.

Your job is to explain what the first 10 missed.

Pro tip

After the model finds the gaps, ask: “Which of these gaps would make a smart reader disagree in the comments?” That usually reveals the highest-engagement angle.

3. Stat and Data Hunter

Numbers change the feel of a post.

A claim sounds like opinion.

A claim with a current number sounds like something readers need to evaluate.

Prompt

Act as a research assistant for a creator writing about [TOPIC].

Find 7 current statistics about [TOPIC] published in the last 12 months. For each statistic, include:

1. Exact figure.

2. What it measures.

3. Source name.

4. URL.

5. Publication date.

6. Original context of the number.

7. Why it matters to a creator or operator.

8. One sentence I could use in a post.

9. Any caveat, sample limitation, or reason the stat might be misleading.
   Source priority:

10. Primary research reports.

11. Government or academic sources.

12. Company data with clear methodology.

13. Reputable industry surveys.

14. News summaries only if they link to the primary source.
    Rules:
    - Do not include a statistic unless you can provide the original source URL.
    - Do not use a number from a roundup unless you trace it back to the primary source.

- If you cannot find 7 strong stats, return fewer and explain why.

Why this works

The extra line that matters is: “Original context of the number.”

Many bad posts misuse good statistics because they strip away the methodology, audience, or timeframe.

Pro tip

Ask the model to label each statistic as hook stat, support stat, or context stat. Hook stats can open the post. Support stats belong in the body. Context stats prevent oversimplification.

4. Expert Consensus Miner

Expert quotes make content stronger, but only when they show the actual debate.

A lazy expert prompt gives you generic agreement.

A useful expert prompt gives you consensus plus tension.

Prompt

Act as an expert consensus researcher.

Topic: [TOPIC]
Audience: [AUDIENCE]
Time window: last 90 days unless the best source is older and still clearly relevant. Search for what credible experts, analysts, researchers, operators, and practitioners are saying about [TOPIC].

Return:

1. Three consensus points most credible people seem to agree on.

2. Two contrarian or minority views.

3. The strongest quote supporting each consensus point.

4. The strongest quote supporting each contrarian view.

5. Name, title, organization, and credibility reason for every expert.

6. Source URL and publication date for every quote or paraphrase.

7. What this means for someone creating content about the topic. Then answer: - Where is the real disagreement?

- Which view is most overrepresented online?

- Which view is underexplored but credible?

- What should I not claim because the evidence is still unsettled? Rules:

- Do not treat influencers as experts unless they have relevant operating, research, or domain experience.

- Separate direct quotes from paraphrases.

- If experts disagree, show the disagreement instead of smoothing it over.

Why this works

The best content does not pretend certainty where the field is split.

It shows the split clearly and helps the reader think.

Pro tip

Use expert disagreement as the frame. “The real debate is not X. It is Y.” That structure almost always performs better than a generic “Here are 5 expert tips” post.

5. Deep Research Briefer

This is the one that replaced my Sunday research session.

Use Deep Research mode for this prompt if you have it. OpenAI describes Deep Research as useful for comparing options, synthesizing complex information, and building evidence-backed briefs with citations.

Copy-Paste Prompt

Use Deep Research mode.

Act as a senior research analyst preparing a creator briefing on [TOPIC].

Objective: Help me write a source-backed post that is useful, current, and not the same angle everyone else is publishing.

Research questions:

1. What has changed about [TOPIC] in the last 90 days?

2. Who are the key players, researchers, companies, communities, or creators shaping the conversation?

3. What are the major debates?

4. What claims are well-supported?

5. What claims are popular but weakly supported?

6. What contradictions appear across sources?

7. What is one overlooked angle a smart creator could own?

Output format:

- Executive summary in 150 words.

- Timeline of recent developments.

- Key players table. - Major debates table.

- 10-source annotated bibliography.

- 5 strongest stats or findings.

- 5 content angles ranked by originality and evidence strength.

- Final recommendation: the one angle I should write. Rules:

- Use at least 10 credible sources.

- Include URL, date, source type, and why each source is credible.

- Flag contradictions instead of hiding them.

- Do not write the final post yet. Build the briefing first.

Why this works

The last rule matters: do not write the final post yet.

When you ask for writing too early, the model rushes past the research.

Pro tip

Ask for the “claims that are popular but weakly supported.” That section often saves you from publishing a confident-sounding mistake.

6. Reddit Pain Point Finder

This might be the most underrated prompt in the stack.

Search data tells you what people look for.

Reddit tells you what people are frustrated enough to complain about.

Prompt

Switch to Reddit-focused research.
Topic: [TOPIC]
Target audience: [AUDIENCE]
Time window: last 6 months.
Search Reddit for discussions about [TOPIC].

Prioritize threads with real complaints, repeated questions, strong disagreement, or detailed user stories. Return the 5 most common pain points. For each pain point, include:

1. Plain-English pain point.

2. The user’s underlying concern.

3. Representative quote or paraphrase.

4. Subreddit and thread URL.

5. Date.

6. How often this theme appears across the discussions you found.

7. What most content gets wrong about this pain point. 8. A post angle that directly addresses it.

8. A Reddit-style hook using the audience’s language. Then synthesize:

- The emotional pattern behind the complaints.

- The false assumption creators make about this audience.

- The one post I should write if I want comments, not just upvotes. Rules:

- Do not expose private or sensitive information.

- Do not cherry-pick one extreme comment and pretend it is consensus.

- Separate recurring pain from isolated anecdotes.

Why this works

A lot of content fails because it answers the question the creator wishes people had.

Reddit shows you the question people are actually asking.

Pro tip

Do not copy Reddit language directly. Use it to understand vocabulary, objections, and emotional stakes. Then write your own version.

7. Academic Source Builder

This prompt is not for every post.

It is for posts where you are making a bigger claim and need more than vibes.

Prompt

Act as a fact-checking researcher.
Claim or topic: [CLAIM OR TOPIC]

Find 5 peer-reviewed studies, authoritative reports, or high-quality research papers published after 2022 that are relevant to this claim.

For each source, return:

1. Full title.

2. Authors or organization.

3. Publication year.

4. Source URL or DOI.

5. Study type or methodology.

6. Sample size or evidence base, if available.

7. One-sentence finding.

8. How directly it supports, weakens, or complicates my claim.

9. Credibility rating from 1–5 with reason.

10. One caveat a responsible writer should mention. Then synthesize:
    - What the research supports strongly.
    - What remains uncertain.
    - Whether any studies contradict each other.
    - The safest version of the claim I can publish.
    Rules:
    - Do not include fake citations.

- If you cannot verify a study exists, exclude it.

- Prefer DOI, publisher page, PubMed, arXiv, SSRN, university, government, or recognized research organization pages.

Why this works

It asks the model to judge the relationship between the source and your claim.

That is more useful than a list of papers.

Pro tip

Use the output to make your claim narrower. A narrower true claim beats a broad unsupported claim.

8. Fresh Angle Generator

This prompt is for crowded topics.

If everyone is posting about the same thing, the answer is not to write faster.

The answer is to look for the thing they are not saying.

Prompt

Act as a viral content strategist and research analyst.

Topic: [TOPIC] Audience: [AUDIENCE]
Platform: [REDDIT / LINKEDIN / X / NEWSLETTER]

Search recent articles, reports, podcasts, Reddit threads, expert posts, and data from the last 60 days.

Find 5 fresh content angles that avoid the obvious framing. For each angle, include:

1. Angle name.

2. One-sentence thesis.

3. Why this angle is non-obvious.

4. Evidence that supports it.

5. Source URL and date.

6. What most creators are saying instead.

7. Who would disagree and why.

8. One hook line.

9. Best content format.

10. Risk level: low, medium, or high. Score each angle from 1–5 on:

- Stop-scroll strength.

- Evidence strength.

- Novelty.

- Audience relevance.

- Comment potential.

End by recommending the single best angle and explaining why.

Why this works

A good angle is not merely “different.”

It is different, defensible, and relevant.

Pro tip

The “who would disagree and why” line is crucial. If nobody would disagree, it is probably not an angle. It is a summary.

9. Pre-Publish Fact Checker

This is the prompt I would run before publishing anything that includes stats, named companies, expert claims, or scientific research.

It is also the prompt most people skip.

That is a mistake.

Prompt

Act as a skeptical fact-checking editor.
I am about to publish a post.
Below are the claims I make.

Claims: [PASTE CLAIMS]
Check each claim using live web research. Create a table with:

1. Claim.

2. Verdict: accurate, mostly accurate, partially accurate, unsupported, misleading, or false. 3. Supporting source URL.

3. Contradicting source URL, if any.

4. Publication date of source.

5. Explanation in plain English.

6. Suggested rewrite if the claim is too broad, outdated, or unsupported.

7. Confidence score from 1–5. Then list:

- Claims I should remove.

- Claims I should soften.

- Claims that need a better source.

- Claims that are safe to publish as written.

Rules:

- Be strict.

- Do not protect my draft.

- If a source does not directly support the claim, mark it unsupported.

- Prefer primary sources over summaries.

Why this works

Publishing one wrong claim can cost more trust than ten good posts build.

This prompt gives the model permission to be the editor, not the cheerleader.

Pro tip

Paste claims only, not the entire post. If you paste the whole post, the model may get distracted by style. Claim-by-claim checking is cleaner.

Best Practices That Made These Prompts Work Better

Best practice	Why it matters	Example instruction to add
Force source metadata	A source without a date or URL is hard to verify.	“Include source name, URL, publication date, and source type.”
Ask for caveats	Many statistics are true but easy to misuse.	“Add one caveat or limitation for each finding.”
Separate consensus from debate	Content gets stronger when it shows tension.	“List consensus points and credible minority views separately.”
Use recency windows	Research prompts drift into stale examples without time limits.	“Prioritize sources from the last 30/60/90 days.”
Demand contradictions	Contradictions reveal where the real story is.	“Flag sources that disagree and explain the conflict.”
Delay drafting	Writing too early weakens the research.	“Do not write the post yet. Build the research brief first.”
Check claims at the end	The first answer is not the final answer.	“Verify every claim before publishing.”

OpenAI’s own prompt guidance recommends being specific about desired context, outcome, format, length, and style, and using explicit output formats where possible. That advice matters here. The more specific the research job, the less generic the answer.

Top Use Cases

Use case	Best prompt combination
Finding what to post this week	Niche Trend Scanner + Reddit Pain Point Finder
Writing a contrarian LinkedIn post	Competitive Gap Finder + Fresh Angle Generator
Building a serious Reddit guide	Deep Research Briefer + Academic Source Builder + Pre-Publish Fact Checker
Creating a newsletter essay	Expert Consensus Miner + Stat and Data Hunter + Deep Research Briefer
Improving an SEO article	Competitive Gap Finder + Stat and Data Hunter
Finding YouTube video topics	Niche Trend Scanner + Reddit Pain Point Finder + Fresh Angle Generator
Turning a hot topic into a credible post	Stat and Data Hunter + Expert Consensus Miner + Pre-Publish Fact Checker
Building a prompt library	Save each prompt as a reusable step in the same workflow

Things Most People Miss

The first thing people miss is that sources are not the same as proof. A model can return a source that exists but does not actually support the claim. That is why the fact-checking prompt asks whether the source directly supports the sentence you want to publish.

The second thing people miss is that freshness and credibility are different filters. A source can be recent and weak. Another source can be older but foundational. The prompt should tell ChatGPT which one matters for the job.

The third thing people miss is that Reddit research is not quote mining. The goal is not to steal lines from users. The goal is to understand repeated frustrations, language patterns, and unresolved questions.

The fourth thing people miss is that expert consensus is only half the story. The best post often lives where credible people disagree. If the model only gives you agreement, ask for minority views.

The fifth thing people miss is that the best prompt in the stack is the last one. Pre-publish fact-checking feels boring until it saves you from publishing something wrong.

My 15-Minute Workflow

Minute	Action
0–3	Run Niche Trend Scanner to pick the topic.
3–6	Run Reddit Pain Point Finder to understand what people actually complain about.
6–9	Run Competitive Gap Finder to avoid repeating the same angle.
9–12	Run Stat and Data Hunter or Expert Consensus Miner to add proof.
12–15	Run Fresh Angle Generator, pick one angle, then fact-check the final claims before posting.

If the topic is bigger, I use the Deep Research Briefer and treat it like a full research session.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

TLDR - Check the attached presentation

I tested 9 research prompts on the new version of ChatGPT 5.5 this week.

A content idea is cheap.

A researched angle is different.

A researched angle tells you what people are already talking about, what competitors already covered, what nobody has explained well, what the data says, what experts disagree on, what Reddit users complain about, and which claims you should verify before publishing.

That is the real use case.

Not “write me a post about this topic”

More like:

“Before I write, show me what is true, what is recent, what is disputed, what is missing, and what my audience actually cares about.”

That is where these prompts helped.

OpenAI’s own Deep Research materials describe the feature as a research agent that scans many sources, synthesizes findings, and produces structured reports with citations. That is useful. But the same workflow still needs a human editor. Citations help you trace claims, but they do not remove the need to open the source and check the claim yourself. Library guidance has also warned for years that AI systems can produce fake or mismatched citations when prompted loosely.

So I rebuilt the prompts around one rule:

No claim without a source. No source without a date. No stat without context. No angle without a reason it matters.

Here is the full set.

The 9-Prompt Content Research Stack

Step	Prompt	What it does	Best use case
1	Niche Trend Scanner	Finds current topics gaining momentum.	Picking what to write about this week.
2	Competitive Gap Finder	Shows what ranking content covers and misses.	Finding a non-generic angle.
3	Stat and Data Hunter	Pulls recent numbers with sources and context.	Making posts more credible.
4	Expert Consensus Miner	Summarizes expert agreement and disagreement.	Adding authority without pretending certainty.
5	Deep Research Briefer	Builds a full source-backed briefing.	Replacing a long research session.
6	Reddit Pain Point Finder	Finds recurring complaints and questions.	Writing from lived pain, not assumptions.
7	Academic Source Builder	Finds peer-reviewed or authoritative research.	Adding rigor to bigger claims.
8	Fresh Angle Generator	Finds overlooked or counterintuitive angles.	Escaping the same post everyone else writes.
9	Pre-Publish Fact Checker	Checks claims before publishing.	Protecting trust and credibility.

1. Niche Trend Scanner

Most people use ChatGPT to brainstorm topics.

That is too broad.

A better move is asking it to find topics that are already showing movement, then asking for the underexplored angle.

Act as a content trend analyst for [NICHE]. Use live web research only. Find the top 5 topics in [NICHE] gaining traction in the last 30 days. For each topic, return:

1. Trend name.
2. One-sentence explanation.
3. Why it is gaining traction now.
4. Evidence of momentum, including source name, URL, publication date, and the exact signal you used.
5. The audience most likely to care.
6. One obvious angle everyone will cover.
7. One underexplored angle I can cover instead.
8. One Reddit-style post hook. 9. Confidence score from 1–5. Rules:
   - Do not include evergreen topics unless there is fresh evidence from the last 30 days.
   - Do not use vague signals like “many people are discussing.” Name the source and signal.
   - If evidence is weak, say so.
   - End with the single strongest topic to write about this week and explain why.

Why this works

This prompt forces the model to separate topic popularity from topic momentum. Those are not the same thing. Popular topics are crowded. Momentum topics still have room.

Pro tip

Ask for “one obvious angle” and “one underexplored angle” in the same prompt. That contrast is where the post often appears.

2. Competitive Gap Finder

This is the prompt I would use before writing any SEO post, LinkedIn longform, Reddit guide, or newsletter.

Most content repeats because writers only research the topic.

They do not research the existing conversation.

PROMPT:

You are an SEO strategist and editorial researcher.

Keyword/topic: [KEYWORD]

Target audience: [AUDIENCE]
Content format I want to create: [REDDIT POST / LINKEDIN POST / NEWSLETTER / BLOG POST / VIDEO SCRIPT]

Search the live web for the top 10 high-ranking or highly shared pieces about this keyword. Create a table with:

1. Title.
2. Publisher or author.
3. URL.
4. Publication or update date.
5. Main thesis.
6. Key subtopics covered.
7. Evidence used.
8. What the piece does well.
9. What it ignores, oversimplifies, or leaves unsupported. Then synthesize:
   - The 5 themes everyone repeats.
   - The 5 questions almost nobody answers.
   - The 3 strongest content gaps.
   - The best contrarian or overlooked angle for my audience.
   - The ideal format for that angle. - A sharper headline for the piece I should create.
   Rules:
   - Cite every source with URL and date.
   - Do not invent rankings. If ranking position is uncertain, label it “visible result,” not “rank.”
   - Prioritize gaps that matter to the audience, not trivia.

Why this works

If 10 pieces already say the same thing, your job is not to write the 11th version.

Your job is to explain what the first 10 missed.

Pro tip

After the model finds the gaps, ask: “Which of these gaps would make a smart reader disagree in the comments?” That usually reveals the highest-engagement angle.

3. Stat and Data Hunter

Numbers change the feel of a post.

A claim sounds like opinion.

A claim with a current number sounds like something readers need to evaluate.

Prompt

Act as a research assistant for a creator writing about [TOPIC].

Find 7 current statistics about [TOPIC] published in the last 12 months. For each statistic, include:

1. Exact figure.

2. What it measures.

3. Source name.

4. URL.

5. Publication date.

6. Original context of the number.

7. Why it matters to a creator or operator.

8. One sentence I could use in a post.

9. Any caveat, sample limitation, or reason the stat might be misleading.
   Source priority:

10. Primary research reports.

11. Government or academic sources.

12. Company data with clear methodology.

13. Reputable industry surveys.

14. News summaries only if they link to the primary source.
    Rules:
    - Do not include a statistic unless you can provide the original source URL.
    - Do not use a number from a roundup unless you trace it back to the primary source.

- If you cannot find 7 strong stats, return fewer and explain why.

Why this works

The extra line that matters is: “Original context of the number.”

Many bad posts misuse good statistics because they strip away the methodology, audience, or timeframe.

Pro tip

Ask the model to label each statistic as hook stat, support stat, or context stat. Hook stats can open the post. Support stats belong in the body. Context stats prevent oversimplification.

4. Expert Consensus Miner

Expert quotes make content stronger, but only when they show the actual debate.

A lazy expert prompt gives you generic agreement.

A useful expert prompt gives you consensus plus tension.

Prompt

Act as an expert consensus researcher.

Topic: [TOPIC]
Audience: [AUDIENCE]
Time window: last 90 days unless the best source is older and still clearly relevant. Search for what credible experts, analysts, researchers, operators, and practitioners are saying about [TOPIC].

Return:

1. Three consensus points most credible people seem to agree on.

2. Two contrarian or minority views.

3. The strongest quote supporting each consensus point.

4. The strongest quote supporting each contrarian view.

5. Name, title, organization, and credibility reason for every expert.

6. Source URL and publication date for every quote or paraphrase.

7. What this means for someone creating content about the topic. Then answer: - Where is the real disagreement?

- Which view is most overrepresented online?

- Which view is underexplored but credible?

- What should I not claim because the evidence is still unsettled? Rules:

- Do not treat influencers as experts unless they have relevant operating, research, or domain experience.

- Separate direct quotes from paraphrases.

- If experts disagree, show the disagreement instead of smoothing it over.

Why this works

The best content does not pretend certainty where the field is split.

It shows the split clearly and helps the reader think.

Pro tip

Use expert disagreement as the frame. “The real debate is not X. It is Y.” That structure almost always performs better than a generic “Here are 5 expert tips” post.

5. Deep Research Briefer

This is the one that replaced my Sunday research session.

Use Deep Research mode for this prompt if you have it. OpenAI describes Deep Research as useful for comparing options, synthesizing complex information, and building evidence-backed briefs with citations.

Copy-Paste Prompt

Use Deep Research mode.

Act as a senior research analyst preparing a creator briefing on [TOPIC].

Objective: Help me write a source-backed post that is useful, current, and not the same angle everyone else is publishing.

Research questions:

1. What has changed about [TOPIC] in the last 90 days?

2. Who are the key players, researchers, companies, communities, or creators shaping the conversation?

3. What are the major debates?

4. What claims are well-supported?

5. What claims are popular but weakly supported?

6. What contradictions appear across sources?

7. What is one overlooked angle a smart creator could own?

Output format:

- Executive summary in 150 words.

- Timeline of recent developments.

- Key players table. - Major debates table.

- 10-source annotated bibliography.

- 5 strongest stats or findings.

- 5 content angles ranked by originality and evidence strength.

- Final recommendation: the one angle I should write. Rules:

- Use at least 10 credible sources.

- Include URL, date, source type, and why each source is credible.

- Flag contradictions instead of hiding them.

- Do not write the final post yet. Build the briefing first.

Why this works

The last rule matters: do not write the final post yet.

When you ask for writing too early, the model rushes past the research.

Pro tip

Ask for the “claims that are popular but weakly supported.” That section often saves you from publishing a confident-sounding mistake.

6. Reddit Pain Point Finder

This might be the most underrated prompt in the stack.

Search data tells you what people look for.

Reddit tells you what people are frustrated enough to complain about.

Prompt

Switch to Reddit-focused research.
Topic: [TOPIC]
Target audience: [AUDIENCE]
Time window: last 6 months.
Search Reddit for discussions about [TOPIC].

Prioritize threads with real complaints, repeated questions, strong disagreement, or detailed user stories. Return the 5 most common pain points. For each pain point, include:

1. Plain-English pain point.

2. The user’s underlying concern.

3. Representative quote or paraphrase.

4. Subreddit and thread URL.

5. Date.

6. How often this theme appears across the discussions you found.

7. What most content gets wrong about this pain point. 8. A post angle that directly addresses it.

8. A Reddit-style hook using the audience’s language. Then synthesize:

- The emotional pattern behind the complaints.

- The false assumption creators make about this audience.

- The one post I should write if I want comments, not just upvotes. Rules:

- Do not expose private or sensitive information.

- Do not cherry-pick one extreme comment and pretend it is consensus.

- Separate recurring pain from isolated anecdotes.

Why this works

A lot of content fails because it answers the question the creator wishes people had.

Reddit shows you the question people are actually asking.

Pro tip

Do not copy Reddit language directly. Use it to understand vocabulary, objections, and emotional stakes. Then write your own version.

7. Academic Source Builder

This prompt is not for every post.

It is for posts where you are making a bigger claim and need more than vibes.

Prompt

Act as a fact-checking researcher.
Claim or topic: [CLAIM OR TOPIC]

Find 5 peer-reviewed studies, authoritative reports, or high-quality research papers published after 2022 that are relevant to this claim.

For each source, return:

1. Full title.

2. Authors or organization.

3. Publication year.

4. Source URL or DOI.

5. Study type or methodology.

6. Sample size or evidence base, if available.

7. One-sentence finding.

8. How directly it supports, weakens, or complicates my claim.

9. Credibility rating from 1–5 with reason.

10. One caveat a responsible writer should mention. Then synthesize:
    - What the research supports strongly.
    - What remains uncertain.
    - Whether any studies contradict each other.
    - The safest version of the claim I can publish.
    Rules:
    - Do not include fake citations.

- If you cannot verify a study exists, exclude it.

- Prefer DOI, publisher page, PubMed, arXiv, SSRN, university, government, or recognized research organization pages.

Why this works

It asks the model to judge the relationship between the source and your claim.

That is more useful than a list of papers.

Pro tip

Use the output to make your claim narrower. A narrower true claim beats a broad unsupported claim.

8. Fresh Angle Generator

This prompt is for crowded topics.

If everyone is posting about the same thing, the answer is not to write faster.

The answer is to look for the thing they are not saying.

Prompt

Act as a viral content strategist and research analyst.

Topic: [TOPIC] Audience: [AUDIENCE]
Platform: [REDDIT / LINKEDIN / X / NEWSLETTER]

Search recent articles, reports, podcasts, Reddit threads, expert posts, and data from the last 60 days.

Find 5 fresh content angles that avoid the obvious framing. For each angle, include:

1. Angle name.

2. One-sentence thesis.

3. Why this angle is non-obvious.

4. Evidence that supports it.

5. Source URL and date.

6. What most creators are saying instead.

7. Who would disagree and why.

8. One hook line.

9. Best content format.

10. Risk level: low, medium, or high. Score each angle from 1–5 on:

- Stop-scroll strength.

- Evidence strength.

- Novelty.

- Audience relevance.

- Comment potential.

End by recommending the single best angle and explaining why.

Why this works

A good angle is not merely “different.”

It is different, defensible, and relevant.

Pro tip

The “who would disagree and why” line is crucial. If nobody would disagree, it is probably not an angle. It is a summary.

9. Pre-Publish Fact Checker

This is the prompt I would run before publishing anything that includes stats, named companies, expert claims, or scientific research.

It is also the prompt most people skip.

That is a mistake.

Prompt

Act as a skeptical fact-checking editor.
I am about to publish a post.
Below are the claims I make.

Claims: [PASTE CLAIMS]
Check each claim using live web research. Create a table with:

1. Claim.

2. Verdict: accurate, mostly accurate, partially accurate, unsupported, misleading, or false. 3. Supporting source URL.

3. Contradicting source URL, if any.

4. Publication date of source.

5. Explanation in plain English.

6. Suggested rewrite if the claim is too broad, outdated, or unsupported.

7. Confidence score from 1–5. Then list:

- Claims I should remove.

- Claims I should soften.

- Claims that need a better source.

- Claims that are safe to publish as written.

Rules:

- Be strict.

- Do not protect my draft.

- If a source does not directly support the claim, mark it unsupported.

- Prefer primary sources over summaries.

Why this works

Publishing one wrong claim can cost more trust than ten good posts build.

This prompt gives the model permission to be the editor, not the cheerleader.

Pro tip

Paste claims only, not the entire post. If you paste the whole post, the model may get distracted by style. Claim-by-claim checking is cleaner.

Best Practices That Made These Prompts Work Better

Best practice	Why it matters	Example instruction to add
Force source metadata	A source without a date or URL is hard to verify.	“Include source name, URL, publication date, and source type.”
Ask for caveats	Many statistics are true but easy to misuse.	“Add one caveat or limitation for each finding.”
Separate consensus from debate	Content gets stronger when it shows tension.	“List consensus points and credible minority views separately.”
Use recency windows	Research prompts drift into stale examples without time limits.	“Prioritize sources from the last 30/60/90 days.”
Demand contradictions	Contradictions reveal where the real story is.	“Flag sources that disagree and explain the conflict.”
Delay drafting	Writing too early weakens the research.	“Do not write the post yet. Build the research brief first.”
Check claims at the end	The first answer is not the final answer.	“Verify every claim before publishing.”

OpenAI’s own prompt guidance recommends being specific about desired context, outcome, format, length, and style, and using explicit output formats where possible. That advice matters here. The more specific the research job, the less generic the answer.

Top Use Cases

Use case	Best prompt combination
Finding what to post this week	Niche Trend Scanner + Reddit Pain Point Finder
Writing a contrarian LinkedIn post	Competitive Gap Finder + Fresh Angle Generator
Building a serious Reddit guide	Deep Research Briefer + Academic Source Builder + Pre-Publish Fact Checker
Creating a newsletter essay	Expert Consensus Miner + Stat and Data Hunter + Deep Research Briefer
Improving an SEO article	Competitive Gap Finder + Stat and Data Hunter
Finding YouTube video topics	Niche Trend Scanner + Reddit Pain Point Finder + Fresh Angle Generator
Turning a hot topic into a credible post	Stat and Data Hunter + Expert Consensus Miner + Pre-Publish Fact Checker
Building a prompt library	Save each prompt as a reusable step in the same workflow

Things Most People Miss

The first thing people miss is that sources are not the same as proof. A model can return a source that exists but does not actually support the claim. That is why the fact-checking prompt asks whether the source directly supports the sentence you want to publish.

The second thing people miss is that freshness and credibility are different filters. A source can be recent and weak. Another source can be older but foundational. The prompt should tell ChatGPT which one matters for the job.

The third thing people miss is that Reddit research is not quote mining. The goal is not to steal lines from users. The goal is to understand repeated frustrations, language patterns, and unresolved questions.

The fourth thing people miss is that expert consensus is only half the story. The best post often lives where credible people disagree. If the model only gives you agreement, ask for minority views.

The fifth thing people miss is that the best prompt in the stack is the last one. Pre-publish fact-checking feels boring until it saves you from publishing something wrong.

My 15-Minute Workflow

Minute	Action
0–3	Run Niche Trend Scanner to pick the topic.
3–6	Run Reddit Pain Point Finder to understand what people actually complain about.
6–9	Run Competitive Gap Finder to avoid repeating the same angle.
9–12	Run Stat and Data Hunter or Expert Consensus Miner to add proof.
12–15	Run Fresh Angle Generator, pick one angle, then fact-check the final claims before posting.

If the topic is bigger, I use the Deep Research Briefer and treat it like a full research session.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

You can use this personal brand prompt with a reference image to create a personal brand with ChatGPT or Google Gemini - both give good results.

Most people use ChatGPT images the wrong way.

They upload a photo and ask for a better headshot.

Sharper jaw. Cleaner lighting. More expensive background. Founder energy. Cinematic look. Premium vibe.

Then the result looks impressive for about three seconds.

After that, you notice the problem.

It looks like you, but not quite.

The eyes are slightly different. The face is a little too polished. The expression is not really yours. It feels like ChatGPT made a successful cousin who borrowed your LinkedIn account.

That is not a personal brand.

That is identity drift.

The better move is not to ask AI to make you look more attractive.

The better move is to ask AI to make you more recognizable.

A personal brand does not start with a logo. It starts with repeated recognition. People see the same face, colors, crop, tone, visual rhythm, and content style enough times that your account becomes familiar before they even read the name.

So instead of asking for one polished AI headshot, try asking for a full brand board built around your actual face.

Here is the prompt:

Turn this photo into a full personal brand sheet.

Keep my face and identity exactly the same.
Create a clean brand identity board around me with:

1. Professional profile photo version
2. Color palette based on the photo
3. Font style suggestions
4. 3 social media post template ideas
5. Personal brand keywords
6. Visual direction for my content
7. Profile picture crop
8. Cover photo concept
9. Content style moodboard
10. Simple brand rules

Make it look premium, clean, and modern.
Use a dark cinematic background.
Keep everything organized like a professional brand board.
Do not change my face. Do not beautify me.
Do not make me look like a different person.
Make it suitable for a creator, entrepreneur, or personal brand.

-

If you want better results, upload the cleanest photo you have. Good lighting. Face visible. No heavy filters. No sunglasses. No weird crop. The photo does not need to be perfect, but it does need to be honest.

Then run the prompt once.

After the first version, do not immediately regenerate everything.

Refine it like a designer would:

Keep my face identical, but make the brand board more minimal and premium.

Keep the same layout, but make the color palette more serious and founder-oriented.

Keep the same face and identity, but make the social templates more suitable for LinkedIn and X.

Keep the same visual direction, but give me a cleaner profile crop and a stronger cover photo concept.

Now turn this into a simple one-page brand guide I can follow for future posts.

The goal is not to walk away with one image.

The goal is to walk away with rules.

Use this type of board to answer questions like:

“What colors should my posts use?”

“What should my profile picture feel like?”

“What should my banner communicate?”

“What kind of templates should I repeat?”

“What should my content look like before someone reads a word?”

That last question matters more than people think.

A lot of creators have useful ideas, but their visual identity resets every week. One post looks corporate. The next looks like a podcast thumbnail. The next looks like a SaaS ad. The next looks like a motivational quote account.

Nothing compounds because nothing feels familiar.

This prompt fixes that by turning one real photo into a visual operating system.

You get a profile image. A color palette. Font direction. Post templates. Moodboard. Cover concept. Content keywords. Brand rules.

More importantly, you get constraints.

And constraints are what make a personal brand recognizable.

The brand board is everything that makes it repeatable.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

You can use this personal brand prompt with a reference image to create a personal brand with ChatGPT or Google Gemini - both give good results.

Most people use ChatGPT images the wrong way.

They upload a photo and ask for a better headshot.

Sharper jaw. Cleaner lighting. More expensive background. Founder energy. Cinematic look. Premium vibe.

Then the result looks impressive for about three seconds.

After that, you notice the problem.

It looks like you, but not quite.

The eyes are slightly different. The face is a little too polished. The expression is not really yours. It feels like ChatGPT made a successful cousin who borrowed your LinkedIn account.

That is not a personal brand.

That is identity drift.

The better move is not to ask AI to make you look more attractive.

The better move is to ask AI to make you more recognizable.

A personal brand does not start with a logo. It starts with repeated recognition. People see the same face, colors, crop, tone, visual rhythm, and content style enough times that your account becomes familiar before they even read the name.

So instead of asking for one polished AI headshot, try asking for a full brand board built around your actual face.

Here is the prompt:

Turn this photo into a full personal brand sheet.

Keep my face and identity exactly the same.
Create a clean brand identity board around me with:

1. Professional profile photo version
2. Color palette based on the photo
3. Font style suggestions
4. 3 social media post template ideas
5. Personal brand keywords
6. Visual direction for my content
7. Profile picture crop
8. Cover photo concept
9. Content style moodboard
10. Simple brand rules

Make it look premium, clean, and modern.
Use a dark cinematic background.
Keep everything organized like a professional brand board.
Do not change my face. Do not beautify me.
Do not make me look like a different person.
Make it suitable for a creator, entrepreneur, or personal brand.

-

If you want better results, upload the cleanest photo you have. Good lighting. Face visible. No heavy filters. No sunglasses. No weird crop. The photo does not need to be perfect, but it does need to be honest.

Then run the prompt once.

After the first version, do not immediately regenerate everything.

Refine it like a designer would:

Keep my face identical, but make the brand board more minimal and premium.

Keep the same layout, but make the color palette more serious and founder-oriented.

Keep the same face and identity, but make the social templates more suitable for LinkedIn and X.

Keep the same visual direction, but give me a cleaner profile crop and a stronger cover photo concept.

Now turn this into a simple one-page brand guide I can follow for future posts.

The goal is not to walk away with one image.

The goal is to walk away with rules.

Use this type of board to answer questions like:

“What colors should my posts use?”

“What should my profile picture feel like?”

“What should my banner communicate?”

“What kind of templates should I repeat?”

“What should my content look like before someone reads a word?”

That last question matters more than people think.

A lot of creators have useful ideas, but their visual identity resets every week. One post looks corporate. The next looks like a podcast thumbnail. The next looks like a SaaS ad. The next looks like a motivational quote account.

Nothing compounds because nothing feels familiar.

This prompt fixes that by turning one real photo into a visual operating system.

You get a profile image. A color palette. Font direction. Post templates. Moodboard. Cover concept. Content keywords. Brand rules.

More importantly, you get constraints.

And constraints are what make a personal brand recognizable.

The brand board is everything that makes it repeatable.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

Claude isn’t cutting you off because you ask too much.

It is cutting you off because you make it reread junk.

That sounds harsh, but it is the simplest way to understand Claude limits. Anthropic says usage is affected by message length, file attachment size, current conversation length, tool usage, model choice, and artifact usage. It also says tools and connectors are token-intensive, and that Projects can cache reused content.

So the game is not “send fewer prompts.”

The game is stop making every prompt drag a shipping container of old context behind it.

Here are the 21 fixes I’d use before upgrading, rage-quitting, or blaming the model.

1. Stop uploading raw PDFs when you only need the text.

A PDF can carry formatting, images, layout noise, headers, footers, and junk Claude has to process. If you only need the words, extract the text first. Paste it into a clean doc, strip the clutter, then upload or paste the clean .md version.

Pro tip: Ask Claude for a “source-cleaning checklist” once, save it, and use it before every research-heavy session.

2. Do not build files in Cowork before the plan is clear.

A lot of people open a workspace, start creating files, then ask Claude to rethink the whole thing five times. That burns context fast.

Plan in Chat first. Get the outline, constraints, file names, acceptance criteria, and edge cases. Move into Cowork only when the build path is clear.

3. Replace giant prompts with a question-first prompt.

Most 500-word prompts are just anxiety with formatting.

Use this instead:

I want to [task] to [goal]. Ask me questions before you start.

If you want Claude to be stricter, add:

Ask only the questions that materially change the output.

This prevents Claude from solving the wrong problem for 20 minutes.

4. Never say “redo the whole thing” when only one section is broken.

That phrase is a context bonfire.

Use:

Only redo section 3. Keep everything else unchanged. No commentary. Just the replacement section.

This is one of the highest ROI habits on the list.

5. Batch related tasks into one message.

Do not send three separate messages like this:

Summarize this.
Now list the key points.
Now suggest a headline.

Send one message:

Summarize this, list the key points, and suggest 10 headlines ranked by curiosity.

Claude’s own best-practice docs recommend batching similar requests.

6. Edit the original prompt instead of stacking corrections.

When you type “no, I meant…” five times, the chat now contains the mistake, the correction, the second correction, and the apology tour.

If the first prompt was wrong, edit it and regenerate. Do not preserve a bad branch unless the history matters.

7. Stop rewriting prompts from scratch.

Keep a prompt library.

Use the same structure and swap the variable. This matters because Anthropic says similar prompts can be partially cached. Even when caching is not visible to you, repeatable prompt structure reduces your own setup cost.

My default structure: role, task, source material, constraints, output format, quality bar.

8. Stop using Opus for tiny chores.

Using Opus for a grammar check is like hiring a neurosurgeon to open a jar.

Use Sonnet or Haiku for quick rewrites, summaries, formatting, grammar, extraction, and simple planning. Save Opus and Extended Thinking for deep strategy, hard reasoning, high-stakes writing, architecture, and debugging.

9. Trim your “about me” or brand file.

A 22,000-word brand file feels thorough. It is usually a tax.

Make a tight version under 2,000 words. Include voice, offers, audience, proof, banned phrases, and examples. At the end of important sessions, ask:

Write a compact session-notes .md file I can reuse later. Include decisions, constraints, open questions, and next actions.

That one habit turns messy context into reusable context.

10. Restart from the last clean point.

When a Cowork session goes sideways, do not keep arguing with the current branch.

Go back to the last useful message and restart from there. The goal is to cut away the confused middle, not make Claude reason through it forever.

11. Summarize before the chat gets heavy.

Every 15–20 messages, ask Claude for a transfer brief:

Summarize this session for a fresh Claude chat. Preserve decisions, files, constraints, terminology, and next steps. Remove dead ends.

Then start a fresh chat with that summary.

Most people wait until the chat is already bloated. That is too late.

12. Use Projects for recurring files.

If you reuse the same documents, do not upload them every time.

Use Projects. Anthropic says Project content is cached when reused, and only new or uncached portions count against limits. That is exactly what you want for brand docs, product notes, customer research, style guides, SOPs, and reference libraries.

13. Do not dump 50 files into Cowork “just in case.”

Claude does not need your entire digital attic to write one email.

Attach only the files this task needs. For quick tasks, attach zero files and paste only the relevant excerpt.

What most people miss: irrelevant files still compete for attention even when Claude ignores them.

14. New topic means new chat.

A LinkedIn post, a travel plan, a recipe, and a pricing page do not belong in one thread.

Claude re-reads the conversation context. Dead context becomes dead weight.

New topic, new chat. Always.

15. Turn off search and connectors by default.

Do not leave every tool on because it feels powerful.

Anthropic says tools and connectors are token-intensive. Keep web search, Research, MCP connectors, and other tools off by default. Turn them on per task.

A simple rewrite does not need the internet.

16. Schedule recurring tasks instead of re-prompting them manually.

If you run the same report every week, stop rebuilding it from memory.

Claude Code docs say scheduled tasks can re-run prompts automatically on an interval. Use this for weekly briefings, deployment checks, PR monitoring, dependency checks, and recurring research.

Important: session-scoped scheduled tasks expire after seven days, so use durable options like Routines, Desktop scheduled tasks, or GitHub Actions when the task needs to survive beyond one session.

17. Do not let Claude Code explore your whole repo by default.

Bad prompt:

Look through the repo and improve it.

Better prompt:

In /analytics, build a bar chart from sales.csv. Save it as chart.png. Do not inspect unrelated folders unless needed.

Claude Code is great when the target is clear. It is expensive when you ask it to wander.

18. Set Personal Preferences once.

If you keep typing the same tone, formatting, and style instructions, move them into settings.

Set your default tone, structure, preferred output style, and banned behaviors once. Then every prompt can focus on the actual task.

19. Speak rich prompts instead of typing lazy ones.

“Make it better” creates follow-up loops.

Use dictation if you think faster than you type. A spoken prompt often includes the real context: what you tried, what failed, who the output is for, and what “good” means.

The rule is simple: more useful context once beats vague context five times.

20. Split work across the rolling window.

Claude usage is not a simple daily bucket. Paid users can see five-hour session usage and weekly usage in Settings → Usage.

Do not burn the whole window in one morning on low-value tasks. Do lightweight prep outside the heavy session. Then use the expensive window for the tasks that actually need Claude.

21. Stop using Claude for jobs another tool does better.

Claude is excellent for reasoning, writing, coding, analysis, and long-context work.

But if the job is image generation, real-time social search, transcription, spreadsheet cleanup, or simple file conversion, ask whether another tool is cheaper or better.

Use Claude where Claude is strongest.

That is the real “hack.”

You are not trying to squeeze one more prompt out of the subscription.

You are trying to stop paying for repeated confusion.

If you remember one line, remember this:

Claude limits are not just message limits. They are context limits, tool limits, file limits, model limits, and habit limits stacked together.

Fix the habits and the subscription feels completely different.

Top Use Cases People Miss

Use case	How to save Claude usage
Weekly market or competitor briefings	Schedule the recurring task or keep a reusable Project brief instead of rebuilding the prompt each week.
Long-form writing	Keep the voice guide short, summarize every 15–20 turns, and ask Claude to revise only the weak section.
Coding tasks	Name the folder, file, expected output, and exclusions so Claude Code does not explore the whole repo.
Research synthesis	Clean PDFs into Markdown first, attach only the sources you need, and start a fresh chat with a transfer brief when the thread gets long.
Brand/content production	Store the brand file in Projects and reuse a prompt-library template rather than retyping style instructions.
Simple edits	Use Sonnet or Haiku, not Opus, and avoid Extended Thinking unless the task truly requires reasoning.
Tool-heavy work	Turn search, Research, connectors, MCP tools, and file access on only for the specific task that needs them.

What Most People Miss

Most users focus on the visible limit message, but the invisible leak is context drag. They keep too many topics in one thread, attach too many files, leave tools enabled, ask for full rewrites, and then blame the subscription. The better habit is to treat every Claude session like a clean workbench: bring only the materials needed for the job, do the expensive thinking in the right model, save the reusable result, and start fresh before the mess becomes the context.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

Claude isn’t cutting you off because you ask too much.

It is cutting you off because you make it reread junk.

That sounds harsh, but it is the simplest way to understand Claude limits. Anthropic says usage is affected by message length, file attachment size, current conversation length, tool usage, model choice, and artifact usage. It also says tools and connectors are token-intensive, and that Projects can cache reused content.

So the game is not “send fewer prompts.”

The game is stop making every prompt drag a shipping container of old context behind it.

Here are the 21 fixes I’d use before upgrading, rage-quitting, or blaming the model.

1. Stop uploading raw PDFs when you only need the text.

A PDF can carry formatting, images, layout noise, headers, footers, and junk Claude has to process. If you only need the words, extract the text first. Paste it into a clean doc, strip the clutter, then upload or paste the clean .md version.

Pro tip: Ask Claude for a “source-cleaning checklist” once, save it, and use it before every research-heavy session.

2. Do not build files in Cowork before the plan is clear.

A lot of people open a workspace, start creating files, then ask Claude to rethink the whole thing five times. That burns context fast.

Plan in Chat first. Get the outline, constraints, file names, acceptance criteria, and edge cases. Move into Cowork only when the build path is clear.

3. Replace giant prompts with a question-first prompt.

Most 500-word prompts are just anxiety with formatting.

Use this instead:

I want to [task] to [goal]. Ask me questions before you start.

If you want Claude to be stricter, add:

Ask only the questions that materially change the output.

This prevents Claude from solving the wrong problem for 20 minutes.

4. Never say “redo the whole thing” when only one section is broken.

That phrase is a context bonfire.

Use:

Only redo section 3. Keep everything else unchanged. No commentary. Just the replacement section.

This is one of the highest ROI habits on the list.

5. Batch related tasks into one message.

Do not send three separate messages like this:

Summarize this.
Now list the key points.
Now suggest a headline.

Send one message:

Summarize this, list the key points, and suggest 10 headlines ranked by curiosity.

Claude’s own best-practice docs recommend batching similar requests.

6. Edit the original prompt instead of stacking corrections.

When you type “no, I meant…” five times, the chat now contains the mistake, the correction, the second correction, and the apology tour.

If the first prompt was wrong, edit it and regenerate. Do not preserve a bad branch unless the history matters.

7. Stop rewriting prompts from scratch.

Keep a prompt library.

Use the same structure and swap the variable. This matters because Anthropic says similar prompts can be partially cached. Even when caching is not visible to you, repeatable prompt structure reduces your own setup cost.

My default structure: role, task, source material, constraints, output format, quality bar.

8. Stop using Opus for tiny chores.

Using Opus for a grammar check is like hiring a neurosurgeon to open a jar.

Use Sonnet or Haiku for quick rewrites, summaries, formatting, grammar, extraction, and simple planning. Save Opus and Extended Thinking for deep strategy, hard reasoning, high-stakes writing, architecture, and debugging.

9. Trim your “about me” or brand file.

A 22,000-word brand file feels thorough. It is usually a tax.

Make a tight version under 2,000 words. Include voice, offers, audience, proof, banned phrases, and examples. At the end of important sessions, ask:

Write a compact session-notes .md file I can reuse later. Include decisions, constraints, open questions, and next actions.

That one habit turns messy context into reusable context.

10. Restart from the last clean point.

When a Cowork session goes sideways, do not keep arguing with the current branch.

Go back to the last useful message and restart from there. The goal is to cut away the confused middle, not make Claude reason through it forever.

11. Summarize before the chat gets heavy.

Every 15–20 messages, ask Claude for a transfer brief:

Summarize this session for a fresh Claude chat. Preserve decisions, files, constraints, terminology, and next steps. Remove dead ends.

Then start a fresh chat with that summary.

Most people wait until the chat is already bloated. That is too late.

12. Use Projects for recurring files.

If you reuse the same documents, do not upload them every time.

Use Projects. Anthropic says Project content is cached when reused, and only new or uncached portions count against limits. That is exactly what you want for brand docs, product notes, customer research, style guides, SOPs, and reference libraries.

13. Do not dump 50 files into Cowork “just in case.”

Claude does not need your entire digital attic to write one email.

Attach only the files this task needs. For quick tasks, attach zero files and paste only the relevant excerpt.

What most people miss: irrelevant files still compete for attention even when Claude ignores them.

14. New topic means new chat.

A LinkedIn post, a travel plan, a recipe, and a pricing page do not belong in one thread.

Claude re-reads the conversation context. Dead context becomes dead weight.

New topic, new chat. Always.

15. Turn off search and connectors by default.

Do not leave every tool on because it feels powerful.

Anthropic says tools and connectors are token-intensive. Keep web search, Research, MCP connectors, and other tools off by default. Turn them on per task.

A simple rewrite does not need the internet.

16. Schedule recurring tasks instead of re-prompting them manually.

If you run the same report every week, stop rebuilding it from memory.

Claude Code docs say scheduled tasks can re-run prompts automatically on an interval. Use this for weekly briefings, deployment checks, PR monitoring, dependency checks, and recurring research.

Important: session-scoped scheduled tasks expire after seven days, so use durable options like Routines, Desktop scheduled tasks, or GitHub Actions when the task needs to survive beyond one session.

17. Do not let Claude Code explore your whole repo by default.

Bad prompt:

Look through the repo and improve it.

Better prompt:

In /analytics, build a bar chart from sales.csv. Save it as chart.png. Do not inspect unrelated folders unless needed.

Claude Code is great when the target is clear. It is expensive when you ask it to wander.

18. Set Personal Preferences once.

If you keep typing the same tone, formatting, and style instructions, move them into settings.

Set your default tone, structure, preferred output style, and banned behaviors once. Then every prompt can focus on the actual task.

19. Speak rich prompts instead of typing lazy ones.

“Make it better” creates follow-up loops.

Use dictation if you think faster than you type. A spoken prompt often includes the real context: what you tried, what failed, who the output is for, and what “good” means.

The rule is simple: more useful context once beats vague context five times.

20. Split work across the rolling window.

Claude usage is not a simple daily bucket. Paid users can see five-hour session usage and weekly usage in Settings → Usage.

Do not burn the whole window in one morning on low-value tasks. Do lightweight prep outside the heavy session. Then use the expensive window for the tasks that actually need Claude.

21. Stop using Claude for jobs another tool does better.

Claude is excellent for reasoning, writing, coding, analysis, and long-context work.

But if the job is image generation, real-time social search, transcription, spreadsheet cleanup, or simple file conversion, ask whether another tool is cheaper or better.

Use Claude where Claude is strongest.

That is the real “hack.”

You are not trying to squeeze one more prompt out of the subscription.

You are trying to stop paying for repeated confusion.

If you remember one line, remember this:

Claude limits are not just message limits. They are context limits, tool limits, file limits, model limits, and habit limits stacked together.

Fix the habits and the subscription feels completely different.

Top Use Cases People Miss

Use case	How to save Claude usage
Weekly market or competitor briefings	Schedule the recurring task or keep a reusable Project brief instead of rebuilding the prompt each week.
Long-form writing	Keep the voice guide short, summarize every 15–20 turns, and ask Claude to revise only the weak section.
Coding tasks	Name the folder, file, expected output, and exclusions so Claude Code does not explore the whole repo.
Research synthesis	Clean PDFs into Markdown first, attach only the sources you need, and start a fresh chat with a transfer brief when the thread gets long.
Brand/content production	Store the brand file in Projects and reuse a prompt-library template rather than retyping style instructions.
Simple edits	Use Sonnet or Haiku, not Opus, and avoid Extended Thinking unless the task truly requires reasoning.
Tool-heavy work	Turn search, Research, connectors, MCP tools, and file access on only for the specific task that needs them.

What Most People Miss

Most users focus on the visible limit message, but the invisible leak is context drag. They keep too many topics in one thread, attach too many files, leave tools enabled, ask for full rewrites, and then blame the subscription. The better habit is to treat every Claude session like a clean workbench: bring only the materials needed for the job, do the expensive thinking in the right model, save the reusable result, and start fresh before the mess becomes the context.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

TL;DR: Most people prompt Claude like they are writing polite emails. That adds filler, ambiguity, and friction. Start prompts with one shortcut command instead. I tested 32 shortcut prompts, and they cut my prompting time by almost 80% because Claude does not need manners. It needs direction.

Claude shortcuts are the new keyboard shortcuts for AI.

That sounds like a small shift.

It is not.

Most people still prompt like they are writing emails.

“Can you please help me…”

“Here’s some context…”

“Maybe try to…”

“Could you make this a little better…”

That style feels natural because we learned to communicate with people before we learned to direct models.

But Claude is not a coworker waiting for social softness.

Claude does not need manners.

It needs commands.

I tested this with 32 shortcut prompts, and it cut my prompting time by almost 80%.

Not because the model suddenly became smarter.

Because the instruction got cleaner.

The biggest unlock was starting every prompt with a shortcut.

Not a paragraph.

Not a preamble.

Not a soft request.

A command.

Here are the five shortcut families I now use constantly.

Shortcut Family	Use It When	Examples
Compress	The answer is too long, too complex, or too boring.	/TLDL, /BRIEFLY, /EXEC SUMMARY, /ELI5
Control Format	You need structure instead of prose.	/CHECKLIST, /FORMAT AS, /SCHEMA, /BEGIN WITH — /END WITH
Change Lens	The content is directionally right but contextually wrong.	/TONE, /AUDIENCE, /ACT AS, /REWRITE AS
Think Better	You need reasoning quality, not just word output.	/FIRST PRINCIPLES, /STEP-BY-STEP, /PITFALLS, /MULTI-PERSPECTIVE
Remove Garbage	The output sounds generic, lazy, or overconfident.	/NO AUTOPILOT, /EVAL-SELF, /GUARDRAIL, /SYSTEMATIC BIAS CHECK

Here is what changed for me.

When I wrote normal prompts, Claude had to infer the job.

When I used shortcuts, Claude knew the job before reading the rest of the request.

That is the difference.

A shortcut sets the operating mode first.

Then the prompt gives the details.

For example, instead of writing:

Can you read this and summarize the most important points in a way a busy executive would understand?

I write:

/EXEC SUMMARY Summarize this for a busy executive. Focus on decisions, risks, and next actions.

Instead of writing:

Can you make this more useful and maybe turn it into something I can actually follow?

I write:

/CHECKLIST Convert this into a step-by-step execution checklist. Start each line with a verb.

Instead of writing:

Can you think through this carefully and tell me what might go wrong?

I write:

/PITFALLS Identify the failure modes, hidden assumptions, and second-order consequences.

This feels almost too simple.

That is why it works.

The best AI prompts are not long.

They are directional.

The shortcut tells Claude what kind of cognitive work to perform.

The rest of the prompt tells Claude what material to work on.

Once you see it, long polite prompts start to look like clicking through five menus instead of pressing Cmd + K.

The old skill was “prompt writing.”

The new skill is direction design.

That means you are not trying to sound articulate.

You are trying to reduce ambiguity.

You are choosing the job before you describe the task.

Here is the simple rule I now use:

Start every prompt with one shortcut.

If the output is too long, start with /TLDL.

If the output is messy, start with /FORMAT AS.

If the output is generic, start with /NO AUTOPILOT.

If the output is shallow, start with /FIRST PRINCIPLES.

If the output is risky, start with /GUARDRAIL.

If the output needs to fit a reader, start with /AUDIENCE.

This turns Claude from a chatbot into an operator.

And it changes the user’s job too.

You stop asking Claude to “help.”

You start directing Claude to compress, structure, translate, critique, stress-test, and execute.

That is the real upgrade.

Most AI output is not bad because the model is weak.

It is bad because the instruction is lazy.

Start with one shortcut.

Then add the task.

You will get cleaner answers, faster drafts, and fewer rewrites.

My take:

Claude shortcuts are not a prompting trick. They are the keyboard shortcuts for AI work.

What shortcut would you add to the list?

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

TL;DR: Most people prompt Claude like they are writing polite emails. That adds filler, ambiguity, and friction. Start prompts with one shortcut command instead. I tested 32 shortcut prompts, and they cut my prompting time by almost 80% because Claude does not need manners. It needs direction.

Claude shortcuts are the new keyboard shortcuts for AI.

That sounds like a small shift.

It is not.

Most people still prompt like they are writing emails.

“Can you please help me…”

“Here’s some context…”

“Maybe try to…”

“Could you make this a little better…”

That style feels natural because we learned to communicate with people before we learned to direct models.

But Claude is not a coworker waiting for social softness.

Claude does not need manners.

It needs commands.

I tested this with 32 shortcut prompts, and it cut my prompting time by almost 80%.

Not because the model suddenly became smarter.

Because the instruction got cleaner.

The biggest unlock was starting every prompt with a shortcut.

Not a paragraph.

Not a preamble.

Not a soft request.

A command.

Here are the five shortcut families I now use constantly.

Shortcut Family	Use It When	Examples
Compress	The answer is too long, too complex, or too boring.	/TLDL, /BRIEFLY, /EXEC SUMMARY, /ELI5
Control Format	You need structure instead of prose.	/CHECKLIST, /FORMAT AS, /SCHEMA, /BEGIN WITH — /END WITH
Change Lens	The content is directionally right but contextually wrong.	/TONE, /AUDIENCE, /ACT AS, /REWRITE AS
Think Better	You need reasoning quality, not just word output.	/FIRST PRINCIPLES, /STEP-BY-STEP, /PITFALLS, /MULTI-PERSPECTIVE
Remove Garbage	The output sounds generic, lazy, or overconfident.	/NO AUTOPILOT, /EVAL-SELF, /GUARDRAIL, /SYSTEMATIC BIAS CHECK

Here is what changed for me.

When I wrote normal prompts, Claude had to infer the job.

When I used shortcuts, Claude knew the job before reading the rest of the request.

That is the difference.

A shortcut sets the operating mode first.

Then the prompt gives the details.

For example, instead of writing:

Can you read this and summarize the most important points in a way a busy executive would understand?

I write:

/EXEC SUMMARY Summarize this for a busy executive. Focus on decisions, risks, and next actions.

Instead of writing:

Can you make this more useful and maybe turn it into something I can actually follow?

I write:

/CHECKLIST Convert this into a step-by-step execution checklist. Start each line with a verb.

Instead of writing:

Can you think through this carefully and tell me what might go wrong?

I write:

/PITFALLS Identify the failure modes, hidden assumptions, and second-order consequences.

This feels almost too simple.

That is why it works.

The best AI prompts are not long.

They are directional.

The shortcut tells Claude what kind of cognitive work to perform.

The rest of the prompt tells Claude what material to work on.

Once you see it, long polite prompts start to look like clicking through five menus instead of pressing Cmd + K.

The old skill was “prompt writing.”

The new skill is direction design.

That means you are not trying to sound articulate.

You are trying to reduce ambiguity.

You are choosing the job before you describe the task.

Here is the simple rule I now use:

Start every prompt with one shortcut.

If the output is too long, start with /TLDL.

If the output is messy, start with /FORMAT AS.

If the output is generic, start with /NO AUTOPILOT.

If the output is shallow, start with /FIRST PRINCIPLES.

If the output is risky, start with /GUARDRAIL.

If the output needs to fit a reader, start with /AUDIENCE.

This turns Claude from a chatbot into an operator.

And it changes the user’s job too.

You stop asking Claude to “help.”

You start directing Claude to compress, structure, translate, critique, stress-test, and execute.

That is the real upgrade.

Most AI output is not bad because the model is weak.

It is bad because the instruction is lazy.

Start with one shortcut.

Then add the task.

You will get cleaner answers, faster drafts, and fewer rewrites.

My take:

Claude shortcuts are not a prompting trick. They are the keyboard shortcuts for AI work.

What shortcut would you add to the list?

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

TL;DR: Most people prompt Claude like they are writing polite emails. That adds filler, ambiguity, and friction. Start prompts with one shortcut command instead. I tested 32 shortcut prompts, and they cut my prompting time by almost 80% because Claude does not need manners. It needs direction.

Claude shortcuts are the new keyboard shortcuts for AI.

That sounds like a small shift.

It is not.

Most people still prompt like they are writing emails.

“Can you please help me…”

“Here’s some context…”

“Maybe try to…”

“Could you make this a little better…”

That style feels natural because we learned to communicate with people before we learned to direct models.

But Claude is not a coworker waiting for social softness.

Claude does not need manners.

It needs commands.

I tested this with 32 shortcut prompts, and it cut my prompting time by almost 80%.

Not because the model suddenly became smarter.

Because the instruction got cleaner.

The biggest unlock was starting every prompt with a shortcut.

Not a paragraph.

Not a preamble.

Not a soft request.

A command.

Here are the five shortcut families I now use constantly.

Shortcut Family	Use It When	Examples
Compress	The answer is too long, too complex, or too boring.	/TLDL, /BRIEFLY, /EXEC SUMMARY, /ELI5
Control Format	You need structure instead of prose.	/CHECKLIST, /FORMAT AS, /SCHEMA, /BEGIN WITH — /END WITH
Change Lens	The content is directionally right but contextually wrong.	/TONE, /AUDIENCE, /ACT AS, /REWRITE AS
Think Better	You need reasoning quality, not just word output.	/FIRST PRINCIPLES, /STEP-BY-STEP, /PITFALLS, /MULTI-PERSPECTIVE
Remove Garbage	The output sounds generic, lazy, or overconfident.	/NO AUTOPILOT, /EVAL-SELF, /GUARDRAIL, /SYSTEMATIC BIAS CHECK

Here is what changed for me.

When I wrote normal prompts, Claude had to infer the job.

When I used shortcuts, Claude knew the job before reading the rest of the request.

That is the difference.

A shortcut sets the operating mode first.

Then the prompt gives the details.

For example, instead of writing:

Can you read this and summarize the most important points in a way a busy executive would understand?

I write:

/EXEC SUMMARY Summarize this for a busy executive. Focus on decisions, risks, and next actions.

Instead of writing:

Can you make this more useful and maybe turn it into something I can actually follow?

I write:

/CHECKLIST Convert this into a step-by-step execution checklist. Start each line with a verb.

Instead of writing:

Can you think through this carefully and tell me what might go wrong?

I write:

/PITFALLS Identify the failure modes, hidden assumptions, and second-order consequences.

This feels almost too simple.

That is why it works.

The best AI prompts are not long.

They are directional.

The shortcut tells Claude what kind of cognitive work to perform.

The rest of the prompt tells Claude what material to work on.

Once you see it, long polite prompts start to look like clicking through five menus instead of pressing Cmd + K.

The old skill was “prompt writing.”

The new skill is direction design.

That means you are not trying to sound articulate.

You are trying to reduce ambiguity.

You are choosing the job before you describe the task.

Here is the simple rule I now use:

Start every prompt with one shortcut.

If the output is too long, start with /TLDL.

If the output is messy, start with /FORMAT AS.

If the output is generic, start with /NO AUTOPILOT.

If the output is shallow, start with /FIRST PRINCIPLES.

If the output is risky, start with /GUARDRAIL.

If the output needs to fit a reader, start with /AUDIENCE.

This turns Claude from a chatbot into an operator.

And it changes the user’s job too.

You stop asking Claude to “help.”

You start directing Claude to compress, structure, translate, critique, stress-test, and execute.

That is the real upgrade.

Most AI output is not bad because the model is weak.

It is bad because the instruction is lazy.

Start with one shortcut.

Then add the task.

You will get cleaner answers, faster drafts, and fewer rewrites.

My take:

Claude shortcuts are not a prompting trick. They are the keyboard shortcuts for AI work.

What shortcut would you add to the list?

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

Most AI training programs are solving the wrong problem.

They teach tools.

They do not build levels.

That distinction matters because the enterprise AI numbers now look absurd on the surface. McKinsey reports that 88% of organizations use AI in at least one business function, but most are still experimenting or piloting rather than scaling. DataCamp reports that 82% of enterprise leaders say their organization offers some AI training, yet 59% still report an AI skills gap.

So the gap is not access.

It is not budget.

It is not another platform procurement cycle.

The gap is that most leaders cannot answer one basic question:

What level of AI user is each person in our workforce right now?

That is the map every CXO needs before they buy another training module.

Here are the 7 levels of AI users I would map across a company.

Level	User Type	What They Actually Do	What They Need
1	The Avoider	Knows AI exists and actively avoids it. Often capable people protecting expertise, status, or quality standards.	Psychological safety, not pressure.
2	The Dabbler	Tried ChatGPT once or twice. Called it interesting. Has no repeat behavior.	One credible proof point tied to real work.
3	The Occasional User	Uses AI when stuck, not by default. Gets value in bursts, then disappears for weeks.	Habit infrastructure and obvious workflows.
4	The Routine Integrator	Uses AI daily for drafts, summaries, research, and admin work. Saves time but does not multiply output yet.	Better prompts, examples, and quality standards.
5	The Workflow Architect	Redesigns how work gets done. Builds reusable AI-supported processes for the team.	Visibility, mandate, and permission to redesign work.
6	The Strategic Multiplier	Uses AI to pressure-test decisions, generate insights, model scenarios, and sharpen judgment.	Retention, executive access, and decision rights.
7	The Agent Orchestrator	Designs and directs multi-step agentic workflows. Thinks in systems, not chats.	Investment now, because the talent market is moving fast.

The mistake is training everyone as if they are Level 2.

Avoiders do not need a prompt library first. They need safety.

Dabblers do not need a four-hour certification. They need a proof point.

Occasional Users do not need another tool demo. They need a default workflow.

Routine Integrators do not need hype. They need quality control.

Workflow Architects do not need permission to “experiment.” They need a mandate.

Strategic Multipliers do not need generic training. They need to be protected from being buried in low-leverage work.

Agent Orchestrators do not appear by accident. They need to be built, funded, and retained.

This is why so many AI training programs feel busy but produce little organizational lift.

• They optimize for attendance.
• They measure completions.
• They celebrate access.

Then leadership wonders why the business still has a skills gap.

The better move is simple:

1. Map every team by AI user level.

2.Stop giving every level the same training.

3. Build progression paths from Level 1 to Level 7.

4. Promote the people already redesigning work.

5. Treat agentic capability as a workforce strategy, not a software feature.

McKinsey’s AI research shows broad adoption, but scaling remains the hard part. Its Technology Trends Outlook also shows how quickly agentic AI work is becoming a labor-market signal, with agentic AI job postings up sharply in the 2023–2024 period.

That should change how executives think about AI training.

The next advantage will not come from which company “has AI.”

Everyone has AI now.

The advantage will come from which company knows exactly where its people are on the capability curve and moves them up intentionally.

The future AI-native organization will not be built by tool access. It will be built by level design.

Where do you think most employees are today: Level 2, Level 3, or Level 4?

Want some great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.