How to Use AI

The Basics

Three ideas that, once you understand them, explain almost every bad experience you've had with AI.

You don't need to be technical to use AI well. But you do need three simple mental pictures in your head. If you skip this page, the rest won't make much sense. Go slow here.

1. Tokens

An AI model doesn't read words the way you do. It reads little pieces called tokens. A token is usually a short chunk, about three quarters of an average English word. The word "cat" is one token. The word "running" might be two.

The way to think about tokens is as fuel. Every question you type and every answer the AI gives back uses up some fuel. The bigger the question, the more tokens it costs. The longer the answer, the more tokens it costs. If you get close to running out, the AI starts acting strange: forgetting earlier parts of the conversation, repeating itself, or cutting off mid-sentence.

How a sentence breaks into tokens A SENTENCE YOU TYPE "The cat was running quickly to the house." HOW THE AI READS IT: AS TOKENS The cat was run ning quickly to the house . 10 tokens. Each one costs a little fuel. Notice: "running" became two tokens, "run" and "ning". That's normal.
One sentence, ten tokens. Roughly three tokens per four words. Every token you send, and every token the AI sends back, uses up fuel.
Quick picture

Tokens are like the gas in a car. A short trip uses a little. A cross-country drive uses a lot. If you keep driving without filling up, the car sputters.

There's one more thing tokens explain, and it surprises people. Because the AI reads chunks, not individual letters, it's bad at anything letter-by-letter. Ask it "how many R's are in strawberry?" and it may get it wrong. Ask it to count the words in a paragraph and it may miscount. This isn't a sign it's broken. It simply never sees the letters the way you do.

The letter blind spot

The AI can write a beautiful sales page and then miscount the letters in a single word. When you need something exact, a character count, a word count, a bit of math, don't trust the guess. Tell it: "use code to count this." It'll write a tiny program that gives the precise answer instead of eyeballing it. More on this below.

2. Context windows

A context window is how much the AI can hold in its head at one time during a single conversation. Everything you've typed, every answer it's given, every file you've attached, it all lives inside this window.

When the window fills up, the AI doesn't crash. It quietly starts forgetting the oldest parts of the conversation to make room for new stuff. This is why, after a long chat, the AI seems to ignore something you told it at the beginning. It didn't ignore you. It forgot.

Different tools have different-size windows, and the exact numbers keep changing, so treat these as rough and "as of writing":

Don't memorize the figures. The point is only this: the window is big, but it is not infinite, and every tool has one.

A context window filling up over a conversation FRESH CHAT plenty of room left ONGOING CHAT still working. WINDOW FULL: EARLIEST PARTS BEGIN TO FADE The AI starts "forgetting" the oldest messages to fit new ones. you the AI being forgotten
A context window fills up message by message. When it's full, the oldest parts silently drop off.
Quick picture

A context window is the AI's short-term memory. Like a whiteboard. When the whiteboard fills up, the oldest writing gets erased to make room for the new.

Two habits come straight out of this whiteboard picture, and they'll save you a lot of frustration:

3. The model has no memory: the whole chat is re-sent every turn

This is the fact that makes the context window finally click, and almost nobody is told it.

The model does not sit there remembering your conversation between messages. It remembers nothing. Each time you hit enter, the tool quietly gathers up the entire conversation so far, your first message, its first reply, your second message, its second reply, all the way down to what you just typed, and hands that whole pile to the model as if for the first time. The model reads all of it, writes one reply, and then forgets it ever happened. Next turn, the pile is gathered up and handed over again, now one exchange longer.

Nothing carries over between turns except the transcript itself. The model is like someone with no short-term memory who is handed the full notepad before every single answer. It reads the whole notepad, speaks, and forgets. The only reason the conversation feels continuous is that the notepad keeps growing and keeps being re-read.

The whole transcript is re-sent to the model on every turn TURN 1: WHAT GETS SENT msg 1 (you) MODEL Reads the pile, replies once, forgets everything. TURN 3: WHAT GETS SENT (THE WHOLE PILE AGAIN) msg 1 (you) reply 1 (AI) msg 2 (you) reply 2 (AI) msg 3 (you) MODEL Same model. Same fresh read. Just a bigger pile, everything from turn 1 onward, handed over again from scratch.
On turn 1 the model is handed one message. On turn 3 it's handed the same pile plus everything since, re-read from scratch. Nothing persists between turns except the transcript.

Three things you've probably noticed all fall out of this one fact:

4. Grounding

This is the most important idea on the page.

Grounding means pinning the AI to specific, real information you give it, instead of letting it guess based on the whole internet.

Consider two ways of asking the same thing:

"Write me a welcome email for new customers."

That's ungrounded. The AI will write some generic welcome email using patterns it has seen a million times. The result will feel bland, corporate, and unlike you.

"Here is my brand voice doc, my last five welcome emails, and my list of services. Write a new welcome email in the same tone, mentioning my free intro call."

That's grounded. The AI is pinned to your real materials. The answer will sound like you, not like a stock template.

Almost every complaint about AI ("it's so generic," "it doesn't sound like me," "it just makes things up") is really a grounding problem. The AI wasn't told enough. It was guessing.

Ungrounded versus grounded prompting UNGROUNDED "Write me a welcome email for new customers." AI (guessing generically) no files · no context no voice samples RESULT "Welcome to our family! We're thrilled to have you. Don't hesitate to reach out with any questions." GROUNDED "Write me a welcome email for new customers." about.txt voice.txt samples.txt AI (reading your real files) pinned to your voice + facts RESULT "Hey, welcome. Since you booked your first consult, here's what to expect and the free 20-min intro call..."
Same question, two very different setups. The right column gives the AI real files about you, and the answer stops being generic and starts sounding like you.

5. What it knows, and what it's only guessing

Here's a mental picture that ties the whole page together. Think of the AI as a lossy zip file of the internet. It read an enormous slice of the web and squeezed it down into patterns, the vibes and statistics of how words tend to go together. It did not keep exact copies of anything.

That one fact predicts what it's good and bad at:

A gentle peek under the hood (optional)

You do not need any of this to use AI well, but some people feel calmer knowing roughly what's inside. Picture layers of tiny switches, each holding a number, wired together. Words flow in as numbers, ripple through the layers, and a next-word guess comes out the other side. It "learned" by being nudged, over billions of examples, to make better guesses. There's no rulebook and no lookup table in there, just pattern recognition trained from a mountain of text. That's the whole machine.

6. Lean on its tools

The AI has two weak spots you already met on this page: it can't do exact letter-and-number work reliably, and its built-in knowledge is frozen at the moment it was trained, so it doesn't automatically know today's news, prices, or events. Both have a simple fix, and it's the same move each time: tell it to use a tool.

Two weak spots, two tools Exact numbers and counting go to code, which computes the answer. Recent or local facts go to web search, which looks them up. Both replace a guess from frozen training. you ask for say an exact countor sum today's priceor hours "use code" "search the web" instead of a guess from frozen training
Both weak spots have the same fix: stop it guessing from memory and have it use a tool. Code for exact numbers, search for anything recent.

Why this matters

If you take one thing from this page, take this:

Bad output is almost never the AI being stupid. It's almost always a setup problem: not enough context, not enough grounding, or the context window is full.

Once you start thinking this way, you stop getting frustrated at the AI and start asking: "What did I forget to tell it?"

The rest of this guide is about fixing the setup. You'll learn how to load your real information into both Claude and Gemini once, so you never have to re-explain yourself, and how to ask questions in a way that gets grounded, specific, useful answers.

Quick check · 1 of 2

You've been chatting with an AI for a long time and it seems to have forgotten something you told it near the start. Why?

Answer: every conversation lives inside a fixed-size "context window," the AI's short-term memory. When it fills up, the oldest messages get silently pushed out to make room for new ones.

This is exactly the problem that Projects solve. They keep your core information permanent so it never gets pushed out of the window.

Quick check · 2 of 2

Your AI answer comes back feeling generic, nothing like your voice or the thing you're working on. What's the most likely cause?

Answer: generic output is almost always a grounding problem. The AI wasn't given enough of your real materials (writing samples, notes, the actual documents) so it defaulted to averaged internet patterns.

The fix isn't a different AI. It's giving the same AI more of your real stuff.

Quick check · bonus

You need to know the exact number of words in a caption, and how much you'd make if 14 clients each paid $450. What's the most reliable way to ask the AI?

Answer: the AI reads chunks of text, not individual letters or digits, so counting and arithmetic are exactly the things it fumbles. Telling it to "use code" makes it write a tiny program that returns the precise answer.

Same idea for anything recent or local: tell it to "search the web" rather than trust its frozen, half-remembered training.