AIUnlimited
๐ŸŒณ

AI Foundations

๐ŸŒฑ
AI Seeds

Start from zero

๐ŸŒฟ
AI Sprouts

Build foundations

๐ŸŒณ
AI Branches

Apply in practice

๐Ÿ•๏ธ
AI Canopy

Go deep

๐ŸŒฒ
AI Forest

Master AI

๐Ÿ”จ

AI Mastery

โœ๏ธ
AI Sketch

Start from zero

๐Ÿชจ
AI Chisel

Build foundations

โš’๏ธ
AI Craft

Apply in practice

๐Ÿ’Ž
AI Polish

Go deep

๐Ÿ†
AI Masterpiece

Master AI

๐Ÿ“˜

AI Practice

๐Ÿ“–
Understanding Open-Source Models

Fundamentals and resources for open-source models

๐ŸŽฏ
From Problem to Model Task

Converting business problems to model tasks

โšก
Running Your First Model

See your first results in 30 minutes

๐Ÿ”ง
Fine-Tuning and Evaluation

Fine-tune models and evaluate performance

๐Ÿš€
Application Systems

Build real-world AI applications

๐ŸŽจ
Generative AI

Explore open-source AIGC models

๐Ÿค–
Agents

Learn Agent frameworks and MCP tools

๐Ÿ“
Supplementary Fundamentals

LLM basics and evaluation

๐ŸŽ“

Claude Academy

๐Ÿค–
Claude 101

Learn AI basics with Claude

๐Ÿ’ป
Claude Code 101

Code with Claude as your pair programmer

๐Ÿค
Introduction to Claude Cowork

Collaborate with Claude on complex projects

โš™๏ธ
Claude Platform 101

Build apps with the Claude API

Lab

7 experiments loaded
๐ŸงฌNeural Network Sandbox๐Ÿค–AI or Human?๐Ÿฅ‹Prompt Engineering Dojo๐ŸAlgorithm Race๐Ÿง AI Trivia Challenge๐Ÿ—๏ธSystem Design Canvas
๐ŸŽฏMock InterviewEnter the Labโ†’
๐Ÿš€

Career Development

๐Ÿš€
Interview Launchpad

Start your journey

๐ŸŒŸ
Behavioral Mastery

Master soft skills

๐Ÿ’ป
Technical Interviews

Ace the coding round

๐Ÿค–
AI & ML Interviews

ML interview mastery

๐Ÿ†
Offer & Beyond

Land the best offer

Get Started
AIUnlimited

MIT Licence.

ๆฒชICPๅค‡18025655ๅท-11

Learn

  • AI Basics
  • AI Practice
  • Claude Academy
  • Lab
  • Career Development

Community

  • About
  • FAQ

Support

  • Terms of Service
  • Privacy Policy
  • Contact
AI & Engineering Academicsโ€บ๐Ÿค Introduction to Claude Coworkโ€บLessonsโ€บStanding Context: Global Instructions and Projects
๐Ÿ“
Introduction to Claude Cowork โ€ข Intermediateโฑ๏ธ 15 min read

Standing Context: Global Instructions and Projects

Standing context: Global instructions and projects

In this lesson, you'll learn to set global instructions so Claude starts every session already knowing how you work, decide when a piece of work belongs in a project, and choose between the three ways to start a project.

Onboard your new collaborator

In Chat, memory builds itself โ€” turn it on and Claude learns from your conversations automatically. Cowork works differently. The context that carries from task to task is mostly the context you set up: global instructions, which apply to every Cowork session, and projects, where Claude builds memory automatically from the conversations you have inside them. Most people start with global instructions and add projects as recurring work surfaces.

Global instructions: the brief that applies to every session

Global instructions are a standing brief. You write them once, in Settings, and Claude will reference them during every session โ€” every chat, every scheduled task.

To set them up:

  1. Open the Claude desktop app and go to Settings โ†’ Cowork.
  2. Click Edit next to Global instructions.
  3. Write your brief and save.

What to put in it: who you are and what you do; the shorthand and acronyms you use (so Claude doesn't have to ask what "the QBR deck" is); and how you like output delivered (format, length, tone, etc.).

Your global instructions don't need to be complete on day one. As you work with Cowork more, you'll notice corrections you keep giving ("share the bottom line up front in your responses" or "don't use Oxford commas") โ€” those are global-instruction candidates.

Projects: a scoped workspace for a stream of work

Global instructions cover you. Projects cover what you're working on.

A project is a workspace tied to a specific stream of work โ€” a customer, a recurring deliverable, a launch. Inside the project are three things you can set up and one that Claude builds for you:

  • Instructions โ€” like global instructions, but scoped to this project.
  • Scheduled tasks โ€” recurring runs you've set up that belong to the project: the Friday status pull, the pre-meeting brief, the end-of-month rollup.
  • Context โ€” one or more folders or links Claude should work from. Every conversation in the project has access to them.
Lesson 11 of 280% complete
โ†Get Better Results Faster

Discussion

Sign in to join the discussion

  • Memory โ€” what Claude learns from the conversations you have inside the project. This builds up over time as you work; you don't write it.
  • That last one is the difference projects make. Outside of a project, each session starts fresh apart from your global instructions. Inside one, every conversation adds to what Claude knows โ€” so the next task opens with the client's situation, last week's decisions, and what's still open already in hand.

    Some streams of work that are good for a project:

    • A client or account. The folder of meeting notes and deliverables, and the standing instructions for the account. Every meeting prep, follow-up, and review draft happens inside the project, and Claude picks up the relationship as it goes.
    • A recurring deliverable. The monthly report, the quarterly review, the weekly leadership update. Each new cycle is a new conversation inside the same project that automatically builds on the insights from the last time.
    • A launch or initiative. The redesign, the migration, the new program rollout. Briefs, decisions, status updates โ€” the whole thread of the work in one place until it ships.

    Three ways to start a project

    There are three ways to create a project, depending on where the materials already live:

    • From scratch โ€” start empty, add instructions and context as you go.
    • From an existing folder on your computer โ€” point the project at a folder you already work out of. The folder becomes the project's working directory.
    • From a Chat project โ€” if you've been using projects in Chat, you can transition the instructions and knowledge over to Cowork. This only works one-way: changes you make in Cowork don't sync back to Chat.

    To create one, click Projects in the Cowork sidebar, then New project, and choose whichever option makes the setup easiest for you. You can change the working folder, instructions, and connectors at any time.

    Try it now

    Put both layers in place โ€” global instructions for you, and one project for a stream of work you're in right now.

    1. Write a first-pass global instructions block. Don't overthink it โ€” just start with a few sentences.

    A useful starter:

    I'm a [role] at [company], working on [main 1โ€“2 streams of work]. Here are some common [acronyms/shorthand] you need to know. Most of my deliverables are [docs, decks, briefs, models โ€” whatever]. I want updates and briefs concise โ€” lead with the recommendation, keep background to one paragraph. I like to review the .md previews before creating the final document file.

    2. Create a project for one stream of work. Pick something recurring โ€” a customer account, a monthly deliverable, a current initiative. Point it at the folder where the materials already live, or start fresh if there isn't one yet.

    What's next

    In the next lesson, you'll meet skills โ€” how to teach Claude the processes you and your team rely on, so the way you do specialized work happens automatically.