Projects, Artifacts and Keeping Work Organised
Learn how Projects hold instructions, knowledge and chats, how to write short project instructions, what artifacts are, and how to keep knowledge files tidy, with a real instruction and file checker.
In this lesson you will
- Explain Projects, instructions and knowledge
- Write short project instructions
- Know what artifacts are
- Choose the right place for each task
About 22 minutes
The fourth time Meera explained the newsletter
Meera edits the library newsletter every month. Every month, she opens a new chat and explains the same things: who reads it, what tone to use, how long each article should be, and what never to include. Four months in, she realises she has typed the same paragraph four times. There must be a better way. There is, and it is one of the best habits you can learn: put the things that do not change somewhere they are loaded automatically, and keep each new chat for the thing that does.
Projects: a workspace for ongoing work
Claude’s help pages describe Projects: a workspace that groups together instructions, reference files and the conversations for one piece of ongoing work. A project has three parts:
- Instructions: how Claude should behave in every chat in the project: its role, the tone, the format, the rules.
- Knowledge: files and text you add once, such as a style guide, past issues or a glossary, which Claude can draw on in every chat in the project.
- Chats: the individual conversations, each focused on one task.
Two details matter. First, each chat in a project starts with the project’s instructions and knowledge already in place. Second, as Anthropic’s help pages note, a chat’s own content is not automatically shared with other chats in the project: if something should be available every time, add it to the knowledge or the instructions. Projects exist in versions of Claude on several plans, but limits, such as how many projects you can have, how large the knowledge can be, and whether projects can be shared with others, depend on your plan, so check the current help pages.
Writing good project instructions
Instructions work best when they are short, specific and about things that stay the same. A long essay of rules is harder for Claude to follow and harder for you to maintain. Some guides suggest keeping instructions under a couple of hundred words, though there is no magic number. A useful structure has five parts: role, audience, style, format and boundaries. The program below builds a set of instructions for Meera’s newsletter from those five fields, counts the words, checks that no section is missing and, because knowledge files also need care, checks a list of file names for badly named files and duplicates.
fields = {
"role": "You are a friendly editor for a village library newsletter.",
"audience": "Readers are adults and teenagers, many with limited time.",
"style": "Use plain English, short sentences and no jargon.",
"format": "Give a headline, then two short paragraphs, then one line to act on.",
"boundaries": "If you are unsure of a fact, say so and do not invent details.",
}
instructions = "\n".join(fields.values())
words = len(instructions.split())
print("sections:", len(fields))
print("words:", words)
print("short enough (under 120):", words < 120)
needed = ["role", "audience", "style", "format", "boundaries"]
print("missing sections:", [k for k in needed if k not in fields] or "none")
files = ["style-guide.md", "past-issues.txt", "Style Guide FINAL.docx", "style-guide.md"]
import re
bad = [f for f in files if not re.fullmatch(r"[a-z0-9-]+\.(md|txt)", f)]
dups = sorted({f for f in files if files.count(f) > 1})
print()
print("files to rename:", bad)
print("duplicates:", dups)
sections: 5
words: 54
short enough (under 120): True
missing sections: none
files to rename: ['Style Guide FINAL.docx']
duplicates: ['style-guide.md']
The instructions have 5 sections and 54 words, well under a limit of 120, with nothing missing. The file check found one file to rename, [‘Style Guide FINAL.docx’], because its name has spaces and capitals, and one duplicate, [‘style-guide.md’], which would confuse any knowledge base. Neither problem is dramatic, but both show up later as strange behaviour, when old and new versions of a document disagree and Claude uses the wrong one. Keeping knowledge files tidy, current and clearly named is half the work of a good project.
Artifacts: things Claude makes that you keep
Sometimes Claude produces something substantial that you want to use outside the conversation: a document, a web page, a small tool, a diagram. Anthropic’s help pages describe artifacts: when Claude creates self-contained content that is long or reusable, it can open it beside the conversation, so you can see it, ask for changes, copy it, and in some cases publish or share it. You can usually ask for one directly, for example ‘Make this into a one-page document I can edit.’ Availability and sharing options depend on your plan and your version.
Turn the plan above into a one-page checklist I can print. Use plain headings and tick boxes. Keep it to one page.
Choosing the right place
- A normal chat for a one-off question or a quick draft.
- A project for work that repeats or needs the same background each time.
- An artifact for something you will keep editing, such as a document or a small page.
- A fresh chat inside a project for each new task, so conversations stay short and focused.
Putting everything in one giant project. If the instructions try to cover newsletters, taxes and poetry, they will fit none of them. One project, one job. Old, contradictory files in the knowledge are another trap: delete what is out of date.
Memory is a separate feature. In some versions, Claude can remember information across chats, and you can switch this on or off in settings. Instructions in a project are written by you and visible to you, so they are the more reliable place for rules that matter.
Practice for this lesson
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
What does a project hold?
- Only photos
- Only passwords
- Only one chat
- Instructions, knowledge files and chats
A project groups the instructions, reference files and conversations for one piece of work.
Is one chat’s content automatically shared with other chats in the project?
- Yes, always
- No, unless added to knowledge or instructions
- Only on Fridays
- Only for artifacts
Anthropic’s help notes that context is not shared between chats unless it is added to the project.
What makes good project instructions?
- As long as possible
- Constantly changing
- Hidden
- Short, specific, about things that stay the same
Short, stable instructions are easier to follow and easier to maintain.
What is an artifact?
- Substantial content Claude creates beside the chat
- A kind of file name
- A payment
- A chat error
Artifacts are self-contained documents, pages or tools that open beside the conversation.
Why delete outdated files from project knowledge?
- They are heavy
- They are illegal
- Old and new versions can contradict each other
- They change colour
Contradictory files can lead Claude to use the wrong information.
Summary
- Projects hold instructions, knowledge and chats for ongoing work.
- Short, stable instructions work best.
- Artifacts are substantial content you keep and edit.
- Keep knowledge files clearly named, current and free of duplicates.
Questions
Do I need a paid plan for Projects?
Projects exist on several plans, but limits and sharing depend on the plan. Check Anthropic's current help pages.
How long should instructions be?
Short and specific. Some guides suggest a couple of hundred words at most, but the right length is the shortest that covers what stays the same.
Can I share an artifact?
Often yes, though sharing options depend on your plan and version. Check what a shared link reveals before you send it.
