The default ChatGPT answer is one averaged voice. For anything with real tradeoffs - a decision, a strategy, a "should I do X or Y" - that averaging is the problem: it smooths over the disagreement, and the disagreement is exactly where the useful thinking lives.

So for those questions I make it argue with itself. This prompt turns one answer into a panel of three experts who genuinely disagree, plus a moderator who forces a conclusion out of it. Paste it, then ask your question.

For my next question, do NOT answer in one voice. Convene a panel of 3 experts who genuinely disagree on it.

For each expert:
- Give them a distinct role or school of thought (name the lens).
- Have them give their honest take in a few sentences.
- Have them say directly where they think the other two are wrong.

Then step in as a neutral moderator and give me:
- The point they all actually agree on.
- The single biggest real tension between them.
- What you would do, and the one thing that would change your answer.

Keep each voice short and sharp. No fence-sitting - I want the disagreement made explicit, not smoothed over.

Wait for my question before starting.

Why it works: a single answer picks the safest path and hides the tradeoff. Forcing three lenses to argue surfaces the objections you would have hit later anyway, and the "where the others are wrong" step stops it from just saying the same thing three times in different hats. The moderator step is what saves it from being three opinions and no decision.

Works best on genuinely contested questions (strategy, career, design, "is this a good idea") - overkill for anything with one correct answer.

(I keep it saved and drop it in with a // shortcut when I hit a real decision, instead of retyping it. Happy to share which extension in the comments if anyone wants. It works fine pasted by hand.)

Most weak answers are not the model's fault - they happen because it guesses what you meant instead of asking, then confidently runs 500 words in the wrong direction. The fix that made the biggest difference for me is a single prompt I paste at the start of a chat that forces it to clarify first and cut the fluff.

It is not clever. It just changes the default behavior for the whole conversation. Steal it:

For the rest of this conversation, follow this process for every request I give you:

1. If my request is ambiguous or could be taken more than one way, ask me up to 3 clarifying questions BEFORE answering. Do not answer until I reply.
2. If it is already clear, restate what I am asking in one line, then answer.
3. In every answer, prefer specific and concrete over general. Cut hedging, filler, and throat-clearing intros.
4. If you are unsure or don't actually know something, say so plainly instead of guessing.
5. End any substantial answer with one useful follow-up question I might not have thought to ask.

Acknowledge that you understand, then wait for my first request.

Why it works: the clarifying-questions step alone kills most bad outputs, because half the time the model was about to solve the wrong problem. The "say so instead of guessing" line cuts confident nonsense. And restating the request catches misunderstandings before you have read a wall of text.

Paste it once at the top of a chat and it holds for the whole conversation. I use it as my default opener for anything that is not trivial.

(I keep it saved and drop it in with a // shortcut in the ChatGPT box so I am not hunting for it every time. Happy to share which extension in the comments if anyone asks. It works fine pasted by hand.)

The mistake most people make editing with AI (and editing in general) is doing everything in one pass - fixing commas while the structure is still broken, polishing a paragraph that should be cut. Real editing is layered: big picture first, then prose, then proofreading. Fix the foundation before the paint.

So I run revisions as a chain, one pass at a time, each building on the last. It keeps the AI from rewriting my voice into mush, because each step has a narrow job.

STEP 1 - Developmental pass (big picture only)

You are my developmental editor. Give me BIG-PICTURE feedback only - do not touch sentences, grammar, or word choice yet.

DRAFT:
{{paste}}

What this piece is trying to do: {{goal and audience}}

Cover:
- Structure: does it open in the right place? Is anything out of order? Does it drag or rush?
- Is the core point or story actually landing?
- What is missing, and what should be cut.

Give me the 3 highest-impact changes, most important first. No line edits.

STEP 2 - Revision plan

Turn that feedback into a concrete revision plan I can follow.

- Make each big-picture issue a specific action ("move X before Y", "cut the second section", "add a concrete example in paragraph 3").
- Order them so I fix structure before prose.
- Mark which are essential vs nice-to-have.

Just the plan - I will do the rewriting myself.

STEP 3 - Line edit (after the structure is fixed)

Now that the structure is sorted, do a line edit on this revised draft. Keep my voice - do not flatten it into generic clean prose.

REVISED DRAFT:
{{paste your revised version}}

- Tighten weak or wordy sentences.
- Cut filler and clichés.
- FLAG style choices instead of auto-fixing them, so I keep the ones I meant.

Show the edited version, then the 3 most important changes and why.

The reason this beats one big "edit this for me" prompt: if you let it fix everything at once, it smooths your prose before you have decided whether the structure even works, and you end up polishing sentences you later cut. Doing the developmental pass first means you only line-edit what survives - and your voice makes it through intact.

(I run this as a saved chain so the passes fire in order when I type .., in a browser extension, instead of pasting three prompts. Happy to share which one in the comments if anyone wants. It works fine by hand, one pass at a time.)

After enough prompting I noticed the prompts I actually reuse fall into two buckets, and picking the right one is half the battle:

1. Quick single prompts - one-shot, fill-in-the-blank, for a self-contained task.
2. Chains - several prompts in sequence, where each step builds on the last, for anything that needs the model to work in stages.

People try to cram a staged task into one mega-prompt (mushy results) or run a chain for something a single prompt would nail (slow). Here are examples of each so you can feel the difference. Copy them, swap the {{variables}}.

Quick single prompts (one and done)

The Tightener

Tighten this {{text type, e.g. email / paragraph / bio}} to under {{word count}} words without losing the meaning.

- Cut filler and repetition.
- Keep my voice - do not make it generic.
- Give me the tightened version, then one line on what you cut.

TEXT:
{{paste it}}

The Gut-Check

Here is something I am about to send or do: {{describe or paste it}}.

Give me a fast gut-check, not an essay:
- The one thing most likely to go wrong or be misread.
- The single change that would improve it most.
- Your call: send/do it as-is, or fix that first?

Keep it to a few lines.

A chain (when one prompt is not enough)

This is the one I use to make almost anything better. Run the three in order, pasting each result into the next.

STEP 1 - Draft

Write a first draft of: {{what you need - email, post, plan, etc.}}.
Constraints: {{tone, length, audience}}.

Just get a complete draft down. Do not polish or second-guess yet - I want raw material to work with.

STEP 2 - Critique

Switch roles. You are now a tough reviewer seeing the draft above for the first time.

- Name the 3 weakest things, most important first.
- Flag anything generic, unclear, or unsupported.
- Say what is missing.

Do not rewrite it. Critique only - be blunt.

STEP 3 - Finalize

Now rewrite the draft, fixing every point from the critique.

- Keep what was already working.
- Address each weakness specifically.
- Give me the final version only, polished.

The rule of thumb: if the task is self-contained, a single prompt is faster. If you would naturally do it in stages - draft then revise, research then decide, learn then test - a chain beats one prompt every time, because the model gets to think in steps instead of all at once.

(I keep the single ones on a // shortcut and the multi-step ones as a saved .. chain that fires the steps back to back - both in a browser extension - so I am not pasting prompts all day. Happy to share which one in the comments if anyone asks. Everything above works fine by hand.)

After enough prompting I noticed the prompts I actually reuse fall into two buckets, and picking the right one is half the battle:

1. Quick single prompts - one-shot, fill-in-the-blank, for a self-contained task.
2. Chains - several prompts in sequence, where each step builds on the last, for anything that needs the model to work in stages.

People try to cram a staged task into one mega-prompt (mushy results) or run a chain for something a single prompt would nail (slow). Here are examples of each so you can feel the difference. Copy them, swap the {{variables}}.

Quick single prompts (one and done)

The Tightener

Tighten this {{text type, e.g. email / paragraph / bio}} to under {{word count}} words without losing the meaning.

- Cut filler and repetition.
- Keep my voice - do not make it generic.
- Give me the tightened version, then one line on what you cut.

TEXT:
{{paste it}}

The Gut-Check

Here is something I am about to send or do: {{describe or paste it}}.

Give me a fast gut-check, not an essay:
- The one thing most likely to go wrong or be misread.
- The single change that would improve it most.
- Your call: send/do it as-is, or fix that first?

Keep it to a few lines.

A chain (when one prompt is not enough)

This is the one I use to make almost anything better. Run the three in order, pasting each result into the next.

STEP 1 - Draft

Write a first draft of: {{what you need - email, post, plan, etc.}}.
Constraints: {{tone, length, audience}}.

Just get a complete draft down. Do not polish or second-guess yet - I want raw material to work with.

STEP 2 - Critique

Switch roles. You are now a tough reviewer seeing the draft above for the first time.

- Name the 3 weakest things, most important first.
- Flag anything generic, unclear, or unsupported.
- Say what is missing.

Do not rewrite it. Critique only - be blunt.

STEP 3 - Finalize

Now rewrite the draft, fixing every point from the critique.

- Keep what was already working.
- Address each weakness specifically.
- Give me the final version only, polished.

The rule of thumb: if the task is self-contained, a single prompt is faster. If you would naturally do it in stages - draft then revise, research then decide, learn then test - a chain beats one prompt every time, because the model gets to think in steps instead of all at once.

(I keep the single ones on a // shortcut and the multi-step ones as a saved .. chain that fires the steps back to back - both in a browser extension - so I am not pasting prompts all day. Happy to share which one in the comments if anyone asks. Everything above works fine by hand.)

The version of AI writing I cannot stand is the one where you ask it to write the thing and paste the result. But used as support roles - outliner, beta reader, line editor, the friend who unsticks you - it has genuinely made me write more and write better, without taking over my voice.

These are the 5 I reuse. None of them write the piece for you. Copy them, swap the {{variables}}, and use them on your own work.

1. The Outliner - structure before you draft, without losing the idea

I have a messy idea for a {{piece, e.g. short story / essay / chapter}} and I need an outline before I draft.

THE IDEA: {{dump it, however rough}}

Give me:
- The through-line in one sentence - what this is really about.
- A structured outline of the key beats or sections, in order.
- One line on the purpose of each beat.
- The single part of my idea that is underdeveloped and needs more thought before I write.

Do not write the piece. Outline only.

2. The Beta Reader - an honest reader reaction, not an edit

Read the following as a thoughtful beta reader, not an editor. I want a reader's honest reaction.

DRAFT:
{{paste}}

Tell me:
- Where you were hooked and where your attention drifted - point to specific lines.
- Anything that confused you or pulled you out of it.
- What you think the piece is actually about, so I can see if it landed.
- The one change that would most improve the experience of reading it.

React honestly. Do not rewrite it.

3. The Line Editor - tighten the prose without flattening your voice

Do a line edit on this passage. Keep my voice - do not turn it into generic clean prose.

PASSAGE:
{{paste}}

- Tighten wordy or weak sentences.
- Cut filler and redundancy.
- FLAG, do not auto-fix, anything that is a style choice I might want to keep.

Show the edited version, then a short list of the most important changes and why.

4. The Continuity Checker - catches what you are too close to see

Check this {{story / chapter / draft}} for continuity problems and inconsistencies.

TEXT:
{{paste}}
Things you should know (names, established facts, timeline): {{optional notes}}

Find:
- Contradictions in facts, names, timeline, or character details.
- Things set up but never paid off, or referenced but never set up.
- Anything a sharp reader would catch.

List them with the specific lines. Flag only - do not fix them.

5. The Unsticker - for when a scene or section will not move

I am stuck on this part: {{describe the scene or section}}.

Where I am: {{what just happened}}
Where I need to get to: {{what has to happen next, if you know}}
Why I think I am stuck: {{your guess, or "not sure"}}

Give me:
- 3 different ways this could move forward, each a different tone or direction.
- For each, the first sentence or two to get me going.
- One question about my characters or story that might reveal the real path.

Do not write the whole scene. Just get me moving.

The throughline is that the model does the support work - structure, reactions, catching mistakes, options when you are stuck - and you do the actual writing. The Beta Reader and Continuity Checker especially do things that are genuinely hard to do for your own work, because you cannot un-know what you meant.

(I keep these saved and pull them up by typing // in the chat box so they are one keystroke away on whatever I am working on. Happy to share the setup in the comments if anyone wants it. They all work fine pasted by hand.)

"Teach me {{topic}}" gives you a wall of text you nod along to and forget by tomorrow. Real learning is staged: figure out your level, get taught at it, get tested, fix what you missed, then compress it into something you keep. One prompt cannot do that. A chain can.

So I run it as 5 prompts back to back, each feeding the next. Paste them in order, answering as you go.

STEP 1 - Calibrate

I want to learn {{topic}}. Before teaching me anything, calibrate to me.

Ask me:
1. What I already know about it, so you can skip that.
2. Why I want to learn it and how I will use it.
3. How deep I need to go - rough overview, or a working understanding.

Ask these as a short numbered list and then wait. Do not start teaching yet.

STEP 2 - Teach at my level

Based on my answers, teach me {{topic}} at exactly the level I need - no more, no less.

Rules:
- Build on what I already said I know. Do not re-explain that.
- One concept at a time, in a logical order, each with a concrete example.
- Define every new term the first time you use it.
- Stop after the core concepts that get me to my stated goal. Do not dump the whole field.

Teach it now.

STEP 3 - Test me

Now test whether it actually stuck. Do NOT re-explain anything first.

Ask me 6 questions about what you just taught, ONE at a time, waiting for my answer each time:
- Mix straight recall, "explain why," and one applied scenario.
- After each answer, tell me right or wrong with a one-line correction.

At the end, list the specific concepts I clearly have not grasped.

STEP 4 - Fix the gaps

Re-teach ONLY the concepts I got wrong or was shaky on. Ignore everything I already understood.

For each one:
- Explain it a different way than you did the first time - a new angle or analogy.
- Give me one fresh example.
- Ask me a single follow-up question to confirm I have it now.

STEP 5 - Compress into a keeper

Now compress everything into a one-page reference I can save and review later.

Include:
- The core concepts as short, plain-language bullets.
- The key examples, briefly.
- The mistakes I made during the test, written as "remember: ..." reminders.
- 3 questions I can use to re-test myself in a week.

Keep it tight enough to fit on one screen.

The difference between Step 2 alone and the full chain is the difference between feeling like you learned something and actually being able to use it next week. Steps 3 and 4 are the uncomfortable part, which is exactly why they are the part that works.

(I run this as a saved chain that fires the steps back to back when I type .., so I am not pasting five prompts every time. Happy to share how in the comments if anyone wants. It works fine by hand, one step at a time.)

After enough prompting I noticed weak prompts mostly fail for the same handful of reasons: no role or quality bar, no examples to anchor the format, no self-check, sloppy output structure, or no decomposition on a multi-part task. So instead of task-specific prompts, I keep 5 scaffolds that encode those patterns, each with {{variables}} I fill in. They work on almost anything.

Copy them, swap the {{variables}}, and reuse.

1. Role + Rubric - forces consistent quality instead of vibes

You are {{specific expert role, e.g. a senior copy editor with 15 years in B2B SaaS}}.

TASK: {{what you want done}}

Hold the output to this rubric. It must:
- {{criterion 1}}
- {{criterion 2}}
- {{criterion 3}}

Produce the output, then rate it against the rubric in one line and fix anything that falls short BEFORE showing me the final version.

2. Few-Shot Lock - when you need the format/style to match exactly

I want output that matches a specific pattern. Infer it from these examples, then apply it to my new input.

EXAMPLES:
Input: {{example input 1}} -> Output: {{example output 1}}
Input: {{example input 2}} -> Output: {{example output 2}}

Match the structure, length, and tone of the example outputs exactly. Do not explain your reasoning.

NEW INPUT: {{your input}}

3. Self-Critique Loop - stops it from handing you a lazy first draft

TASK: {{your task}}

Do this in three passes and show each:
1. DRAFT: a first attempt.
2. CRITIQUE: act as a harsh reviewer and name the 3 biggest weaknesses of the draft against the goal of {{what good looks like}}.
3. FINAL: rewrite the draft fixing every point from the critique.

Only the FINAL has to be polished. The point is that you do not get to skip the critique.

4. Strict Output Schema - kills preamble and gives you parseable results

{{your task or question}}

Return ONLY this structure, nothing before or after:

- Summary: <one sentence>
- Options: <bulleted list>
- Recommendation: <one option + why>
- Confidence: <low / medium / high>

Rules: no preamble, no "here is", no closing remarks. If a field has no content, write "none". Respect the length I specified for each field.

5. Decompose-First - for multi-part problems where it jumps to a shallow answer

This is a multi-part problem and I want you to think before answering: {{the problem}}

Step 1: restate the problem and list the sub-questions that must be answered to solve it.
Step 2: answer each sub-question briefly.
Step 3: only then give the final answer, assembled from those parts.

Do not skip to step 3. If a sub-question depends on information I did not provide, ask me instead of guessing.

The reason these beat task-specific prompts is that they are composable: Role + Rubric wraps almost anything, Decompose-First and Self-Critique can stack on top, and Strict Output Schema makes the result usable downstream. Once you think in patterns instead of one-off prompts, you stop rewriting and start assembling.

(I keep these saved so each is one shortcut away in the message box instead of buried in a doc - which is the only reason I actually reuse them. Happy to share how I do that in the comments if anyone wants.)

People keep asking for more of these, so here is the next batch. Same idea as before: take the tasks you do over and over, write the prompt once, over-specify it, and turn the parts that change into {{variables}} so you fill in blanks instead of starting from scratch.

This set is less about producing content and more about the stuff that actually eats your week - deciding between options, writing replies, and not getting caught off guard. Copy them, swap the {{variables}}, reuse.

1. The Comparison - for deciding between options without going in circles

Help me compare my options so I can actually decide.

OPTIONS: {{list them, e.g. tool A vs tool B vs tool C}}
What matters most to me: {{your criteria, e.g. price, setup time, learning curve}}

Do this:
- Build a table: options as rows, my criteria as columns, a short honest rating in each cell.
- Call out the single biggest tradeoff between the top 2.
- Recommend one for my situation, and say who should pick a different one instead.

No "it depends." Commit to a recommendation.

2. The Reply - for messages you keep putting off answering

Help me reply to this message.

MESSAGE I RECEIVED:
{{paste it}}

What I want to get across: {{your goal or the gist of your response}}
Tone: {{e.g. warm but firm / professional / casual}}

Give me 2 versions: one short, one more complete.
Keep it natural, no corporate filler, and do not over-apologize or over-explain.

3. The SOP - for turning "the way you do it" into something others can follow

Turn this process into a clear step-by-step SOP that someone else could follow without asking me questions.

THE PROCESS: {{describe how you do it, even messily}}

Format it as:
- Goal (one line: what "done" looks like)
- Numbered steps, each starting with an action verb
- For any step that is easy to get wrong, a short "watch out" note
- What to do if something goes wrong

Flag anything I described that is ambiguous and needs a decision from me.

4. The Briefing - for getting up to speed on something fast

Get me up to speed on {{topic}} fast. Assume I am smart but know nothing about this.

Give me:
- What it is, in 2-3 plain sentences.
- Why it matters and why people care.
- The 5 things I actually need to know to hold a conversation about it.
- The most common misconception.
- 3 good questions to ask if I want to go deeper.

Skip the history lecture. Prioritize what is useful now.

5. The Objection Handler - for any time you have to convince someone

I am about to propose this: {{your idea / pitch / request}}.
Audience: {{who you are proposing it to and what they care about}}.

Help me prepare:
1. The top 5 objections or pushbacks they are most likely to raise.
2. For each, the strongest honest version of their concern (steelman it).
3. A concise, straight response to each - no spin.
4. The one objection I probably cannot answer well, so I can prepare for it in advance.

The real unlock is still the habit, not any single prompt: the moment something works well, stop and turn the parts that change into {{variables}} before you move on. Do it for a few weeks and you stop facing a blank box and start filling in blanks instead.

(I keep all of mine in a browser extension and pull any of them up by typing // in the ChatGPT box - it then asks me to fill in the variables, so I never dig through a doc. Happy to share which one in the comments if anyone asks. The templates above work fine pasted by hand.)

Once you have more than a few dozen Claude conversations, your history is basically a black hole. You can scroll, and the built-in search mostly matches chat titles - so if you remember something Claude explained inside a chat three weeks ago but not what you happened to name it, good luck ever finding it again.

So I added a search tab to my Chrome extension (AI Toolbox) that actually searches inside your conversations, not just their titles:

• Full-text search across every chat - titles AND message content
• Filter by who said it (your messages vs Claude's) and by date (past week / month / year)
• Each result shows a match-count badge and highlights the matching text, so you can see exactly why it came up
• Click any result to jump straight into that conversation
• It is near-instant because it searches a local copy of your chats, not by hammering an API on every keystroke

AI Toolbox Search History Feature

The extension's Claude features are free. All data stays local - your conversations are cached in your own browser (IndexedDB) and searched right there. Nothing is sent through any backend of mine.

We have all done it: dump a page of notes into ChatGPT, ask for flashcards, and get back 20 bloated cards with paragraph-long answers that are useless to actually review. The model does not know the minimum information principle unless you make it.

These 5 prompts fix that. They force atomic, recall-friendly cards instead of walls of text, and a couple of them clean up the bad cards you already have. Copy them, paste your material, and you get cards worth putting in a deck.

(Worth saying: always sanity-check AI-made cards for accuracy before you drill them in. A wrong card you review 200 times is worse than no card.)

1. Notes to Atomic Cards - the one that fixes bloated decks

Turn these notes into Anki flashcards following good card principles: one fact per card, atomic, short answers.

NOTES:
{{paste your notes}}

Rules:
- Each card tests ONE thing. Split anything compound into multiple cards.
- Phrase the front as a specific question, not a topic or "what about X."
- Keep answers short - a few words where possible, never a paragraph.
- No yes/no questions.

Output as a clean list of Front / Back pairs I can paste straight in.

2. Cloze Generator - for definitions, lists, and sequences

Turn the following text into Anki cloze deletion cards.

TEXT:
{{paste}}

Rules:
- Delete only the key term or number, not whole phrases.
- One deletion per card unless two facts are truly inseparable.
- Leave enough of the sentence intact that I can actually recall the answer from context.

Output each card in Anki cloze format, using the sentence with {{c1::the deleted part}}.

3. The Card Doctor - fix cards you keep failing for the wrong reasons

These Anki cards are not working - too long, not atomic, or I fail them because they are ambiguous, not because I do not know the material.

CARDS:
{{paste your cards}}

For each:
1. Tell me exactly what is wrong with it.
2. Rewrite it as one or more better cards following the minimum information principle.

4. Recognition to Recall - when you "know it" on the card but blank in real life

I have cards for {{concept}} but I only recognize the answer, I cannot truly recall or use it.

Make me harder cards that force real understanding:
- 2 that require recalling it cold, with no hints in the question.
- 2 that apply it to a new example or situation.
- 1 that asks me to explain WHY, not just state what.

Output as Front / Back pairs.

5. Explain, Then Build - for a new topic you are starting from scratch

Teach me {{concept}}, then build my flashcards from it.

1. Explain it clearly and simply, with one concrete example.
2. Pick the 5-8 facts most worth remembering long term.
3. Turn each into an atomic Anki card (Front / Back) following good card principles.

Do the explanation first, then the cards.

The shift that helped me most was treating ChatGPT as a card-drafting assistant, not a card factory. The Card Doctor in particular saved a deck I was about to give up on - half my "hard" cards were just badly written, not actually hard.

(I keep these saved in a browser extension and trigger them with // in the ChatGPT box so I am not re-pasting the same instructions for every lecture. Happy to share which one in the comments if anyone wants it. They all work fine pasted by hand.)

Every time I share my screen or mention how I use ChatGPT, someone stops me and says "wait, you can't do that." Turns out a lot of people have no idea most of this is possible. So here is everything I do daily that apparently is not "supposed" to exist:

• My chats are in folders. Actual folders and subfolders in the sidebar - Work, Clients, Personal, each with sub-projects. No more scrolling a thousand untitled chats.
• I can search across all my conversations. Full-text. I type a word and it finds the exact chat from four months ago where I worked something out. ChatGPT's own search never did this for me.
• My most-used prompts are on a shortcut. I type // in the message box and a menu of my saved prompts pops up. Pick one, fill in the blanks, send. I have not rewritten a go-to prompt from scratch in months.
• I chain prompts. I type .. and run a saved sequence of prompts back to back, each building on the last, without babysitting it step by step.
• I pin the chats I actually return to, so my five active projects sit at the top instead of getting buried under one-off questions.
• I export anything to Markdown or PDF. Single chats or my whole history at once, as clean files. That is how my best ChatGPT work ended up in my notes app instead of trapped in an account.

None of this is a different version of ChatGPT or some API setup. It is the same ChatGPT everyone uses, plus one thing running on top of it.

I am deliberately not naming it in the post because every time I do, it gets flagged as an ad and removed, which is fair. But if you want to know what it is, just say so in the comments and I will tell you - no affiliation, I just use it daily.

Which of these did you not know was possible? That is usually the part people get stuck on.

I love ChatGPT Projects, but I kept hitting the same wall: they're flat. You get one level. That's fine for a dozen chats. It falls apart the moment you have a real workload.

My setup was a mess. A "Marketing" project. A "Client work" project. A "Personal" project. But inside "Client work" I have five clients, and inside each client I have research chats, draft chats, and a dedicated Project. There's no way to express that in a flat list. So everything just piled up and I'd lose threads constantly.

What actually fixed it for me was switching to real nested folders. The thing that makes it click is what you're allowed to put inside a folder:

• Chats - the obvious one
• GPTs - keep the custom GPTs for a workflow next to the chats that use them
• ChatGPT Projects - yes, you can drop an entire Project inside a folder

So now my tree looks like:

Client work
  └─ Acme Corp
       ├─ Research (a subfolder)
       ├─ Q3 Campaign (a ChatGPT Project)
       └─ Brand-voice GPT
  └─ Globex
       └─ ...
Personal
Marketing

AI Toolbox Folders Feature

Unlimited depth, so I can go as deep as the work actually is instead of flattening it into one layer.

A few things that turned out to matter more than I expected:

• Breadcrumbs so you always know where you are (Folders / Client work / Acme / Research)
• Color-coded folders and little count pills ("5 chats, 1 project, 2 subfolders") so you can scan a folder at a glance
• Pin your most-used folders to the top of the sidebar for one-click access
• Export a whole folder hierarchy as a ZIP when you need to hand off or back up a client's stuff

Full disclosure: this is from a browser extension I work on (AI Toolbox). I'm not going to pretend otherwise. But the nesting-with-Projects-inside is genuinely the part that changed how I use ChatGPT day to day, so I figured the org nerds here might appreciate it.

Let me get the obvious objection out of the way: AI copy mostly sounds like AI copy, and "write me a sales page" gives you garbage. I am not arguing with that.

But ChatGPT is genuinely useful for the work around the writing - generating angles to react to, matching a voice, repurposing, and mining customer language. None of that replaces the writing. It just removes the blank-page grind so the actual craft is faster.

These are the 5 I reuse. Notice none of them are "write the copy for me."

**1. The Hook Generator** \- angles to react to, so you are not staring at a blank doc

I need scroll-stopping hooks for {{the offer / topic / piece}}.

Audience: {{who they are and what they actually want}}.
Overused angle to avoid: {{the obvious one, if any}}.

Give me 10 hooks across different angles - curiosity, contrarian, problem-agitation, result-driven, story-open, and so on. Label each with its angle.
One line each, no explanations. Then mark the 2 strongest and say why in a few words.

**2. The Voice Match** \- rewrite to a brand voice without flattening it

Rewrite the following copy to match a specific brand voice. Do not change the meaning or the offer.

BRAND VOICE: {{describe it - e.g. dry and confident, warm and casual, short punchy sentences, no hype}}.
SAMPLE OF THE VOICE (optional): {{paste a line or two if you have them}}.

COPY TO REWRITE:
{{paste}}

Give me 2 versions. After each, note in one line what you changed to hit the voice.

**3. The Repurposer** \- one piece into a week of native posts

Turn this one piece of content into a set of posts.

SOURCE: {{paste the article / email / transcript}}
Platforms: {{e.g. LinkedIn, X, Instagram caption}}
How many per platform: {{number}}

For each platform:
- Match its native format and length.
- Pull a different angle each time so they are not the same post reworded.
- Keep my core message, invent no new claims or stats.

**4. The De-AI Pass** \- punch up flat copy and strip the tells

Make this copy sharper and more human. It currently reads flat or AI-generated.

COPY:
{{paste}}

- Cut hedging, filler, and throat-clearing intros.
- Replace vague claims with concrete, specific language.
- Vary sentence length so it has rhythm.
- Kill the obvious AI tells: "in today's fast-paced world," "unlock," "elevate," "dive in," "game-changer," "it's not just X, it's Y."

Give me the rewrite, then list the 3 biggest changes you made and why.

**5. Voice-of-Customer Mining** \- the one that actually improves conversions

Here is raw customer language - reviews, support tickets, survey replies, or comments:

{{paste it}}

Mine it for copy I can use:
1. The exact phrases customers use to describe their problem, verbatim.
2. The words they use for the outcome they want.
3. The top 3 objections or hesitations that show up.
4. 3 headline angles built from their own words, not marketing speak.

The pattern across all of these: the model does the grunt work and the research, you do the judgment and the actual writing. Voice-of-Customer Mining alone has earned its keep more than any "write my ad" prompt ever could.

(I keep these saved in a browser extension and pull them up by typing `//` in the ChatGPT box, so they are one keystroke away on every project instead of living in a doc. Happy to share which one in the comments if anyone asks. They all work fine pasted by hand.)

Let me get the obvious objection out of the way: AI copy mostly sounds like AI copy, and "write me a sales page" gives you garbage. I am not arguing with that.

But ChatGPT is genuinely useful for the work around the writing - generating angles to react to, matching a voice, repurposing, and mining customer language. None of that replaces the writing. It just removes the blank-page grind so the actual craft is faster.

These are the 5 I reuse. Notice none of them are "write the copy for me."

1. The Hook Generator - angles to react to, so you are not staring at a blank doc

I need scroll-stopping hooks for {{the offer / topic / piece}}.

Audience: {{who they are and what they actually want}}.
Overused angle to avoid: {{the obvious one, if any}}.

Give me 10 hooks across different angles - curiosity, contrarian, problem-agitation, result-driven, story-open, and so on. Label each with its angle.
One line each, no explanations. Then mark the 2 strongest and say why in a few words.

2. The Voice Match - rewrite to a brand voice without flattening it

Rewrite the following copy to match a specific brand voice. Do not change the meaning or the offer.

BRAND VOICE: {{describe it - e.g. dry and confident, warm and casual, short punchy sentences, no hype}}.
SAMPLE OF THE VOICE (optional): {{paste a line or two if you have them}}.

COPY TO REWRITE:
{{paste}}

Give me 2 versions. After each, note in one line what you changed to hit the voice.

3. The Repurposer - one piece into a week of native posts

Turn this one piece of content into a set of posts.

SOURCE: {{paste the article / email / transcript}}
Platforms: {{e.g. LinkedIn, X, Instagram caption}}
How many per platform: {{number}}

For each platform:
- Match its native format and length.
- Pull a different angle each time so they are not the same post reworded.
- Keep my core message, invent no new claims or stats.

4. The De-AI Pass - punch up flat copy and strip the tells

Make this copy sharper and more human. It currently reads flat or AI-generated.

COPY:
{{paste}}

- Cut hedging, filler, and throat-clearing intros.
- Replace vague claims with concrete, specific language.
- Vary sentence length so it has rhythm.
- Kill the obvious AI tells: "in today's fast-paced world," "unlock," "elevate," "dive in," "game-changer," "it's not just X, it's Y."

Give me the rewrite, then list the 3 biggest changes you made and why.

5. Voice-of-Customer Mining - the one that actually improves conversions

Here is raw customer language - reviews, support tickets, survey replies, or comments:

{{paste it}}

Mine it for copy I can use:
1. The exact phrases customers use to describe their problem, verbatim.
2. The words they use for the outcome they want.
3. The top 3 objections or hesitations that show up.
4. 3 headline angles built from their own words, not marketing speak.

The pattern across all of these: the model does the grunt work and the research, you do the judgment and the actual writing. Voice-of-Customer Mining alone has earned its keep more than any "write my ad" prompt ever could.

(I keep these saved in a browser extension and pull them up by typing // in the ChatGPT box, so they are one keystroke away on every project instead of living in a doc. Happy to share which one in the comments if anyone asks. They all work fine pasted by hand.)

Most people use ChatGPT to summarize notes or spit out answers. It feels productive, but it does almost nothing for memory - you read a tidy summary, nod, and forget it by next week.

What actually moved my grades was using it for the boring, proven stuff: active recall, self-testing, and the Feynman technique. The catch is those methods are a pain to do alone. These 5 prompts make ChatGPT run them on you. Copy them, fill in the blanks, and use them on whatever you are studying.

1. The Tutor - learns you up one step at a time instead of dumping everything

Be my tutor for {{topic}}. Assume I am starting from {{level, e.g. complete beginner / know the basics}}.

Teach it in small steps:
- Explain ONE concept at a time, then stop.
- After each concept, ask me a quick question to check I got it before moving on.
- If I answer wrong, explain it a different way - do not just repeat the same words.
- Use a concrete example for anything abstract.

Start with the first concept and your first check question. Wait for my answer before continuing.

2. Quiz Me - active recall, which is the part that actually builds memory

Quiz me on {{topic or material}} to help me remember it, not just recognize it.

Rules:
- One question at a time, wait for my answer.
- Mix formats: straight recall, "explain why," and applied problems.
- Difficulty: {{easy / medium / hard / mixed}}.
- After each answer: tell me right or wrong, give the correct answer, and one line on why.
- Keep score, and after 10 questions tell me my weakest area.

Start with question 1.

3. The Feynman Check - exposes what you only think you understand

I am going to explain {{concept}} in my own words, as if teaching it. Your job is to find the gaps.

MY EXPLANATION:
{{write it out}}

Then:
1. Point out anything I got wrong or fuzzy.
2. Identify what I left out that actually matters.
3. Ask me the one question that would reveal whether I truly understand it.

Do not praise it. The point is to find what I do not actually know.

4. Exam Predictor - focuses your limited time on what is likely to be tested

I have an exam on {{subject}} covering {{scope, e.g. chapters 3-6 / these topics}}.

Help me prepare:
1. Predict the 10 questions most likely to appear, in realistic exam style.
2. For each, give a short model answer or solution outline.
3. Tell me the 3 highest-yield topics to focus on if I am short on time.

Be realistic about how this material is usually tested, not random trivia.

5. The Simplifier - for the concept that just will not click

Explain {{hard concept}} using an analogy from {{something I already get, e.g. cooking / football / video games}}.

Then:
- Give the plain technical explanation.
- Point out where the analogy breaks down, so I do not learn it wrong.
- End with one question to check I followed.

The trick is to stop reading and start getting tested. Summaries feel good and do little. Quiz Me and the Feynman Check feel uncomfortable, which is exactly why they work. I run the Tutor when learning something new, then Quiz Me and the Feynman Check before exams.

(I keep these saved in a browser extension and trigger them by typing // in the ChatGPT box, so I am not pasting the same prompt for every chapter. Happy to share which one in the comments if anyone wants it. They all work fine pasted by hand.)

A while back I posted about turning your best prompts into fill-in-the-blank templates with `{{variables}}` so you stop rewriting them. A bunch of people asked for the ones I actually use, so here is the next batch.

These are the 5 I reach for most. They are not clever party-trick prompts. They are the boring, high-frequency tasks I do every week, written once and over-specified on purpose, because the detail is what makes the output good. Copy them, swap the `{{variables}}` for your specifics, and reuse.

**1. The Summarizer** \- for getting the point of something fast without missing what matters

Summarize the following {{content type, e.g. article / transcript / long thread}} for someone who has about {{how much time, e.g. 30 seconds}}.

Give me, in this exact order:
- TL;DR in one sentence.
- The 3-5 key points as bullets, most important first.
- Any decisions or action items, only if there are any.
- The one thing most people skimming this would miss.

Do not pad it. If something is not important, leave it out entirely.

CONTENT:
{{paste it}}

**2. The Brainstormer** \- for ideas that are not just the first 5 obvious ones

Give me {{number, e.g. 15}} ideas for {{goal or problem}}.

Constraints that rule ideas in or out: {{budget / time / tools / audience}}.

Rules:
- Mix safe and obvious ideas with at least 3 genuinely unconventional ones.
- One line each, no explanation yet.

After the list, pick the 3 you think are strongest and give me one sentence on why each could work.

**3. The Planner** \- for turning a vague goal into something you can actually start

I want to {{goal}} by {{deadline}}.

Where I am now: {{starting point}}.
My constraints: {{time per week / budget / current skill level}}.

Build me a realistic step-by-step plan:
- Break it into clear milestones with rough timing.
- For each milestone, give me the first concrete action to take.
- Flag the single step most likely to stall me, and how to get past it.

Make it fit my actual constraints, not an idealized version with unlimited time.

**4. The Organizer** \- for turning a mess of notes into something usable

Turn these messy notes into a clean, structured {{output, e.g. meeting summary / project brief}}.

Organize into:
- Summary (2-3 sentences)
- Key decisions
- Action items (include owner and deadline if mentioned)
- Open questions

Do not invent anything that is not in my notes. If an owner or date is missing, write "unassigned" instead of guessing.

NOTES:
{{paste them}}

**5. The Pre-Mortem** \- for catching how a plan will fail before it does

Here is a {{plan / idea / decision}}: {{describe it}}.

Run a pre-mortem. Assume it is now {{timeframe, e.g. 6 months}} later and this failed badly.

1. Tell the story of how it most likely failed.
2. List the top 3 causes, ranked by likelihood times damage.
3. For each cause, give me one concrete thing I can do right now to prevent it.

Be specific to my situation. No generic "communicate clearly" advice.

The real unlock is still the habit, not any single prompt: the moment you write something that works well, stop and turn the parts that change into `{{variables}}` before you move on. Do that for a few weeks and you stop starting from a blank box and start filling in blanks instead.

(I keep all of mine in a browser extension and pull any of them up by typing `//` in the ChatGPT box - it then asks me to fill in the variables, so I never dig through a doc. Happy to share which one in the comments if anyone asks. The templates above work fine pasted by hand.)

A while back I posted about turning your best prompts into fill-in-the-blank templates with {{variables}} so you stop rewriting them. A bunch of people asked for the ones I actually use, so here is the next batch.

These are the 5 I reach for most. They are not clever party-trick prompts. They are the boring, high-frequency tasks I do every week, written once and over-specified on purpose, because the detail is what makes the output good. Copy them, swap the {{variables}} for your specifics, and reuse.

1. The Summarizer - for getting the point of something fast without missing what matters

Summarize the following {{content type, e.g. article / transcript / long thread}} for someone who has about {{how much time, e.g. 30 seconds}}.

Give me, in this exact order:
- TL;DR in one sentence.
- The 3-5 key points as bullets, most important first.
- Any decisions or action items, only if there are any.
- The one thing most people skimming this would miss.

Do not pad it. If something is not important, leave it out entirely.

CONTENT:
{{paste it}}

2. The Brainstormer - for ideas that are not just the first 5 obvious ones

Give me {{number, e.g. 15}} ideas for {{goal or problem}}.

Constraints that rule ideas in or out: {{budget / time / tools / audience}}.

Rules:
- Mix safe and obvious ideas with at least 3 genuinely unconventional ones.
- One line each, no explanation yet.

After the list, pick the 3 you think are strongest and give me one sentence on why each could work.

3. The Planner - for turning a vague goal into something you can actually start

I want to {{goal}} by {{deadline}}.

Where I am now: {{starting point}}.
My constraints: {{time per week / budget / current skill level}}.

Build me a realistic step-by-step plan:
- Break it into clear milestones with rough timing.
- For each milestone, give me the first concrete action to take.
- Flag the single step most likely to stall me, and how to get past it.

Make it fit my actual constraints, not an idealized version with unlimited time.

4. The Organizer - for turning a mess of notes into something usable

Turn these messy notes into a clean, structured {{output, e.g. meeting summary / project brief}}.

Organize into:
- Summary (2-3 sentences)
- Key decisions
- Action items (include owner and deadline if mentioned)
- Open questions

Do not invent anything that is not in my notes. If an owner or date is missing, write "unassigned" instead of guessing.

NOTES:
{{paste them}}

5. The Pre-Mortem - for catching how a plan will fail before it does

Here is a {{plan / idea / decision}}: {{describe it}}.

Run a pre-mortem. Assume it is now {{timeframe, e.g. 6 months}} later and this failed badly.

1. Tell the story of how it most likely failed.
2. List the top 3 causes, ranked by likelihood times damage.
3. For each cause, give me one concrete thing I can do right now to prevent it.

Be specific to my situation. No generic "communicate clearly" advice.

The real unlock is still the habit, not any single prompt: the moment you write something that works well, stop and turn the parts that change into {{variables}} before you move on. Do that for a few weeks and you stop starting from a blank box and start filling in blanks instead.

(I keep all of mine in a browser extension and pull any of them up by typing // in the ChatGPT box - it then asks me to fill in the variables, so I never dig through a doc. Happy to share which one in the comments if anyone asks. The templates above work fine pasted by hand.)

By now most of us have hundreds, maybe thousands, of ChatGPT conversations. And somewhere in there is genuinely useful stuff - a config you finally got working, a plan you thought through, an explanation that made something click. The problem is you will almost certainly never find any of it again.

Two things bother me about this:

1. It is effectively unsearchable. ChatGPT's own search is weak, titles are useless, and the chats just pile up until that knowledge is gone in practice even though it technically still exists.
2. It is not really yours. It lives in an account. One outage, one lockout, one "we've updated our terms" and your entire thinking history could be inaccessible.

What fixed both for me: I exported my whole ChatGPT history as individual Markdown files and dropped the folder into Obsidian. Now it is a real knowledge base - full-text search, backlinks, tags - sitting on my own disk.

https://preview.redd.it/6x8rkzg5p25h1.png?width=1118&format=png&auto=webp&s=03ae43983aa7710f4d261a5fa2df12b30b97f3ad

A few things that made it actually work:

• One file per conversation, as Markdown. Each chat became its own .md file with a small frontmatter block at the top (title, date, model, and a link back to the original chat). That means Obsidian, Logseq, and Notion ingest them natively instead of choking on one giant blob.
• Folder structure preserved. However I had things organized carried straight over into the vault, so I was not starting from chaos.
• Skip the native export for this. ChatGPT does have Settings → Data controls → Export, but it hands you one massive JSON plus an HTML file that is basically unusable as a knowledge base. You want per-conversation Markdown files, not a single dump.

The payoff is bigger than I expected. Something I worked out 8 months ago is now one search away, it is linkable to related notes, and it is backed up locally instead of trapped behind a login. It also quietly turned into a decent record of how my own thinking on certain projects evolved.

If you have ever thought "I know I figured this out in ChatGPT once," this is the fix.

(I did the bulk part with a browser extension - selected all my chats and exported a ZIP of Markdown files in one go, rather than saving them one at a time. Happy to share which one in the comments if anyone wants it. The idea works with any per-chat Markdown export though.)

Most people here collect great prompts and then never use them, because the prompt is buried in a note somewhere and rewriting it from memory is faster than going to find it. So you end up typing a worse, lazy version every time.

The fix that changed how I use ChatGPT: stop saving prompts as finished text, and start saving them as templates with fill-in-the-blank variables. Write the prompt once, mark the parts that change with {{double braces}}, and from then on you only fill in the blanks instead of rewriting the whole thing.

Here are 5 of the templates I reuse constantly. Copy them, swap the {{variables}} for your specifics, and go. They are deliberately over-specified, because the detail is what makes the output good.

1. The Explainer - for actually understanding something, not getting a Wikipedia paragraph

Explain {{concept}} to me as if I am a {{audience, e.g. smart 15-year-old / working engineer / total beginner}}.

Rules:
- Start with the one-sentence version, then go deeper.
- Use one concrete analogy from everyday life.
- Give a real example I would actually encounter.
- End with the single most common misconception about it and why it is wrong.
- No filler intro. Start with the explanation.

2. The Rewrite - for making any text sharper without losing your voice

Rewrite the following {{content type, e.g. email / paragraph / bio}} to be more {{quality, e.g. concise / persuasive / friendly / formal}}.

Keep my core meaning and my voice. Do not invent facts.
Give me 2 versions: one safe, one bolder.
After each, add a one-line note on what you changed and why.

TEXT:
{{paste your text}}

3. The Decision - for thinking clearly instead of going in circles

Help me think through this decision: {{the decision}}.

My options: {{option A vs option B}}.
What matters most to me: {{your top priorities}}.

Do this:
1. State the real tradeoff in one sentence.
2. Make the strongest case for each option.
3. Tell me what someone who is great at {{relevant skill/domain}} would likely choose and why.
4. Name the one piece of information that would most change the answer.
Do not just tell me "it depends."

4. The Critique - for honest feedback before you ship something

Act as a demanding {{expert role, e.g. senior editor / hiring manager / designer}} reviewing this {{thing}}.

Goal of the work: {{what it is supposed to achieve}}.
Audience: {{who it is for}}.

Give me:
- The 3 weakest things, most important first, with a specific fix for each.
- One thing that is genuinely working, so I do not break it.
- A score out of 10 and the single change that would raise it most.
Be blunt. I want it better, not validated.

WORK:
{{paste it}}

5. The Outreach - for messages you actually want a reply to

Write a {{type, e.g. cold email / DM / follow-up}} to {{recipient}} with the goal of {{goal}}.

Context they need: {{relevant background}}.
Tone: {{tone, e.g. warm but direct, no corporate fluff}}.
Length: under {{word count}} words.

Rules:
- Lead with something about them, not about me.
- One clear ask, not three.
- No "I hope this email finds you well."
Give me 2 subject lines too.

The real unlock is not any single template, it is the habit: every time you write a prompt that works well, pause and turn the changeable parts into {{variables}} before you move on. Within a few weeks you have a personal library you fill in instead of rewrite.

(I keep mine in a browser extension and pull any of them up by typing // in the ChatGPT box, then it asks me to fill in the variables - so I never go hunting through a doc. Happy to share which one in the comments if anyone asks. The templates above work fine pasted by hand.)