The Problem Nobody Talks About
Every time I started a new conversation with an AI tool, I'd spend the first five minutes doing the same awkward dance. "So, um, I'm learning to code, I'm a career changer, I don't have a CS background, please don't use jargon..." It felt like introducing myself to the same coworker over and over again because they kept forgetting who I was.
The thing is, this isn't really the AI's fault. Most AI tools don't have persistent memory turned on by default, and even the ones that do can only hold so much. Every new chat is basically a blank slate. So if you want the AI to actually understand your situation and give you useful answers, you have to tell it — every time.
That's where an onboarding prompt comes in. It's a short, reusable block of text you paste at the start of any new conversation (or drop into a system prompt, custom instruction, or CLAUDE.md file). Think of it as your personal AI briefing document. Write it once, use it everywhere, and stop re-explaining yourself forever.
What an Onboarding Prompt Actually Does
An onboarding prompt does three things. First, it sets context — it tells the AI who you are and what you're trying to accomplish. Second, it sets constraints — it tells the AI how you want to be helped (simple language, no jargon, step-by-step, etc.). Third, it sets tone — it tells the AI what kind of collaborator you want it to be.
Without this, the AI makes assumptions. And those assumptions are often wrong. I once asked ChatGPT to help me understand a Python function, and it launched into a response that assumed I knew what decorators, closures, and lambda functions were. I did not. I had to stop the whole conversation, clarify my level, and start over. A good onboarding prompt would have prevented that entirely.
The beauty is that once you've written a solid one, you can paste it into ChatGPT, Claude, Gemini, Copilot chat — basically any conversational AI tool — and get a head start in any session.
The Four Parts of a Good Onboarding Prompt
I've tried a lot of different formats over the past year. Some were too long and the AI basically ignored half of it. Some were too vague and didn't change anything. Here's the structure that actually works for me:
1. Who you are — One or two sentences about your background and what you're working on. Not your life story, just the relevant stuff.
2. Your skill level — Be specific. "Beginner" is vague. "I've been coding for three months and I understand variables, functions, and basic loops but I get lost with classes and APIs" is useful.
3. How you want to be helped — This is where you set the rules. Do you want explanations or just answers? Do you want it to ask clarifying questions before diving in? Do you want analogies?
4. What you're working on right now — Optional, but useful if you're in the middle of a project. Give the AI a snapshot of your current goal so its answers stay relevant.
A Real Example You Can Steal and Customize
Here's the actual onboarding prompt I used when I was first getting into AI-assisted coding. Feel free to grab it and make it your own:
# My AI Onboarding Prompt
Before we start, here's some context about me so you can
give me the most useful help:
WHO I AM:
I'm a career changer learning to code. My background is in
[marketing / teaching / etc.], not tech. I've been coding
for about [X months] on my own using tutorials and AI tools.
MY SKILL LEVEL:
I'm comfortable with [variables, functions, basic loops].
I struggle with [classes, APIs, error messages, etc.].
I'm working mostly in [Python / JavaScript / etc.].
HOW TO HELP ME:
- Explain things in plain English before showing code
- Use analogies when a concept is abstract
- Break answers into numbered steps when possible
- If something has a technical name, explain what it means
- If my question is unclear, ask me to clarify before answering
WHAT I'M WORKING ON RIGHT NOW:
I'm trying to [build a small web app / learn APIs / etc.].
My current goal this week is [specific task].When I first started using something like this, the change was immediate. The AI stopped assuming I knew things I didn't. It started adding little explanations I actually needed. It felt less like talking to a professor and more like talking to a patient tutor who actually knew my situation.
Where to Put Your Onboarding Prompt
Depending on which AI tool you're using, there are a few different places this lives:
ChatGPT Custom Instructions: Go to Settings → Personalization → Custom Instructions. Paste the "about you" part in the first box and the "how to respond" part in the second. This runs automatically in every new chat — you don't have to paste anything.
Claude (new conversation): Just paste it at the top of your first message. Claude is great at picking up on this kind of context and referring back to it throughout the conversation.
CLAUDE.md files: If you're using Claude Code on a project, drop a version of this into your CLAUDE.md file in the project root. Claude will read it every time you start a session in that project. (We have a whole article on CLAUDE.md files if you want to go deeper on that.)
Cursor or Copilot system prompts: If you're in an AI-assisted IDE, check for a "system prompt" or "rules" field in settings. Same idea — paste it there and it applies automatically.
Save it somewhere you can find it
Keep your onboarding prompt in a plain text file, a notes app, or your AI prompt journal. You'll want to paste it into tools that don't have a persistent settings area, and you'll want to update it as your skills grow.
Common Mistakes (I Made All of These)
Being too vague about skill level. Saying "I'm a beginner" doesn't tell the AI much. Every AI tool I've used interprets "beginner" differently. Be specific about what you know and what you don't. The more concrete you are, the better the calibration.
Making it too long. I once wrote a 400-word onboarding prompt. The AI technically read it, but the later parts clearly got less weight. Keep it under 200 words. Hit the highlights, skip the backstory.
Never updating it. Your onboarding prompt should grow with you. When I learned how to work with APIs, I updated my prompt to remove that from the "I struggle with" list. It took 30 seconds and immediately changed the quality of answers I got on API-related questions.
Writing it once and forgetting it. The prompt is only useful if you actually use it. Build a habit: every time you open a new chat in a tool that doesn't have persistent memory, the first thing you do is paste your onboarding prompt. It becomes second nature faster than you'd think.
A Lightweight Version for Quick Sessions
Sometimes you're just popping into a quick chat to ask one question and you don't want to paste a whole block of text. For those situations, I keep a two-sentence "mini onboarding" I can drop in fast:
Quick context: I'm a self-taught beginner coder, about
[X months] in, working in [Python/JS]. Please keep
explanations simple and step-by-step — assume I don't
know jargon unless you explain it first.It's not as powerful as the full version, but it's way better than nothing. The AI immediately adjusts its register and stops throwing terminology at me like I'm a senior dev.
Your Next Step
Here's what I want you to do right now: open a notes app, copy the template from earlier in this article, and fill it in for yourself. It should take you about 10 minutes. Then save it somewhere easy to access — your phone notes, a pinned tab, a sticky note on your desktop, whatever works for you.
Then the next time you open a new chat with any AI tool, paste it in before your first question. Watch what happens to the quality of the response. I'm willing to bet you'll notice the difference immediately.
The AI tools haven't changed. But the way you're introducing yourself to them has. And that makes all the difference.
More tutorials in this category, or explore the full field guide.