The Recursion InstituteINDEPENDENT RESEARCH IN AI SAFETY

UNDERSTAND AI

How to use AI well

Most people type a question into an AI, read the first answer, and move on — then wonder why the results feel generic or a little off. The good news is that getting genuinely useful results isn’t a talent or a trick. It’s a small, repeatable method anyone can learn in an afternoon. This page is the craft side: how to actually get good work out of one of these tools. A companion page covers the protective side — using it safely — and the two fit together. Here we just want your results to be better.

It helps to start from what the tool actually is. An AI chat assistant is a system that predicts likely text, very fluently, based on what you give it. It has no goals of its own, and it works only from what’s in front of it — the conversation, plus whatever it has saved in memory if that’s on. That sounds like a limitation, and in a way it is — but it’s also exactly why the method below works. You’re not asking an oracle. You’re steering a fast, capable, slightly literal collaborator. The clearer you steer, the better it goes.

1. Frame it — don’t just ask

The single biggest improvement you can make: instead of a bare question, give the AI a frame. Tell it three things — the role it should take, the context it’s working in, and what a good result looks like to you. A bare question gets you a bare, average answer. A framed request gets you something shaped to your situation.

Compare “write me a cover letter” with: “You’re helping me apply for a junior nursing role. Here’s the job posting and my résumé. Write a warm, specific cover letter, under 300 words, that connects my clinic experience to what they’re asking for.” Same tool, completely different quality — because the second one told it the role, the context, and the target. You don’t need fancy wording. You just need to say out loud what’s already in your head.

2. Give it what it needs

The AI can only work with what it can see. It doesn’t know your project, your inbox, last week’s conversation, or what you meant but didn’t say. So feed it the actual material: paste in the real document, the real numbers, the example you like, the draft you’re unhappy with. If you want it to match a style, show it the style. If you want it to fix something, give it the whole thing, not a description of the thing.

A useful instinct: before you send a request, ask yourself, “Could a smart stranger do this with only what I’ve written here?” If the answer is no, you’re missing context — add it. Examples are especially powerful. One or two samples of what you want is often worth a paragraph of instructions.

3. Iterate — the first answer is a draft

This is where most people stop too early. Treat the first output as a starting point, not a verdict. It’s a thinking partner, not a vending machine where one coin buys one final answer. Push back. Say what’s wrong. Ask for a different angle, a shorter version, a warmer tone, a harder critique. “This is too formal — loosen it up.” “Cut the second half.” “Now argue the opposite side so I can see what I’m missing.”

Each correction makes the next version better, because you’re adding the information the AI didn’t have the first time — namely, what you actually want. The people who get the most out of these tools aren’t the ones with magic prompts. They’re the ones who go three or four rounds instead of one.

4. Verify — you own the facts

Here is the one place where being clear-eyed matters most. A system that predicts text can produce confident, fluent statements that are simply wrong — a made-up statistic, a citation that doesn’t exist, a “fact” it assembled because it sounded right. This isn’t the tool being broken; it’s a normal byproduct of how it works. So the rule is simple: fluent is not the same as true. Anything that actually matters — a number, a name, a date, a medical or legal or financial claim — you check against a real source before you rely on it.

This doesn’t mean distrusting everything. For brainstorming, drafting, explaining, and organizing your own thoughts, the tool is excellent, and you rarely need to fact-check your own ideas back to yourself. Verification is for the claims you’d be embarrassed or harmed to get wrong. Why AI makes things up → walks through exactly why this happens and how to catch it.

5. Keep the judgment yours

The most important habit is also the quietest one. The AI is a mirror and a tool. It can draft, suggest, and reflect — but you decide what’s good. It doesn’t decide for you, and it shouldn’t. When it writes something, you’re the editor. When it gives advice, you’re the one who weighs it against what you know about your own life. When it sounds confident, that confidence is a feature of the writing, not evidence that it’s right.

Keeping the judgment yours is what makes everything above safe to use freely. You can frame boldly, hand it real material, and iterate fast precisely because the final call stays with you. The tool gets better the more you use it well — it never gets to be the one who decides.

Go deeper: the technical version

Under the hood, these systems are large language models: networks trained to predict the next chunk of text (a “token”) given everything before it. “Framing” and “giving it context” both work because the output is shaped by the text in its context window — the running input it can currently see — on top of everything it learned in training. More relevant, specific input shifts the probabilities toward the answer you want; vague input leaves it predicting the bland average of everything it ever read. Iteration works for the same reason: each exchange adds to that context, so your corrections literally become part of what the next prediction is based on. Fabrication (often called “hallucination”) is the flip side — the model is optimizing for plausible-sounding text, not verified text, so when it lacks the real information it will still generate a fluent, well-formed answer. The model has no reliable built-in “I don’t know,” so it tends to fill the gap rather than flag it. That’s why verification has to come from you — and why the same property that makes it a strong drafting partner is the one that makes outside fact-checking non-negotiable.

The one-line version: frame the request, give it the real material, treat the first answer as a draft and push back, check anything that matters against a real source — and always keep the final judgment yours. That’s the whole craft.

Where to go next

The other half: using it safely

The protective companion to this page — the few habits that keep even a heavy AI habit a healthy one.

Use it safely →

Why you always verify

Why a confident AI can still be wrong — and the simple way to catch it before it costs you.

Why AI makes things up →

Going deeper: designing AI for a person

The same instincts, taken all the way down — the language practice behind building an AI that genuinely serves someone.

The Method →

The free course, RI-101

The long form: how AI works, how a conversation can drift, and how to use and build it well.

Start RI-101 →