Resources

All entries below were fetched and verified on 2026-08-07. Feature availability on Claude changes often; re-verify anything plan-gated before a course build locks screenshots.

Knowledge — Claude features (primary, for module accuracy)

• Understanding Claude's personalization features — Claude Help Center The authoritative map of the three persistence layers. Confirms the current UI name is "Instructions for Claude" (Settings → Instructions for Claude), not "custom instructions." Also confirms free accounts now get up to five projects. Use for: Module 6.

• Use Claude's chat search and memory to build on previous context — Claude Help Center Memory is entry-based and categorized, written and updated in real time during chats rather than on a schedule. Available on free, Pro and Max. Controls: Settings → Memory → "Generate memory from chats"; pause vs. reset (reset is irreversible); incognito chats via the ghost icon. Use for: Module 6, and the privacy-anxiety section specifically.

• Import and export your memory from Claude — Claude Help Center Use for: the "memory is inspectable and portable" confidence move in Module 6.

• What are projects? — Claude Help Center · How can I create and manage projects? Project knowledge lives in the right-hand panel and applies across every chat in the project. Paid plans scale large knowledge bases via retrieval when approaching context limits. Use for: Module 6 hands-on.

• What are artifacts and how do I use them? — Claude Help Center Artifacts trigger on content that is substantial (~15+ lines) and self-contained. Forking works by editing an earlier message to branch the conversation. Use for: Module 7.

• Publish and share artifacts — Claude Help Center Free/Pro/Max use Publish for a public link; Team/Enterprise use Share for org-internal. Viewers need no account for basic functionality. Confirms the Pro-learner path. Use for: Module 7.

• Use artifacts to visualize and create AI apps without writing a line of code — Claude Help Center The no-code interactive artifact path. Use for: Module 7's stretch exercise.

• Use Google Workspace connectors — Claude Help Center Gmail/Calendar/Drive. Claude accesses data only on explicit request. Docs pulled from Drive sync to the latest version. Pro users self-authenticate; the org-admin enable step is Team/Enterprise only — this is why the connector exercise works for our audience. Use for: Module 7.

• Use connectors to extend Claude's capabilities — Claude Help Center General connector setup and permissions flow. Use for: Module 7 screenshots.

• Change the model, effort, and thinking settings — Claude Help Center Corrects an assumption made in rev. 1: this is three independent controls, not a model picker. Model (click the model name, then "More models"); effort — low/medium stretch usage on routine work, high is the quality/speed balance, xhigh is for long-running coding and agentic tasks, max is deepest reasoning and slowest; and thinking, a separate toggle that combines freely with any effort level. Use for: Module 7's dials section. Note xhigh is deliberately excluded from the course as out of scope.

Knowledge — pedagogy and framing

• AI Fluency: Framework and Foundations — Anthropic Free 12-module course for non-technical users, built with Prof. Joseph Feller (University College Cork) and Prof. Rick Dakan (Ringling College). Its 4D framework — Delegation, Description, Discernment, Diligence — is the closest thing to a canonical vocabulary in this space, and the "Description–Discernment loop" is exactly our Module 3 → Module 4 handoff. Use for: borrowing vocabulary learners may meet elsewhere, and as the recommended companion resource.

• Prompting best practices — Claude Platform Docs Written for developers, but the technique ordering (be specific → give examples → structure the input) is the evidence base for Module 3's component list. Mine it; do not assign it to learners.

• Prompt engineering best practices for 2026 — Anthropic blog More accessible than the docs. Use for: Module 3's recommended reading.

Wisdom (Communities)

• r/ClaudeAI — active, Claude-specific, heavy on real workflow reports and current-feature gotchas. Use for: learners wanting to see how others structure Projects; also the best early-warning signal for UI changes that will rot course screenshots.
• Anthropic Discord — official; good for feature questions where the help center is ambiguous.
• Not yet vetted for the course author's own practice: an instructional-design community (e.g. r/instructionaldesign) for async-completion and assessment-design critique.

Knowledge — sources adopted while building the lessons

Each verified live on 2026-08-07 by the agent that adopted it.

• SIFT: The Four Moves — Mike Caulfield
  Stop, Investigate the source, Find better coverage, Trace claims to the original context. Lesson 5's primary source, and it substantially closes the gap recorded below. “Trace claims to the original context” and “investigate the source” map exactly onto that lesson's two independent columns — traceability and source quality. Written for a general audience and about evidence rather than about models, so it does not date as models improve.
• Signs of introspection in large language models — Anthropic
  Lesson 4's primary source, backing the diagnosis-as-hypothesis rule: Claude's account of why it produced something is not a log of what happened. Companion: Reasoning models don't always say what they think.
• Effective context engineering for AI agents — Anthropic Engineering
  Lesson 2's primary source. Learners should stop at the agentic-search section — beyond that is out of scope for this course.
• Best practices for prompt engineering for 2026 — Anthropic
  Lesson 3's primary source. Note it advises phrasing constraints positively where possible, which cuts against the “non-goals” component; Lesson 3 surfaces that tension in a sidenote rather than suppressing either side.
• Define success criteria and build evaluations — Claude Platform Docs
  Lesson 8's primary source, scoped to the first half only — everything from the code samples on is API material and out of scope.

Gaps

• No high-trust plain-language source on hallucination mechanics — substantially closed. SIFT (above) covers the skill this course actually needs, and Module 5's reframe from verification to evidence means the module now leans on a question anyone can apply rather than on an authored account of mechanism. What remains genuinely uncited is the one-paragraph explanation of why fabrication happens at all; that is still authored prose, and still the paragraph most worth a second reader.
• No published completion-rate data for self-paced AI-literacy courses to calibrate the assessment thresholds against. Thresholds below are reasoned, not evidence-based.
• Screenshots: no stable archival source. Assume UI drift and plan re-capture cycles.