daBongo LMS AI Training Courses

Lesson Content

The re-explanation tax.

Every time you start a new conversation for an ongoing project – a job search, a business plan, a research project, a writing project, a job role – you pay a re-explanation tax. You re-paste the background document. You re-explain the constraints. You re-describe the audience. You re-establish what has already been decided.

For short, one-off tasks, this is fine. For ongoing work that spans days, weeks, or months, it is a significant and unnecessary friction.

Projects is the feature that eliminates this tax.

What Projects does.

Projects (verify current availability in your plan and interface) is a persistent workspace where you can:

• Store documents, files, and context that Claude can reference across all conversations within the Project
• Maintain a consistent set of instructions specific to that project (like a project-level Custom Instructions)
• Access a history of all conversations within the Project in one organized place
• Build on prior work without starting from scratch each session

Think of a Project as a dedicated workspace for a specific ongoing task – like having a dedicated desk with all your materials already laid out, rather than clearing and resetting a shared table for every work session.

How Projects differs from Custom Instructions.

Custom Instructions apply to all your conversations globally – they are your general working preferences. Projects are specific to a single, defined work context. You might have Custom Instructions that reflect your general communication style, plus a Project for your job search, another for a business you are building, and another for a course you are taking.

When you work inside a Project, both your Custom Instructions and the Project's specific context are active.

What to put in a Project.

Good Project content includes:

• A background document or brief explaining what the project is about
• Key decisions already made (so Claude does not re-suggest what has been decided)
• Reference documents Claude should be able to draw on (style guides, requirements, outlines)
• Project-specific instructions: "This project is for [specific audience]. Always [specific requirement]. Never [specific constraint]."
• Relevant past output: documents already created that Claude should be aware of

Do not put: sensitive personal data, passwords, confidential client data without verifying your platform's data handling, or excessive irrelevant material that dilutes Claude's focus.

Practical use cases for Projects.

• Job search: Background on your experience, target role descriptions, tailored resume versions, notes from interviews
• Business plan: The plan draft, key decisions made, financial assumptions, target market research
• Research project: Research question, sources gathered, synthesis notes, outline
• Content strategy: Brand voice guide, content calendar, past published pieces for consistency
• Learning project: Learning plan, notes from sessions, practice questions answered
• Client work (anonymized): Project brief, key requirements, past deliverables for consistency

Verifying current feature availability.

Projects may be available on certain plan tiers and not others. The feature set – how many Projects you can have, how much context you can store, whether file uploads are supported within Projects – varies and changes with product updates. Verify current availability and limits directly in your Claude interface or account settings before building critical workflows around this feature.