The argument in one line.
After learning these 20 concepts in order from workspace folders to sub-agents, every Claude Cowork tutorial will finally make sense because you'll understand the foundational building blocks that all advanced techniques rely on.
Read if. Skip if.
- A beginner exploring Claude desktop for the first time who feels lost by tutorials that assume you know what workspaces, skills, and sub-agents already mean.
- Someone building AI workflows who wants a foundational mental model of all 20 Cowork concepts before diving into advanced implementation.
- A non-technical person or small business owner considering Claude Cowork but intimidated by the jargon and feature density.
- You already use Claude Cowork regularly and are looking for advanced patterns, optimization strategies, or edge-case troubleshooting.
- You need instruction on connecting Cowork to external APIs or databases — this is a concept glossary, not a systems integration guide.
The full version, fast.
Claude Cowork's twenty core concepts stack into a coherent system once you stop treating them as jargon and walk them from simplest to most powerful. Start with the workspace folder Claude reads and writes into, then layer a project-scoped Claude.md and account-wide global instructions to define behavior, memory to persist what matters across sessions, and the context window as the desk where it all sits. Build outward through multimodal inputs, web search, extended thinking, and artifacts that produce real dashboards instead of paragraphs. The leverage compounds at the top: projects isolate brains, skills encode repeatable workflows triggered by slash commands, plugins bundle skills, connectors wire in your actual apps, Chrome and computer use cover whatever lacks an API, scheduled tasks replace Zapier, dispatch controls everything from your phone, and sub-agents run those skills in
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open + promise
Names the overwhelm (MCPs, skills, sub-agents) and promises 20 concepts simple-to-advanced.

02 · #1 Workspace Folder
Where Claude's files live on your computer; create a folder, point Claude at it.

03 · #2 Claude.md
A markdown file that defines how Claude operates; loaded at the start of every session.

04 · #3 Global Instructions
Permanent identity across all Claude surfaces, not project-scoped like Claude.md.

05 · #4 Memory
Markdown files Claude builds over time; tell it 'save that to memory' to keep context.

06 · #5 Context Window
1M tokens — the 'desk' for each conversation. When full, older context drops.
07 · #6 Multimodal
What Claude can see: images, PDFs, text, screenshots. Not video yet.
08 · #7 Web Search
Live web lookup since Claude's knowledge cutoff is May 2025.
09 · #8 Extended Thinking
Claude takes longer on hard questions; better answers at the cost of latency.
10 · #9 Artifacts
Non-text outputs (HTML dashboards, slides, charts) rendered inside Claude.
11 · #10 Projects
Separate brains in one workspace — each project has its own memory, instructions, scheduled tasks, files.
12 · #11 Bash Tool
How Claude runs code itself instead of handing you commands to copy.
13 · #12 Skills
One command that triggers a whole workflow — Brock demos his morning briefing skill.
14 · #13 Slash Commands
Keywords that trigger skills — e.g. /morning-briefing.
15 · #14 Plugins
Bundles of skills you can share or upload as a zip — easier than re-creating 50 skills.
16 · #15 Connectors
Hooks Claude into your apps (Gmail, Calendar, Slack, etc); MCP servers like Zapier MCP expand the catalog.
17 · #16 Chrome Extension
Claude controls your browser to click, fill forms, book things — one step below connectors.
18 · #17 Computer Use
Claude takes over your whole computer (not just browser) — drag files, use apps. Slow but powerful.
19 · #18 Scheduled Tasks
Cron-like automations built on skills — Brock's daily wrap-up auto-runs every evening.
20 · #19 Dispatch Mode
Control your desktop Claude from your phone — trigger skills on the go.
21 · #20 Sub-Agents
Parallel workers for complex tasks — research / financials / narrative / slides in parallel.
22 · Outro + CTA
Subscribe + join School community for 50+ weekly-updated skills.
Lines worth screenshotting.
- Claude Cowork's 20 concepts span from workspace folders to sub-agents, and understanding them in order from simplest to most powerful is the fastest path to fluency.
- A CLAUDE.md file is the project brain — loaded at the start of every session, it defines how the AI operates within a specific workspace.
- Global instructions differ from CLAUDE.md in scope: they apply across all of Claude (chat, Cowork, Code), while CLAUDE.md is folder-specific.
- Selecting multiple folders inside Cowork expands the AI's file access as complexity grows, rather than requiring a rebuild of the workspace.
- The most common source of overwhelm in Claude Cowork is learning concepts out of order, making earlier ideas seem more complex than they are.
- Sub-agents are the most powerful Cowork feature because they enable parallel task execution, but they are only useful after the foundational concepts are internalized.
- Skills inside Cowork are reusable instruction sets that tell the AI how to perform a specific task consistently without re-prompting from scratch.
- MCPs (Model Context Protocol connectors) extend what Cowork can access — web browsers, APIs, external tools — turning a text interface into an action-taking agent.
- A beginner who understands the workspace, CLAUDE.md, and global instructions can extract 80% of the value from Cowork before ever touching skills or MCPs.
- Connectors inside Claude Cowork translate between the sandbox and external services, which is why the Higgsfield connector was such a significant release.
- Treating each Claude project as a separate AI employee with its own CLAUDE.md and skills prevents context bleed between unrelated workflows.
- A numbered glossary format is the right pedagogy for Cowork onboarding because it gives beginners a clear map of what they do not yet know.
Steal the numbered-glossary format.
Pick a tool ecosystem with too many confusing words, number all 20, walk simplest-to-advanced, branded slide for each — own the SEO term forever.
- Pick a tool ecosystem where beginners feel lost (Supabase, Trigger.dev, $6 Stack, MCN+, Claude Code itself) and list every confusing concept on a whiteboard.
- Sort 1-20 from absolute basics to most powerful — never re-order, never skip — the numbering itself is the promise.
- Build ONE branded slide template ('CONCEPT 02 — TITLE — one-line tagline') and reuse it 20 times. The repetition is the brand.
- Pair every concept slide with a 30-90 second live demo inside the actual product UI. Glossary alone is content; glossary plus demo is a tutorial.
- Repeat one comfort-line across the video ('I was in your exact same shoes') as a re-hook between concepts to reset attention.
- End on the most-mind-blowing feature (sub-agents) — never bury the wow at concept #7.
- Soft-CTA your paid offer 4+ times by weaving it into demos ('this skill is in my school community'). No hard pitch block needed.
- Steal candidates: 'Every $6 Stack concept', 'Every MCN concept for creators', 'Every Trigger.dev concept', 'Every JoeFlow concept'.
Terms worth knowing.
- Claude Cowork
- A GUI-based agentic feature inside the Claude desktop app that lets non-developers give Claude access to files, the web, and external tools to complete multi-step tasks autonomously.
- workspace folder
- A folder on your computer that you connect to Claude Cowork as the root directory — all files Claude reads, writes, and creates during sessions live here.
- Claude skill
- A Markdown file containing packaged instructions for a specific task that Claude Cowork can invoke automatically when a relevant request is made, without re-prompting each time.
- MCP (Model Context Protocol)
- An open standard that lets Claude connect to external data sources and tools — such as databases, APIs, and services — through a unified interface, extending what tasks it can perform.
- connector
- A pre-built MCP integration that links Claude to a specific external service (like Google Drive, Notion, or Slack), allowing Claude to read and act on data from that service.
- sub-agent
- A separate Claude instance that a main Claude session can spawn to handle a specific sub-task in parallel, with results returned to the orchestrating session when complete.
- AI employee
- Informal term for a configured Claude Cowork session or agent set up to handle a specific recurring business task autonomously — a delegation metaphor rather than a literal product feature.
- CLAUDE.md
- A Markdown configuration file in the workspace folder that acts as persistent instructions Claude reads at the start of every session, defining its role, rules, and available resources.
Things they pointed at.
Lines you could clip.
“Skills, MCPs, sub agents, connectors — everyone throws out these words like you're supposed to already know what they mean.”
“Every tutorial you watch from here on out will finally click.”
“One command that can trigger entire workflows for you.”
“I've replaced n8n and different automation platforms with this.”
“Parallel workers that are working at the same time.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Brock opens with the pain — you've watched the tutorials, you still don't know what an MCP or a sub-agent is. He promises that by the end of these 31 minutes, every Claude video you ever watch again will finally click. The bait is comprehensiveness: not one concept, all 20, simplest to most powerful, in order.
Named ideas worth stealing.
20 Claude Cowork Concepts (simple to advanced)
- Workspace Folder
- Claude.md
- Global Instructions
- Memory
- Context Window
- Multimodal
- Web Search
- Extended Thinking
- Artifacts
- Projects
- Bash Tool
- Skills
- Slash Commands
- Plugins
- Connectors
- Chrome Extension
- Computer Use
- Scheduled Tasks
- Dispatch Mode
- Sub-Agents
Numbered glossary that walks beginners from filesystem basics to multi-agent orchestration.
Claude.md vs Global Instructions (project brain vs permanent identity)
Project-scoped instructions live in the workspace folder (Claude.md); identity that follows you everywhere lives in Global Instructions. Clear separation kills 90% of confusion.
Connectors > Browser Use > Computer Use (hierarchy of access)
- Connectors (native API)
- Browser/Chrome extension
- Computer Use (full desktop)
Always reach for the highest layer first — connectors are fastest and most reliable, computer use is slowest and most error-prone.
How they asked for the click.
“If you want all 50 plus skills I use every single day, there is a link in the description below to join my school community.”
soft, value-stacked — referenced 4+ times throughout the video. No hard pitch block. Description holds the bit.ly to the paid course and DWY offer too.










































































