Context is everything

The trap: you're talking to a stranger every time

Most people use AI like a search engine. You type a question, you get an answer, you shrug ... “eh, that’s okay.” Then you decide AI is overhyped and go back to doing it yourself.

Here's what actually happened. You asked the smartest stranger you've ever met to do your work, and you told it nothing about you first. Not who you are, not who you serve, not what a good answer even looks like to you. Of course it came back generic. It was written for nobody, because it knew nobody.

Garbage in, garbage out. Everyone quotes that line. But the garbage going in is almost never a bad prompt. It's missing context.

You don't need a better prompt. You need it to know you.

Let go of prompt engineering. Claude is trained on all of language, so it gets the spirit of what you mean even when you say it messy. What it can't do, until you hand it over, is know your world: who you are, who you do it for, why you do it, what matters to you.

Think about the best hire you ever made. Drop them at a desk on day one with no onboarding, no context, no “here's who we are and here's the job,” and they'll still turn in mediocre work that first week. Same brilliant person. The only variable is context. AI is exactly the same. The intelligence is already there. The knowing-you is what you provide.

The move: let it interview you

Don't try to explain your whole self in one paragraph. You'll leave out the parts that matter most, because you're too close to them to see them. Flip it around. Make it pull the context out of you, one question at a time.

That five-minute conversation is worth more than any prompt you'll ever write. Instead of composing, you're just answering. And when it summarizes back, you catch what it got wrong before it ever touches your work. That's the whole move: it interviews you, it reflects it back, you correct it.

Save it once, and every session starts knowing you

Here's the part that makes this compound. That context shouldn't live in one chat and die when you close the window. Save it.

In Claude, it lives in your instructions file: click your name, go to Settings, find the “what should Claude know about you” box. Mine is short. Founder of PitchKitchen, I fix useless marketing and websites, writing style short and punchy, no corporate tone. Yours can be a paragraph or a full chunky background of your business, your customers, and how you like things done. Either way, from then on every new session loads that first and talks to you like it actually knows you.

You teach it once. It remembers forever. That's the difference between starting cold every morning and starting with a partner who already has the file open.

Context is more than facts. It's your voice.

Your context isn't only what your company does. It's how you sound.

If there's writing you love, yours or somebody else's, paste five samples into a fresh session and say: “Analyze this. Tell me the style, the tone, the angles, what makes it work underneath. Then write me a style guide, and a prompt, that would generate copy like this.” Now you've bottled your voice. It becomes a markdown file that travels with you, to Claude, to Codex, to whatever you use next, so you never re-explain how you sound again. Stop dancing between two tools trying to get the tone right. Capture it once and carry it everywhere.

The fastest way to feed it context: stop typing, start talking

Most people are still typing. Big mistake. Hit the dictation key and just talk to it.

It feels messy, and it doesn't matter one bit. Large language models are built on language. They get the spirit of what you meant, and they don't trip on the ums and the tangents the way you're afraid they will. Talking pours in three times the context in a tenth of the time, and context is the whole game. That one habit is the biggest unlock most people never flip.

The payoff: the relationship becomes the context

Here's what it looks like when it's working. A member in one of our sessions built a full client portal over a weekend, start to finish, and she'd tell you herself she's not technical. She never once typed that into Claude. It figured it out anyway, from how she worked, from the screenshots she kept sharing, from the questions she asked. And when it wrote her handoff file, the very first line was “she is not an IT professional.”

Nobody told it that. It knew her. That's context compounding: the more you work together, the more it understands you, until one day working without it feels like leaving the house without your phone. You'll reach for it, and you'll notice it's not there.