Save what works as a Project

A prompt that lives only in your head is a liability. This lesson turns the workflow you built and debugged in the previous two lessons into a Claude Project — a named workspace with a system prompt, attached context, and example outputs that any teammate can use without asking you what the prompt is.

What a Claude Project is

A Project is a named conversation environment with three persistent layers:

1. System prompt — instructions Claude reads at the start of every conversation in this Project, before you type anything.
2. Project files — documents attached at the Project level. They persist across sessions. You do not re-attach them each time.
3. Conversation history — prior conversations within the Project are accessible in the sidebar. You can reference them or start new ones that still inherit the system prompt and files.

A Project is not a saved chat. It is more like a configured tool: the settings stay constant while the conversations vary.

Walk-through

This is the hands-on portion. Budget 20 minutes.

Step 1 — Create the Project. In the Claude Desktop sidebar, click the "Projects" section and then "New Project." Give it a name that describes the workflow, not a generic name like "My Project." Example: "Sprint Status Emails."

Step 2 — Write the system prompt. In the Project settings (gear icon), paste your finalized workflow prompt as the system prompt. Remove the variable slot — that becomes the user's input in each conversation. The system prompt should be complete enough that someone who has never seen your prompt can use the Project and get correct output.

Example system prompt for the meeting notes workflow:

You are a product manager's assistant summarizing engineering syncs for an executive audience.

Always produce:
- Three bullet points of decisions made (each under 20 words)
- One bullet of open questions (if any)
- One sentence on next actions, naming the owner

Constraints:
- Under 150 words total
- No jargon (write as if the reader has no engineering background)
- Do not invent information not present in the input
- If the input is unclear, ask one clarifying question before producing the summary

Step 3 — Attach context files. If your workflow depends on reference material — a style guide, a glossary, a list of team members' names and roles — attach those files at the Project level now. They will be available in every conversation without re-attaching.

Step 4 — Test with a real input. Start a new conversation inside the Project. Paste a real input (meeting notes, an email, raw data). Confirm the output matches what you expect from the system prompt. If it does not, edit the system prompt and test again.

Step 5 — Share with a teammate. Open the Project settings and use the "Share" option to invite one other person by email. Ask them to run the Project on their own input without explaining the prompt. If they get correct output, the system prompt is self-contained. If they get confused, the system prompt has a gap — find it and close it.

If you get stuck

• "I don't see a Projects section in the sidebar" — Projects requires a Pro, Team, or Max subscription. If you are on Free, you can still save prompts as starred chats, but the persistent file layer and system prompt are not available.
• "The system prompt is being ignored" — Check for a conflict: if your conversation message repeats an instruction that contradicts the system prompt, the conversation message usually wins. Make the system prompt's constraints absolute ("always," "never") rather than suggestive ("try to," "prefer").
• "My teammate's output is different from mine" — Check whether they are in the same Project or in a new chat. Also check whether the model picker shows the same model version for both of you. Different models produce different outputs on the same prompt.

Deliverable

A working Claude Project with a system prompt, at least one attached context file, and at least one conversation that produced usable output without manual correction. The explicit success criterion: a teammate ran the Project on their own input, received output they could use without asking you for clarification, and did not need to see the underlying prompt to do so. That is the test. If they needed the prompt, the system prompt has a gap.

Further reading

• "What's on the Desk" — what it looks like when every morning's session starts with the working set already arranged, and the small system that gets you there.