Lab: One project, one artifact

This is the smallest useful Project. No release calendar. No twenty-file knowledge dump. You will make a workspace for one recurring note, put standing context in it once, and leave with an Artifact you can reuse. Plan for about 15 minutes. Use claude.ai signed in.

​

The job

Every Monday you send a short leasing update to your asset manager. Today you will build the Project that makes that note stop starting from zero. If leasing is not your world, keep the same shape and rename it: weekly vendor issues, weekly hiring pipeline, weekly store ops. One recurring note. One audience.

​

Part 1: Create the Project

1. In Claude, create a new Project.
2. Name it after the work: Weekly leasing update.
3. Keep it private.
4. Open Set custom instructions and paste this:

That is the whole behavior layer. Short on purpose.

​

Part 2: Add one knowledge file

Create a plain text file on your computer named cedar-ridge-facts.txt, paste this in, save it, then upload it to Project knowledge: You now have:

• Instructions = how Claude should act
• Knowledge = facts Claude should look up

That is enough for a durable Project.

​

Part 3: Run one chat and ship an Artifact

Inside the Project, start a new chat and send:

​

Expected result

You want all three:

1. Claude uses the Project structure without you re-explaining it.
2. An Artifact opens in the side panel as a real document, not only chat text.
3. Missing facts are flagged instead of invented.

If no Artifact appears, say: “Put the update in an Artifact document.” Then edit one sentence in follow-up and watch the Artifact update.

​

Prove it compounds

Open a second new chat inside the same Project. Send only: If the Project is working, Claude still knows the audience, structure, and standing facts without a re-brief.

​

Flight card

​

Debrief

1. What did the Project save you from retyping?
2. What would you add to knowledge next week: one file only?
3. Name the real recurring note you will turn into a Project after class.