Lesson 05 of 11 · Module 5
Claude Chat web and desktop
Teach Claude for long-context reasoning, projects, artifacts, research, files, connectors, skills and desktop workflows.
Built from aikickstart_sec05.md and Claude research/screenshot material
Claude is often best when the work needs long context, careful reasoning or document-rich output. The lesson should keep that strength tied to permission and evidence habits.
What to understand
- Claude Projects and Artifacts are production surfaces: give them clear source, review and export rules.
- Connector access should follow least privilege and a clear use case.
- Long context is not a substitute for source discipline.
Claude lesson readiness signals
The learner knows which files and links are allowed.
The final artifact, document or chart has a named reviewer.
External access starts read-only and narrow.
Step by step
Create a Claude project rule
Write project instructions for sources, tone, output and data limits.
HintKeep project instructions short enough to maintain.
Reference screens
Course screenshots and visual references for the lesson flow. Re-check the live product before paid delivery or public launch.
Create a Claude project setup card for a document-heavy workflow.
A Claude project brief with source and artifact rules.
Production prompt examples
Goal: [What outcome should exist by the end of this lesson?] Context: [Audience, account tier, device, constraints, and current workflow.] Inputs: [Screens, docs, local files, or example data allowed for this exercise.] Allowed actions: [Read, draft, compare, summarise, or inspect.] Ask before: [Connecting apps, writing to files, sending externally, spending quota, changing settings.] Output: [The exact worksheet, plan, checklist, or capture pack to produce.] Definition of done: [How the learner or facilitator checks the result.] Start by restating the plan in five bullets before executing.
Common mistakes to avoid
- Using long context as a dumping ground.
- Trusting a polished artifact without checking source and assumptions.
Key terms
- Artifact
- A structured output surface for documents, code, visuals or interactive material.
- Long context
- A large working memory window that still needs curated inputs.
Resources
Checkpoint