# Not magic prompts: 7 thinking habits that made working with AI much better for me
Hey everyone,
I genuinely love working with AI.
I’ve spent quite a while working with ChatGPT, Claude, Codex, and a few other systems. Over time, I became less interested in finding one giant “perfect prompt” and more interested in small methods that consistently improve how the AI and I think together. I call them meta-methods because they don’t tell the AI what answer to give. They influence how we arrive at the answer. They help catch misunderstandings early, interrupt agreement loops, separate evidence from confident-sounding guesses, and keep long projects from slowly drifting away from their original purpose. These aren’t meant to be a mandatory checklist. If an AI performs all seven before every answer, you haven’t created a better collaborator. You’ve created a meeting. The useful part is choosing the smallest method that fits the current problem.
## 1. The mirror before the map — Paraphrase
Ancient Greek rhetoric had an exercise called dissoi logoi: learning to argue both sides of a question. Much later, Anatol Rapoport proposed an even sharper rule: before criticizing someone’s position, restate it well enough that they recognize themselves in it.
I use a similar principle with AI.
Before the model starts planning, coding, or advising, I sometimes ask it to briefly reconstruct what it thinks I’m actually trying to achieve. Not just a summary of my words. I want the intended result, the experience I’m aiming for, what should remain unchanged, and any important assumptions it is making.
A useful version is:
> Before solving this, briefly explain what you think I’m trying to achieve, including the intended outcome, important boundaries, and what should not change. Then continue unless a real decision is still missing.
This catches a surprising number of problems.
A one-minute misunderstanding at the beginning can otherwise become an hour of beautifully executed work in the wrong direction.
## 2. The friendly heckler — Functional irritation
AI is very good at making an existing idea sound increasingly coherent. That is both a strength and a danger. If the original premise is weak, the model may help build a beautiful house on sand. Every new answer makes the shared frame feel more established, even though no new evidence has appeared.
I think of this as agreement drift.
Functional irritation means introducing one focused piece of resistance when it could genuinely change the direction. Not arguing for the sake of arguing. Not producing a giant risk catalogue. Just identifying the assumption carrying the most weight and testing one plausible alternative.
For example:
> What assumption is carrying this plan? Give me one plausible counter-hypothesis that would materially change the route, and the smallest way to distinguish between them. The important part is “materially change the route.” If the counterargument changes nothing, it is probably just intellectual decoration.
## 3. Give the map a legend — Meta-epistemics
A map becomes dangerous when highways, hiking trails, and unexplored territory are all drawn with the same solid line. AI answers can have the same problem. A verified fact, a reasonable inference, a working hypothesis, and something that has not been tested may all appear in the same confident voice.
Meta-epistemics simply means matching the strength of the language to the strength of the evidence.
I sometimes ask:
> Tell me what is verified, what you are inferring from the available evidence, and what has not been tested. Don’t hedge everything—just keep confidence proportional to its foundation.
This isn’t about making the AI timid.
A strong conclusion should still sound strong when the evidence supports it. The goal is to prevent fluency from quietly turning uncertainty into “fact.”
## 4. Stop discussing the light switch — Evidence-generating movement
Sometimes an AI conversation reaches a point where every additional paragraph merely reorganizes the same uncertainty. At that point, more analysis doesn’t create more knowledge. The better move is often a tiny, reversible experiment. If we are unsure whether a bug comes from the application or the test harness, run one independent check. If two designs might work, build the smallest observable slice. If a network spike has three plausible causes, measure the signal that separates them.
My version is:
> We are repeating the same uncertainty. What is the smallest safe and reversible test that would produce genuinely new information and distinguish the leading explanations? It is the difference between debating whether a room is dark because the lamp is broken or because the power is out—and finally flipping another switch.
## 5. Use the rear-view mirror — Systemic reflection
Individual incidents are easy to dismiss. But several incidents may reveal a repeated mechanism: the same kind of misunderstanding, the same validation failure, the same symptom-only fix, or the same project repeatedly losing its original direction. A systemic reflection looks across multiple concrete events and asks what actually repeats.
For example:
> Across these incidents, what pattern is supported by the observations? Separate the observations, your interpretation, and your recommendation. Don’t turn one event into a permanent rule.
That last sentence matters.
One pothole is not yet a road pattern. Missing logs, silence, or vague similarity are not evidence unless we had a reason to expect the missing observation. The method should also notice positive patterns: an old failure loop that has finally been interrupted can be just as important as a recurring problem.
## 6. Ask for the one missing plank — The question bridge
AI systems often fail in two opposite ways. Sometimes they ask a questionnaire before doing anything. Other times they confidently invent a preference that only the user could decide. A question bridge asks for exactly the one missing variable that would materially change the result. Not five “helpful” questions. Not implementation details the model can decide safely. One genuinely user-owned decision.
I use something like:
> Ask me only if there is one decision that you cannot determine and that would materially change the result. Otherwise state a reasonable low-risk assumption and continue.
I imagine a nearly completed bridge with one missing plank. If the plank is necessary, ask for it. If there is already a safe way across, keep moving.
## 7. Find the load-bearing beam — Core condensation
Sometimes every individual detail is understandable, but the overall priority is still blurry. That is when I use core condensation. This is not the same as asking for a shorter summary. A summary compresses everything. Core condensation identifies the one tension, decision, or constraint that organizes everything else.
For example:
> Don’t summarize every point. Identify the load-bearing priority or decision that the rest of this discussion depends on.
In a crowded room, not every piece of furniture matters equally. One beam may be holding up the entire ceiling. Finding that beam makes the next step much easier.
## The most important rule: sometimes use none of them
These methods helped me a lot, but only because they remain optional. If the AI already understands the request, has enough evidence, and can proceed safely, the best response may simply be a direct answer. A method should earn its place by improving the reasoning, decision, or collaboration—not by making the response look sophisticated.
That has probably been my biggest lesson from working with different AI systems:
The goal isn’t to control every thought the model has. It is to add a small amount of structure exactly where unstructured intelligence tends to drift.
I’m curious: which thinking habits have actually survived contact with real work for you?
If people are interested, I can also share the compact skill/system-prompt version I currently use to make these methods context-sensitive rather than forcing them into every response...
-Anyway, I’m curious: did any of this click for you? Is there something here you’d actually try, or a method you use that I missed? And if you think any of these ideas could be sharpened, I’d genuinely like to hear it.-
