Tutorial: 20 Claude Code Concepts for Beginners

Most beginners only scratch the surface of Claude Code because the core terminology is never properly defined. This tutorial walks through all 20 foundational concepts — from workspace folders and CLAUDE.md to memory systems, artifacts, and Projects — so every advanced guide finally makes sense. The post also cross-references each concept against Anthropic's official documentation.


0

Every Core Claude Code Concept Explained for Normal People

Claude Code (called “Claude Cowork” throughout this video) packs 20 distinct features into a single desktop app — and most beginners never get past three of them because the terminology is never properly defined. This tutorial walks you through the full conceptual stack, from spinning up your first workspace folder to wiring up memory, projects, and automations. By the end, you’ll have the mental model that makes every advanced Claude Code tutorial finally land.

Overview: 20 core Claude Cowork concepts, from workspace setup to memory and scheduling
Overview: 20 core Claude Cowork concepts, from workspace setup to memory and scheduling
  1. Download the Claude Desktop App from Anthropic’s website. Both Mac and Windows builds are available. Install and open it before proceeding — everything here runs inside the desktop app, not the browser.

  2. Inside the app, locate the mode toggle at the top of the interface and switch from normal chat mode to Cowork mode. The interface shifts to a workspace-oriented layout with an active-tasks panel and a folder selector.

  3. Click the folder selector to choose an existing folder or create a new one. This folder becomes Claude’s workspace — every file Claude generates or reads will live here as a real file on disk (.docx, .html, .py, .csv), permanently accessible outside Claude.

Concept 1: Point Claude at a folder and it becomes a persistent workspace — real files, saved to disk
Concept 1: Point Claude at a folder and it becomes a persistent workspace — real files, saved to disk
  1. Create a file named CLAUDE.md inside your workspace folder. Claude reads it at the start of every session. Structure it with ## Who I am and ## Rules sections — always/never directives, tone preferences, project context — and Claude internalizes them before responding to anything.
Inside CLAUDE.md: define who you are, set Always/Never rules, and Claude internalizes them every session
Inside CLAUDE.md: define who you are, set Always/Never rules, and Claude internalizes them every session
  1. For instructions that span all Claude sessions, go to Settings → Cowork → Global Instructions and add your permanent identity there. CLAUDE.md is the project brain; Global Instructions are your system-wide identity across web, mobile, and chat.
Where to set Global Instructions: Settings → Cowork → Global Instructions field
Where to set Global Instructions: Settings → Cowork → Global Instructions field
  1. Let memory accumulate naturally across sessions. Claude saves important context as .md files inside your project. To force a save, tell it explicitly: “Save that to memory.” Over time this builds a persistent library of preferences, workflows, and corrections you only have to make once.
Concept 4: Memory.md files persist corrections across sessions — you fix Claude once, it remembers forever
Concept 4: Memory.md files persist corrections across sessions — you fix Claude once, it remembers forever
  1. Keep the 1-million-token context window in mind as you work. Every active session draws from that budget: CLAUDE.md, memory files, conversation history, uploaded files, and tool outputs all count toward it.

  2. Drop images, PDFs, and screenshots directly into any conversation. “Multimodal” means nothing more exotic than that — Claude reads them all natively.

  3. Enable web search when you need live data. The video states Claude’s knowledge cutoff is May 2025, so current pricing, recent model releases, and breaking news require web search to stay accurate.

Warning: this step may differ from current official documentation — see the verified version below.

  1. Switch to extended thinking for complex, multi-step problems. Responses take longer, but the quality improves measurably on hard reasoning tasks.

  2. Ask Claude to produce artifacts — HTML dashboards, interactive slideshows, and similar self-contained outputs — saved directly to your workspace folder as real files.

  3. Organize related conversations into Projects, each with its own memory library, CLAUDE.md, scheduled tasks, and output folder. Projects are the organizing layer that turns a collection of chats into a managed workflow.

A real Claude Cowork project: outputs, scheduled automations, and a library of memory files in one panel
A real Claude Cowork project: outputs, scheduled automations, and a library of memory files in one panel

How does this compare to the official docs?

The video delivers a practical mental model built from real use — Act 2 tests that model against Anthropic’s official Claude Code documentation to surface what’s changed, what’s missing, and what holds up even better than shown here.

Here’s What the Official Docs Show

The tutorial in Act 1 gives you a solid working mental model of Claude Code’s desktop experience — at the conceptual level, most of it holds up. The official docs add precision on two points that matter as your usage scales, and flag a handful of steps that need independent verification.

Step 1 — Download and install the desktop app

The video’s approach here matches the current docs exactly. Anthropic’s download page leads with “Chat, Claude Cowork, and Claude Code, all in one place” and offers a macOS download as the primary CTA; Windows is confirmed further down the page.

Official Claude download page confirming 'Chat, Claude Cowork, and Claude Code' are all available in one desktop app, with macOS download prominently featured.
📄 Official Claude download page confirming ‘Chat, Claude Cowork, and Claude Code’ are all available in one desktop app, with macOS download prominently featured.

Step 2 — Switch to Cowork/Code mode

The video’s approach here matches the current docs exactly — the desktop app contains Chat, Cowork, and Code tabs, and “Claude Cowork” is an official Anthropic product name. Worth noting: Claude Code and Claude Cowork are officially distinct products sharing the same desktop shell. Claude Code’s primary form is a terminal/IDE agent installed via curl; the desktop tab carries a BETA label. Both modes require a paid Pro or Max plan.

Claude download page distinguishing Claude Cowork surfaces (Desktop, Chrome, Excel, PowerPoint) from Claude Code environments (Desktop, Terminal, VS Code).
📄 Claude download page distinguishing Claude Cowork surfaces (Desktop, Chrome, Excel, PowerPoint) from Claude Code environments (Desktop, Terminal, VS Code).

Step 3 — Set a workspace folder

The video’s approach here matches the current docs exactly.

Claude Code on desktop (BETA) showing Chat, Cowork, and Code mode tabs alongside Projects and Sessions in the left sidebar.
📄 Claude Code on desktop (BETA) showing Chat, Cowork, and Code mode tabs alongside Projects and Sessions in the left sidebar.

Step 4 — Create CLAUDE.md

The video’s approach here matches the current docs exactly. One useful clarification: CLAUDE.md (written by you) and Auto memory (written by Claude) are two separate mechanisms. CLAUDE.md carries standards and project context; Auto memory captures build commands, debugging patterns, and preferences Claude discovers on its own.

Claude Code Docs 'How Claude remembers your project' page, showing CLAUDE.md files and Auto memory as the two distinct persistence mechanisms.
📄 Claude Code Docs ‘How Claude remembers your project’ page, showing CLAUDE.md files and Auto memory as the two distinct persistence mechanisms.

Step 5 — Set global instructions

As of April 12, 2026, the official docs show global CLAUDE.md files live at specific filesystem paths — on macOS: /Library/Application Support/ClaudeCode/CLAUDE.md — not under a “Settings → Cowork → Global Instructions” UI menu. The video shows a UI path not reflected in current documentation. Whether that UI writes to these paths behind the scenes is unconfirmed; for verified behavior, create the file directly at the documented path for your platform.

Claude Code Docs table showing CLAUDE.md file locations by scope: Managed policy paths for macOS, Linux, and Windows; project instructions at ./CLAUDE.md or ./.claude/CLAUDE.md.
📄 Claude Code Docs table showing CLAUDE.md file locations by scope: Managed policy paths for macOS, Linux, and Windows; project instructions at ./CLAUDE.md or ./.claude/CLAUDE.md.

Step 6 — Let memory accumulate across sessions

As of April 12, 2026, auto memory is fully automatic — the docs state “Claude learns from your corrections without manual effort.” The “save that to memory” trigger command the video demonstrates is not documented. Additionally, auto memory loads only the first 200 lines or 25KB per session, meaning a large accumulated memory file is silently truncated beyond that threshold. Plan your memory files accordingly.

Claude Code Docs comparison table: CLAUDE.md files (user-written, every session, project/user/org scope) vs. Auto memory (Claude-written, first 200 lines/25KB per session, per working tree).
📄 Claude Code Docs comparison table: CLAUDE.md files (user-written, every session, project/user/org scope) vs. Auto memory (Claude-written, first 200 lines/25KB per session, per working tree).

Steps 7–12 — Context window, multimodal inputs, web search, extended thinking, artifacts, Projects

No official documentation was found for these steps —
proceed using the video’s approach and verify independently.

  1. Claude Code by Anthropic | AI Coding Agent, Terminal, IDE — Official product page covering Claude Code’s installation command, supported environments, and Pro/Max plan requirements.
  2. Download Claude | Claude by Anthropic — Primary download page confirming Claude Cowork and Claude Code availability for macOS and Windows, including the surface/environment breakdown for each product.
  3. How Claude remembers your project – Claude Code Docs — Official memory documentation covering CLAUDE.md files, Auto memory, scope hierarchy, filesystem paths, and the 200-line/25KB per-session load limit.

Like it? Share with your friends!

0

What's Your Reaction?

hate hate
0
hate
confused confused
0
confused
fail fail
0
fail
fun fun
0
fun
geeky geeky
0
geeky
love love
0
love
lol lol
0
lol
omg omg
0
omg
win win
0
win

0 Comments

Your email address will not be published. Required fields are marked *