The Claude Stack, Verified
A ten-panel "Claude: the complete AI operating system" poster has been making the rounds since May. Verdict after checking: the product skeleton is real — every major component it names ships today. The flesh around the skeleton is a mix of sound practice and invented ritual. This sheet separates the two, then gives the build order the poster never quite states.
01 — The real stackFive layers, all of them shipping
The Claude app (web, desktop, mobile), Cowork for agentic desktop work, Claude Code in the terminal and IDE, and Claude in Chrome. All real, all current products.
Projects hold persistent files and instructions per line of work; memory carries durable facts across chats; instruction files set standing rules. The poster's core insight is right: context compounds.
Skills: folder-based procedures loaded on demand. The poster's build recipe — one clear job, examples, rules, failure conditions — is genuinely good practice, whatever you think of "mini AI employees" as a metaphor.
MCP (Model Context Protocol) connects apps, databases, APIs and local files. Correctly named, correctly described. This is the layer most casual users never touch and the one that separates chat from operations.
Scheduled tasks for monitoring and follow-up, subagents for parallel work, computer use for screen-level operation. The poster calls scheduled tasks "the most understood AI use case" — ironically, while misusing the word misunderstood. The feature itself: real.
An operating system schedules everything on the machine. This is a product family with shared context — closer to a workbench than an OS. The metaphor sells; the workbench works.
02 — The folklore layerWhat to keep, what to drop
- "Create a ME.md memory file." Same pattern as the invented memory conventions in I-10: it works, because the model reads what you give it — but it's one author's ritual, not a product feature. The productized versions are memory and Project instructions. Use those first; add personal files if you like them.
- "Uploading 300 random files destroys output quality." The number is invented; the direction is right. Curated context beats bulk context — that's verifiable in practice and consistent with how context windows work. Curate aggressively; ignore the specific number.
- "Most people use Claude for answers. Elite users build systems." Engagement framing, but the underlying claim survives verification by observation: the compounding gains live in Projects, Skills and MCP — the system layers — not in better one-off prompts.
03 — The build orderFrom zero to system, honestly
- Write the standing instructions. Who you are, what you make, your voice, your never-list. One page. This is the highest-leverage hour.
- Make one Project per line of work and put the instructions plus five reference files in it. Not three hundred. Five good ones.
- Teach one Skill for the task you repeat weekly. One clear job, two examples, the failure conditions you've already hit.
- Connect one system via MCP — the calendar, the CRM, the folder — the single connection that removes the most copy-paste.
- Schedule one task that watches something you check manually. Then stop and use it all for a month before adding more.
04 — The ledgerTen claims, checked 2026-08-05
| Claim | Verdict | The record |
|---|---|---|
| Cowork — agentic desktop workspace | VERIFIED | Shipping product. |
| Projects — persistent context systems | VERIFIED | Core feature; poster describes it accurately. |
| Skills — reusable taught procedure | VERIFIED | Real; build recipe in the poster is sound. |
| Claude Code — automations, apps, infrastructure | VERIFIED | Real; "analyze → plan → build" mirrors documented plan-first practice. |
| MCP — connect apps, data, local files | VERIFIED | Correctly named and scoped. |
| Scheduled tasks for monitoring/follow-up | VERIFIED | Real feature. |
| Chrome extension / browser work | VERIFIED | Claude in Chrome ships. |
| ME.md / file-per-topic memory ritual | NUANCE | Works as personal convention; not a product mechanism. |
| "300 random files destroys quality" | NO SOURCE | Invented number; keep the curation principle, drop the statistic. |
| "Claude is a complete AI operating system" | NUANCE | Workbench, not OS. The composition is real; the category is marketing. |