Jonathon's AI Wiki

Claude.ai Projects — Per-Project Context Containers

5 min read

Source: wiki synthesis: nate-herk-every-level-of-claude, skills-vs-projects-eliot-prince, cowork-projects-ai-consultant-recipe

Claude.ai Projects are the per-project context containers in claude.ai — a bundle of custom instructions, uploaded knowledge files, and persistent chat history scoped to a single workspace. They are the spine of serious claude.ai usage at the Beginner-through-Intermediate tier of Nate Herk’s 5-level framework: the cheat code from L1 (Enthusiast, single-turn chat) to L2 is “create your first project.” ^[inferred] The same concept extends into the Claude Cowork desktop app via Import from project, which transfers a Chat Project’s knowledge files and custom instructions into a Cowork Project that can additionally execute files and tasks.

Key Takeaways

  • Projects are nouns. Eliot Prince’s verb/noun mental model: skills are doing words (reusable processes that run anywhere in the Claude ecosystem); projects are things (scoped knowledge containers with overarching instructions and chat history). The linguistic test on any prompt: if you want Claude to know about a specific business / client / workspace, it’s a project.
  • Six features stack on top of Projects at L2. Continuity across conversations + memory & past-chat search + connectors (50+) + file creation + persistent artifacts with API access + inline visuals + Microsoft Office native add-ons. Projects are the surface that makes the rest load-bearing.
  • Token-cost win. Eliot Prince’s operator estimate: Projects can reduce token cost by ~90% in some cases versus re-uploading the same knowledge files in every fresh chat. ^[inferred] Particular leverage for users hitting Claude’s weekly cap on recurring context.
  • Scoped, not portable. Skills run anywhere — claude.ai chat, Cowork, Claude Code. A Project runs inside that one workspace only. This portability difference is the biggest functional consequence of the verb-vs-noun distinction.
  • Memory is free; past-chat search is paid. Per the L2 walkthrough, cross-conversation recall works on every plan including free; past-chat search is Pro-and-up. ^[inferred]
  • The 4-knowledge-file architecture is the consultant-tier spec. Business DNA + Client Intelligence Brief (reusable prompt-as-file) + Service Playbook + Consulting Framework. The architectural pattern that makes a Project usable as an “AI consultant,” not just a stocked pantry.
  • Living documents, not chat history. Custom Instructions and knowledge files are framed as documents updated after every engagement. “Fix the instructions, not the chat” — when Claude gets something wrong, update Custom Instructions so it doesn’t happen again.

How Projects work

  • Custom instructions. Overarching house rules — role, behaviour, output standards, knowledge-file routing, guardrails. Discipline rule: instructions here are general guidance only, NOT specific task workflows (those belong in skills).
  • Knowledge files. Documents always referenced in conversations — company info, client lists, ICPs, transcripts, financial breakdowns, templates. Includes the option to store executable prompts as files (e.g., the Client Intelligence Brief), iterated independently of behaviour rules.
  • Persistent chat history. Every conversation in the project files together for retrieval. Forms the long-term memory of decisions and prior work — “what did we decide about the Q2 launch last week?” returns a citation.
  • Sharing model. Project-scoped, not user-scoped — knowledge files, custom instructions, and chat history live inside the project workspace. ^[inferred]
  • Cowork bridge. Cowork’s + button → Import from project → search and select a claude.ai Chat Project → choose local folder. Knowledge files and custom instructions transfer; Cowork adds file creation, multi-step execution, dispatch from mobile.

When to use Projects vs Skills vs Cowork Projects

  • Reach for a Project when you want Claude to know about a specific business / client / workspace and accumulate history within it.
  • Reach for a Skill when you want a repeatable process that runs the same way every time, portable across surfaces.
  • Reach for a Cowork Project when the same context needs to also execute files, run multi-step tasks, and be controlled from your phone — the Cowork import is the bridge, not a replacement.
  • The flywheel: run a skill inside a project. The skill brings the general process; the project supplies the specific knowledge. Output flows back as a new knowledge file, compounding the project’s value over time.

Full comparison and decision-test table in skills-vs-projects-eliot-prince.

Try It

  1. Pick one recurring context you keep re-explaining to Claude — a client, a side hustle, a research thesis. Create a Project, load 3-5 knowledge files, write 5-10 lines of Custom Instructions (role + behaviour + output rules).
  2. Run the same prompt twice — once in a fresh chat, once inside the Project. Compare quality and the time spent re-explaining context. The delta is the Project’s leverage.
  3. Bring it into Cowork. Open Claude Desktop → Cowork → Projects → Import from project → pick the one you just built. Now the same brain can also write files and run multi-step tasks on your local folder.

Graph View

Backlinks