Claude guide

Instructions vs context in Claude: what goes where?

In Claude, instructions say how to work and context is the information Claude refers to while working. Tone, format and role belong in instructions, while documents and background material are context. This guide explains the difference and what to put in account instructions, project instructions, project knowledge, memory and skills.

Skillshop operator and creator of the Maker Evan YouTube channel
6 min read

Translated from Korean. View original

An instructions card with numbered rules next to a context card holding a PDF, an image and a table
In this guide
  1. How do instructions and context differ?
  2. What is the context window?
  3. Where do you write instructions?
  4. How do you give Claude context?
  5. Where should this content go?
  6. Do longer instructions work better?
  7. How does this split work in Claude Code?
  8. Frequently asked questions
  9. Sources

How do instructions and context differ?

Instructions are the way of working you give Claude. ‘Answer politely’, ‘Put the conclusion first’ and ‘Review this as a marketer’ all decide how an answer is made. Content that applies the same way across many requests suits instructions.

Context is the information Claude refers to when answering. Pasted meeting notes, an attached PDF, earlier turns in the conversation and documents uploaded to a project are all context. Material and background that change with each request belong here.

Instructions: how to work
  • Tone and writing style
  • Answer format and length
  • The role to play and rules to follow
Context: what to know
  • Attached documents and pasted material
  • Earlier parts of the same conversation
  • Background material uploaded to a project
Put the method in instructions and the material in context.

What is the context window?

Anthropic's documentation describes the context window as all the text a model can reference when generating a response. It works like working memory. The system prompt, every message, tool results, images and documents, and the response Claude writes all count toward it.

So instructions take up space in the context window too. Instructions and context play different roles but share the same space. The documentation notes that accuracy and recall degrade as the token count grows, and that more context is not automatically better.

Where do you write instructions?

The Claude apps have several places for instructions. Account instructions apply to every conversation. Click your initials at the lower left, open Settings > Your Claude and write in the ‘Instructions’ field. Project instructions apply only to chats within that project.

A skill is a set of instructions that loads only for a specific task. Long, concrete methods such as a weekly report procedure suit skills. Claude's help center says to use profile instructions for account-wide settings and project instructions for guidance specific to a project.

WhereScopeWhat fits
Account instructionsEvery conversationDefault tone and the answer format you always want
Project instructionsChats in that projectThe project audience, terms and document format
SkillsOnly for relevant tasksProcedures for repeated work with set steps
A request in the chatThat conversationConditions needed just this once
Four places to write instructions and the scope of each.

How do you give Claude context?

The simplest way is to paste material into the conversation or attach a file. Documents you reuse across conversations go in project knowledge, which helps Claude understand the background for chats in that project. Projects are available on the Free plan too, up to five.

Memory is also a kind of context. Claude saves what to remember as individual topics while you chat. Each project has its own memory, and you can view, edit or delete saved topics under Settings > Your Claude by choosing ‘Manage’ next to ‘Your memory’.

Attach in chatPaste or upload material needed only for this request.
Project knowledgeKeep documents you reuse across conversations.
MemoryRemembers topics that come up in your chats.
Three ways to give Claude context.

Where should this content go?

When unsure, ask two questions. Is it a method or material? Is it needed every time or only now? A method needed every time is an instruction, material used repeatedly is project knowledge and anything needed only now goes in the conversation.

The table below lists examples that are easy to mix up. People often paste a whole product brochure into the instructions field, but a brochure is material and belongs in project knowledge. In instructions, write only how to use it, such as ‘Use the terms from the brochure as written.’

ContentWhere it goesWhy
Always answer politelyAccount instructionsA method for every conversation
Start reports in this project with a summary tableProject instructionsA method for one project
Company product brochureProject knowledgeMaterial referenced many times
Today's meeting notesAttach in chatMaterial needed only for this request
Weekly report procedureSkillA long procedure loaded only when needed
Choose the place by whether it is a method or material, and whether it is needed every time.

Do longer instructions work better?

Longer does not mean better followed. Instructions occupy the context window, so the longer they get, the less room remains for other material. The Claude Code documentation recommends keeping each instruction file under 200 lines and says longer files consume more context and reduce adherence.

Keep instructions to what must be followed, short and specific. ‘Keep paragraphs to three sentences or fewer’ is easier to follow than ‘Write well’. Moving long procedures needed only for certain tasks into skills keeps everyday conversations light.

How does this split work in Claude Code?

In Claude Code, the CLAUDE.md file plays the role of instructions. The documentation describes CLAUDE.md as instructions you write to give Claude persistent context. Put content for all projects in ~/.claude/CLAUDE.md and content for one project in the CLAUDE.md in that project folder.

The file is loaded at the start of every conversation. Claude treats it as context, not enforced configuration, so being short and specific matters here too. For material such as code and documents, Claude reads the files it needs as it works and brings them into context.

Frequently asked questions

What is the difference between instructions and context in Claude?

Instructions set how Claude works, such as tone, format and role. Context is the information Claude refers to while working, such as attached documents, earlier conversation and project material.

Should reference documents go in instructions or project knowledge?

Documents are material, so project knowledge is the right place. In instructions, briefly say how the document should be used.

Are longer instructions better?

No. Instructions take up the context window too. The Claude Code documentation recommends keeping instruction files under 200 lines. Write only what is needed, specifically.

Sources