CertSafari
    Anthropic Claude Certified Associate – Foundations (CCAO-F) - December 7 onwards· Lessons

    Domain 5 · Lesson 15/21

    Configuring a Claude Project for a recurring use case

    Project Configuration

    16 min read
    3.75% of exam
    6 sources
    Published 18 Nov 2026
    Docs as of 11 Nov 2026

    What you will be able to do

    • Explain what a Project's instructions and knowledge apply to, and what they leave alone
    • Decide whether each requirement of a recurring task belongs in an instruction, a knowledge source or a Skill
    • Choose what to upload as a knowledge source and what to keep out of it
    • Use project memory, chat search boundaries and per-chat memory settings to keep unrelated work streams apart
    • Put Project setup in a working order: requirements, sorting, building, testing, then sharing

    Key concept

    Project scope — A Project is a self-contained workspace. Its instructions, knowledge base and memory shape the chats held inside it and nothing outside it. Configuring a Project means deciding what belongs inside that boundary for one recurring piece of work.

    1.What a Project's configuration reaches

    A Project is worth building when the same kind of work keeps coming back, such as a weekly newsletter, a monthly board report or a quarterly audit. You set the context once, and every chat in the Project starts from it. Without a Project you would re-explain the audience, re-attach the reference files and restate the rules each time you start the task.

    Two parts of a Project shape Claude's answers directly. Project instructions tell Claude how to behave, for example using a more formal tone or answering from the point of view of a particular role or industry. The project knowledge base holds uploaded documents, text and code that Claude uses as background for every chat in the Project. Instructions are saved through "Set project instructions", and Claude applies them to all the chats within the Project.

    The boundary works in both directions. Inside the Project, the instructions apply to every chat. They don't fade after the first reply, and they don't depend on what any particular chat happens to be about. Outside the Project they have no effect at all. A file copied into an ordinary chat is just a file, and it doesn't bring the Project's rules with it. If you want a rule in every conversation on your account, use custom instructions, which apply broadly to all your conversations, not a Project.

    One part of the setup dialog does nothing for Claude. When you create a Project you give it a name and a description, but Claude can't see either one. They are labels for people browsing the Projects list. A sentence like "always write for trustees" typed into the description never reaches the model, so it has to go in the instructions.

    A knowledge source is anything you upload to the project knowledge base: documents, text files or code snippets. Whatever sits there is available to all the chats in the Project, so it suits material Claude should read rather than obey, such as last year's reports, a style guide or a product sheet. Chats don't pass context to each other, which makes the knowledge base the dependable place for a fact that later chats must know. On paid plans a growing knowledge base switches to retrieval mode, where Claude searches the files instead of loading them whole, so clear file names pay off.

    Choosing among instruction, knowledge source and Skill comes down to what a requirement is. A rule about how answers should look is an instruction. Reference material is a knowledge source. A repeatable multi-step procedure is a Skill. A tone rule pasted into a knowledge file is just a document Claude may or may not weigh, and a twelve-report archive pasted into the instructions bloats the one place that should stay short.

    Checkpoint 1 of 8· Match them up

    A team lead is setting up a Project for a monthly board report. Match each place they could put information to what that place actually does.

    Tap a term, then the definition that fits it.

    Checkpoint 2 of 8· Exam question

    A finance analyst built a Project whose instructions say to always reply in a formal tone with a legal sign-off. Outside that Project, in an ordinary chat, she asks Claude to help write a relaxed message to a friend about weekend plans. What should she expect?

    Sources1234

    2.Instruction, knowledge or Skill: sorting each requirement

    Most configuration mistakes happen at the sorting step. A recurring task usually comes with a mix of requirements: some are rules, some are reference material and some are procedures. Each kind has a natural home, and the deciding question is what the requirement *is*, not how often Claude needs it.

    A standing behaviour rule, such as "address trustees", "stay under two pages" or "use a formal tone", is an instruction. It describes how every answer in the Project should look. Reference material, such as last year's reports, a style guide or a product sheet, is knowledge. These are documents Claude reads for context, and they belong in the knowledge base so every chat can draw on them. Give the files clear names: well-named files help Claude find the right information, and that matters even more once a large knowledge base switches to retrieval mode on paid plans.

    A repeatable, multi-step procedure is a Skill. Skills are folders of instructions, scripts and resources that teach Claude to do a specific task the same way every time. Examples include building a chart to a fixed method, applying brand guidelines or structuring meeting notes in a company format. Skills use progressive disclosure: Claude checks which Skills are relevant and loads only those, so a long procedure doesn't take up context in chats that don't need it.

    Where each kind of requirement belongs
    ComponentWhat it holdsWhen it is in playWhere it reaches
    Project instructionsBehaviour rules: tone, role, audience, lengthEvery chat in the ProjectThat Project only
    Project knowledgeDocuments, text and code used as backgroundLoaded for every chat in the ProjectThat Project only
    SkillA specialized, repeatable procedureLoaded dynamically, only when relevantEverywhere across Claude
    Custom instructionsBroad personal preferencesEvery conversationThe whole account

    The last column decides the hard cases. Suppose a nonprofit's board-report Project has three needs: a rule to write for trustees in a formal tone, twelve past reports for reference, and a six-step donor-chart procedure that two other Projects use too. If you write the procedure into this Project's instructions, the other Projects never see it. If you package it as a Skill, it is available wherever Claude runs. Putting all three needs into instructions fails for a second reason as well: twelve past reports are documents, not rules, and they belong in knowledge.

    Skills are not set up inside a Project. You upload and toggle them in Customize > Skills, and they need code execution to be turned on. A custom Skill is private to the person who uploaded it until they share it, or until an organization Owner provisions it for all users. Sharing a Project with a colleague therefore doesn't give them your custom Skill.

    Checkpoint 3 of 8· Check yourself

    Three requirements come with a marketing manager's quarterly campaign-recap Project: (1) always write in the brand's plain, upbeat voice; (2) the last eight campaign results decks; (3) a five-step method for structuring recap notes that three other Projects also use. Which setup fits?

    Checkpoint 4 of 8· Check yourself

    After the owner shares their board-report Project with a colleague, the colleague's chats in it follow the Project instructions and use the knowledge files. But Claude never applies the donor-chart procedure that the owner uploaded as a custom Skill. What explains this?

    Checkpoint 5 of 8· Exam question

    A nonprofit is building a Project for its recurring monthly board report. The team lists three needs: the report must always address trustees and stay under two pages; the last twelve reports must serve as style references; and a six-step procedure for building the donor chart must be reused in other Projects. Which mapping is correct?

    Sources2435

    3.Scoped memory and keeping work streams apart

    Isolation is the other reason to use a Project. A client engagement, a hiring round and a personal side project shouldn't bleed into each other. The tool for this is memory: with memory turned on, Claude saves what it learns from your chats as a set of individual topics while you work, rather than summarizing conversations afterward, so a deadline you mention today is already known in the next chat. Claude saves on its own, and you can also tell it to "remember this" to store something directly.

    Each Project has its own memory, and when you work in one, Claude uses that Project's memory together with your memory from chats outside Projects. It never uses memory from other Projects. Past-chat search follows the same boundary: a search run inside a Project covers only that Project's conversations.

    Memory does not leak from one Project to another, but it can leak outward. Project memory is closed to other Projects, while the line between a Project and your general chats is open by default. For sensitive work, turn off "Use account memory" under Memory on the Project's page. That stops the Project from taking in your general memory and stops its own memory from reaching your other chats.

    Chats inside one Project don't automatically share context with each other. A detail you settle in Monday's chat isn't visible in Thursday's chat unless it has been added to the knowledge base or saved to the Project's memory. If a fact must reach every future chat, put it in the knowledge base. Hoping a past conversation carries it forward is unreliable.

    For a one-off exception, you can turn memory off for a single chat. Use the "Memory" switch in the "+" menu, and do it before you send the first message, because the setting can't be changed once the chat starts. A Project chat started this way neither reads nor adds to the Project's memory, which suits a tangent that shouldn't shape the Project's later work.

    Checkpoint 6 of 8· Check yourself

    For a confidential client engagement, a consultant needs two things. Nothing Claude learns in the client's Project should show up in their ordinary chats, and the Project shouldn't draw on what Claude remembers from those general chats either. Memory is on for the account. What should they configure?

    Sources62

    4.Building, testing and sharing in the right order

    Each setup step depends on the one before it:

    1. Write down what the recurring deliverable must achieve and list every requirement.
    2. Sort each requirement into an instruction, a knowledge file or a Skill.
    3. Create the Project and add its instructions and knowledge, and make sure any Skill the sorting called for is uploaded and enabled.
    4. Run a realistic chat in the Project and compare the draft with the original requirements.
    5. Share the tested Project with teammates.

    You can't sort requirements you haven't listed, and you can't build components you haven't sorted.

    Testing comes before sharing because sharing spreads whatever is in the configuration to everyone. On Team and Enterprise plans, a shared Project gives every member the same instructions and knowledge. A member with Can view access can see the contents, knowledge and instructions and can chat in the Project, but can't edit it. A member with Can edit access can change the instructions and knowledge. If a rule is wrong at launch, every view-only teammate writes from the faulty setup and can't fix it.

    Sharing can go to individual people by email, to a pasted list of addresses, or to the whole organization if an Owner hasn't turned that off. Give edit rights to the people who maintain the configuration and view rights to the people who only produce the deliverable. This keeps the team on one tested version of the setup.

    Checkpoint 7 of 8· Check yourself

    An operations lead has tested a monthly-report Project and is about to share it. Two colleagues maintain its rules and reference files. Eight analysts only use it to produce the report. Which sharing setup fits?

    Checkpoint 8 of 8· Exam question

    A communications team is preparing a new Project for its recurring weekly newsletter. Requirements include writing style rules, reference documents and a repeatable drafting procedure. Which sequence should the team follow to set up and roll out the Project?

    Sources12

    Sources

    (6)

    Every claim above is drawn from one of these pages, quoted as it was written on the date shown.

    1. 1.
      “For example, instructing Claude to use a more formal tone or answer questions from the perspective of a specific role or industry.”
      ↩︎ What a Project's configuration reaches
      “Can view: Members can see project contents, knowledge, and instructions, and chat within the project, but cannot edit it.”
      ↩︎ Building, testing and sharing in the right order
      “Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases.”
      ↩︎ Key concept
    2. 2.
      “Claude will use these instructions for all the chats within the project.”
      ↩︎ What a Project's configuration reaches
      “Give your project a name and description (note that Claude will not have access to these details).”
      ↩︎ What a Project's configuration reaches
      “Anything you upload to this space will be used across all of your chats within that project.”
      ↩︎ What a Project's configuration reaches
      “Anything you upload to this space will be used across all of your chats within that project.”
      ↩︎ Instruction, knowledge or Skill: sorting each requirement
      “Each project has its own memory.”
      ↩︎ Scoped memory and keeping work streams apart
      “Context is not shared across chats within a project unless the information is added into the project knowledge base.”
      ↩︎ Scoped memory and keeping work streams apart
      “Members can modify project instructions and knowledge”
      ↩︎ Building, testing and sharing in the right order
      “Give your project a name and description (note that Claude will not have access to these details).”
      ↩︎ Exam trap 2
      “Claude uses the project's memory alongside your memory from chats outside of projects, but not memory from other projects.”
      ↩︎ Exam trap 5
      “New memory is saved to the project, and if you have memory turned on, Claude can reference it in chats outside of projects too.”
      ↩︎ Prediction
    3. 3.
      “Custom instructions apply broadly to all your conversations.”
      ↩︎ What a Project's configuration reaches
      “Skills teach Claude how to complete specific tasks in a repeatable way”
      ↩︎ Instruction, knowledge or Skill: sorting each requirement
      “Skills work through progressive disclosure”
      ↩︎ Instruction, knowledge or Skill: sorting each requirement
      “Skills provide specialized procedures that activate dynamically when needed and work everywhere across Claude.”
      ↩︎ Instruction, knowledge or Skill: sorting each requirement
      “Custom instructions apply broadly to all your conversations.”
      ↩︎ Exam trap 1
      “Skills provide specialized procedures that activate dynamically when needed and work everywhere across Claude.”
      ↩︎ Exam trap 3
    4. 4.
      “When your project knowledge approaches the context window limit, Claude will automatically enable RAG mode”
      ↩︎ What a Project's configuration reaches
      “Well-named files help Claude understand and retrieve the right information more effectively.”
      ↩︎ Instruction, knowledge or Skill: sorting each requirement
    5. 5.
      “This feature requires code execution to be enabled.”
      ↩︎ Instruction, knowledge or Skill: sorting each requirement
      “Custom skills you upload aren't visible to colleagues until you share them.”
      ↩︎ Instruction, knowledge or Skill: sorting each requirement
      “Custom skills you upload aren't visible to colleagues until you share them.”
      ↩︎ Exam trap 4
    6. 6.
      “Claude saves memory as a set of individual topics as you chat, rather than summarizing conversations after they end.”
      ↩︎ Scoped memory and keeping work streams apart
      “Individual project conversations (searches are limited to within each specific project).”
      ↩︎ Scoped memory and keeping work streams apart
      “You need to turn memory off before you send the first message.”
      ↩︎ Scoped memory and keeping work streams apart
      “To keep a project's memory fully separate, turn off "Use account memory" under Memory on the project's page.”
      ↩︎ Checkpoint

    Ready to test yourself?

    Practise Anthropic Claude Certified Associate – Foundations (CCAO-F) - December 7 onwards in quiz mode.

    Spotted a mistake, or was something unclear? Tell us.