InnerVault

Your cart

Your cart is empty. Add a skill and it waits here. See skills you own

Subtotal$0.00

One payment, secure checkout by Whop. Prices in USD.

My skills

Master Claude: Your AI-Powered Work Assistant / Projects and prompting

Projects, instructions and knowledge

About 12 minutes

If you repeat the same background in every chat, you need a Project. A Project is a self-contained workspace with its own chat history and its own knowledge base. Every chat inside it starts with the same context.

Plan notes (checked 2026-11-18)

  • All users can create Projects. Free accounts are limited to five.
  • On paid plans, when project knowledge gets close to the context limit, Claude can switch to retrieval (RAG), which the help centre says expands capacity by up to 10 times.
  • Sharing a Project with colleagues is for Team and Enterprise plans only.

The three parts of a Project

  1. Instructions: how Claude should behave in every chat in this Project. Tone, role, rules, format.
  2. Knowledge: files and text Claude should use as background. Price lists, style guides, past examples, product details.
  3. Chats: the conversations you have inside the Project.

Step-by-step: build your first Project

  1. In Claude, open Projects from the sidebar and create a new Project.
  2. Give it a clear name, such as "Client emails – Smith Design".
  3. Add a short description so you remember what it is for.
  4. Open the Project's instructions and paste a first version. Adapt this template:
You help me write client communication for Smith Design, a two-person web design studio.

Audience: small business owners who are not technical.
Tone: friendly, direct, plain English. No jargon. No exclamation marks.
Rules:
- Never promise dates, discounts or features unless I give them to you.
- If information is missing, ask me before writing.
- Keep emails under 150 words unless I ask for more.
Format: subject line first, then the email body.
  1. Add knowledge. Good first files are: - your services and prices, - two or three past emails you were happy with, - any style rules you follow.
  2. Start a chat in the Project and test it:
A client asks if we can add an online shop to their site next week. Draft a reply.
  1. Check the result against your instructions. Did it avoid promising a date? Did it ask about missing details?

Writing good instructions

  • Short and specific beats long and vague. Ten clear rules work better than two pages of preferences.
  • Explain the reason for unusual rules. "No exclamation marks, because our clients are lawyers" gives Claude something to generalise from.
  • Update after mistakes. Each time Claude gets something wrong in the same way twice, add a rule.

Choosing knowledge files

Good knowledge is accurate, current and relevant. Ask yourself for each file: would I give this to a new assistant on day one?

Remove:

  • old price lists,
  • drafts that contradict the final version,
  • anything containing other people's private data.

If two files disagree, Claude may use either. Keep one source of truth.

Using the carry-forward summary

In Lesson 2 you saved a summary of decisions. Paste it into your Project knowledge as a text file called "Decisions so far". Now every new chat starts with those decisions.

Common mistakes

  • Dumping every file you own into knowledge. More is not better. Conflicting files cause conflicting answers.
  • Writing instructions once and never changing them. Treat them as a living document.
  • Using one Project for everything. One Project per client, product or recurring job keeps context clean.

Exercise

  1. Create a Project for the task you chose in Lesson 1.
  2. Write instructions with at least: audience, tone, three rules and a format.
  3. Add two to four knowledge files.
  4. Run three test chats. After each, note one thing to change in the instructions, and change it.