Kitchen Prep — Context Engineering | The Prompt Kitchen

What is context and why it matters

Imagine you've hired a brilliant contractor to renovate your kitchen. They show up on the first day with no information — they don't know your budget, your taste, whether you have kids, how much you cook, or that you specifically hate open shelving. They're talented, but their first suggestions will be totally generic.

Now imagine you gave them a two-page brief before they started: your budget, your aesthetic, photos of kitchens you love, a list of your must-haves and dealbreakers, and the fact that you've tried two previous renovations that went over budget. Their first suggestions are now tailored, specific, and far more useful.

AI works exactly the same way. Context is the brief. Without it, you get generic answers. With it, you get responses that feel like they were written specifically for your situation — because they were.

The difference between an AI newbie and someone who gets remarkable results from AI tools is usually not which tool they use. It's how much context they provide.

How AI "remembers" — context windows explained

Here's something that surprises most people: AI doesn't actually have memory the way you do. It can't remember your name from last week's conversation unless you tell it again. What it can do is read everything in the current conversation — your messages, its responses, any documents you paste in — and use all of that as its working context.

📋

The sticky-note analogy

Think of a context window like a whiteboard in a meeting room. Everything written on that whiteboard is visible to everyone in the meeting. The AI can see and use everything on the whiteboard — but when the meeting ends and the whiteboard is erased, it starts fresh next time with no memory of what was there before.

What this means practically:

  • If you start a new conversation, the AI has no memory of previous ones. You'll need to re-introduce yourself and your context.
  • Within a single conversation, the AI can see everything — so it gets smarter as you give it more information.
  • Very long conversations can eventually hit the "context limit" — like a whiteboard that's completely full. When this happens, earlier messages may get compressed or dropped. The AI may seem to "forget" things from earlier. The fix: start a fresh conversation and re-paste the essential context.
How long can a conversation be before it hits the limit?

It depends on the model and the plan you're using. For reference, most free-tier AI tools can comfortably handle conversations of about 20–50 messages with normal amounts of text. If you're pasting large documents, that limit shrinks. Paid tiers typically offer much larger context windows — Claude's extended context, for example, can hold the equivalent of a small novel.

In practice, for everyday use (emails, questions, short research tasks), you'll rarely hit the limit in a single conversation.

System prompts — set the scene before you start

A system prompt is a set of instructions you give the AI at the very beginning of a conversation — before you ask your actual question. It's like setting the rules of engagement before the meeting starts.

Some AI tools (like Claude and ChatGPT) have a dedicated "system prompt" field or "custom instructions" in their settings. Others, you can just paste it in as your first message. Either way works.

You are helping me with [general area — e.g., "work writing tasks" / "learning about personal finance" / "planning my home renovation"].

About me: [2-3 sentences about who you are and what's relevant — your job, your knowledge level, your situation]

My preferences:
- Tone: [how you want responses — e.g., "direct and concise" / "warm and conversational" / "technical is fine"]
- Format: [how you want things structured — e.g., "use bullet points" / "prefer prose" / "always start with the bottom line"]
- Avoid: [anything you don't want — e.g., "don't hedge everything with disclaimers" / "no jargon" / "don't give me legal/medical advice, just explain concepts"]

When I ask a question, assume I want [your default expectation — e.g., "practical advice I can act on today" / "a complete explanation I can understand without follow-up"].
You are helping me with professional writing tasks — emails, proposals, and internal communications.

About me: I'm a project manager at a mid-size software company. I communicate with technical developers, non-technical stakeholders, and external clients regularly. I'm a native English speaker but I write quickly and often need help making my writing more polished and clear.

My preferences:
- Tone: Professional but warm — not stiff corporate-speak, not too casual
- Format: Short and scannable by default. Use bullet points when listing things. Lead with the key point.
- Avoid: Long preambles, redundant phrases like "I hope this email finds you well," anything that sounds like a template

When I ask you to draft or improve something, assume I want it tightened and clarified, not lengthened.
💡

Save your best system prompts

If you find a system prompt that works well for a recurring task (writing, research, coding help), save it in a notes app or document. Next time you start a new conversation, paste it in as your first message. Instant expert assistant, every time.

Conversation priming

Priming is giving AI relevant background within the conversation, not as a formal system prompt. It's the difference between walking into a meeting cold and spending 5 minutes briefing the consultant first.

You can prime a conversation by simply saying:

Before I ask my question, let me give you some background so your answer can be as useful as possible:

[Brief your situation in 3-5 sentences: who you are, what you're working on, what you've already tried, what matters most, what you want to avoid]

Got all that? Now here's my question: [your actual question]

This one change — giving background before asking — is responsible for more improvement in AI output quality than almost anything else. It costs you 30 seconds and frequently saves you several rounds of back-and-forth.

Few-shot examples — show, don't just tell

Sometimes it's easier to show the AI what you want than to describe it. Providing 1–3 examples of your desired output — before asking for the real thing — is called few-shot prompting. (The "few shots" are the examples.)

This is especially powerful for stylistic tasks, where describing the style is harder than just showing it.

I want you to write [type of content] that matches this style. Here are examples of the style I'm going for:

Example 1:
[paste an example]

Example 2:
[paste another example]

Now write [your actual request] in the same style.
I want you to write a blog post introduction that matches our company's voice. Here are two examples of our existing intros:

Example 1:
"Most people think budgeting means tracking every coffee. It doesn't. It means knowing which numbers actually matter — and ignoring the noise. Here's how we think about it."

Example 2:
"There's a moment in most home renovations where you realize the original plan was wrong. Not failed — just wrong. That moment is actually where the interesting work begins."

Now write an intro for a post about why small businesses should audit their software subscriptions once a year. Same voice — direct, a little contrarian, short sentences, starts with a common assumption before flipping it.

Context templates for common tasks

Copy and fill these in before starting any of these kinds of conversations. The more detail you add, the better.

Job Application Help

I need help with a job application. Here's my context:

Role I'm applying for: [job title and company name]
What the job involves: [2-3 sentences from the job posting or your understanding of it]
My relevant background: [your current role, years of experience, key skills]
My biggest strengths for this role: [2-3 things you think make you a strong candidate]
Gaps or concerns: [anything you're worried might count against you]
Tone I want to project: [e.g., confident but not arrogant / warm and collaborative / senior and strategic]

I'll be asking you to help with: [cover letter / CV bullet points / interview prep / all of the above]

Research Assistant

I need help researching a topic. Here's what I'm trying to understand:

Topic: [what you're researching]
Why I'm researching it: [context — making a decision, writing something, satisfying curiosity, etc.]
What I already know: [your starting knowledge level]
What I specifically want to find out: [specific questions you need answered]
Format I want: [e.g., summary / list of key points / comparison table / pros and cons]
What I don't want: [e.g., "don't go into the history" / "skip the technical details" / "focus on practical implications"]

Coding Help

I need help with a coding problem. Here's my context:

Language / framework: [e.g., Python 3.11 / JavaScript / React / SQL]
What I'm trying to build or fix: [describe the goal or bug]
What I've already tried: [what you've attempted]
Error message (if any): [paste the exact error]
Relevant code: [paste the specific section — don't paste your whole codebase]
My experience level: [beginner / intermediate / I know the language but not this specific library]
What I want from you: [explain what's wrong / fix the code / show me a better pattern / all three]

Tips for long conversations

📌

Start with a summary, revisit it

At the beginning of long sessions, give the AI a brief of everything relevant. If the conversation gets very long, paste that brief again: "Just to recap what we're working on:" — it refreshes the context without starting over.

🔖

Use "remember this" checkpoints

Say "Remember this for the rest of our conversation: [key fact / decision / preference]." AI will explicitly acknowledge it and apply it to subsequent answers. This is especially useful for stylistic preferences or constraints.

🔄

Ask for a summary before context limit hits

If your conversation is getting very long, ask: "Summarize the key decisions and information from our conversation so far in a format I could paste into a new chat." This gives you a ready-made context primer for a fresh session.

🆕

Know when to start fresh

If AI starts giving answers that seem to ignore what you said earlier, you've likely hit the context limit. Start a new conversation, paste your context summary, and continue. It's faster than fighting a degrading context.

Ready to put this into practice?

The Daily Specials has complete, ready-to-use playbooks for the most common tasks — with context already built in.

Go to Daily Specials →