The bait, then the rug-pull.
A difficulty slider on screen -- min on the left, max on the right -- is the first thing you see. It is a quiet bet that most people who opened this video already felt the max end. What follows is a deliberate dismantling of that fear: a 31-minute build-along that leaves you with a five-part workspace that runs morning briefings while you sleep.
Where the time goes.
01 · Intro + free prompt pack
Difficulty slider pattern interrupt. Promises free Cowork OS prompt pack and build-alongside structure.
02 · Section 1: The Body
Workspace folder as the physical home for Claude. One folder per project area. Prompt auto-builds the subfolder structure with CLAUDE.md and Memory MD per project.
03 · Section 2: The Brain
CLAUDE.md is the identity file Claude loads every session. Good vs. bad examples. Memory MD grows from use. AquaVoice dictation hack for faster setup.
04 · Section 3: The Hands
Native connectors for Gmail, Google Calendar, and 100+ apps. Zapier MCP for apps not on the native list. Live demo: inbox triage and calendar summary in one prompt.
05 · Section 4: Skills
15 free skills on Gumroad. Budget dashboard live demo. Build-your-own skill by teaching Claude your email voice from sent Gmail history. Skills dashboard live artifact.
06 · Section 5: Scheduled Tasks
Morning briefing runs at 7AM daily -- inbox, calendar, AI news, HTML dashboard, Slack DM. Weekly skill audit automation. Token cost warning. Keep-awake toggle caveat.
Visual structure at a glance.
Named ideas worth stealing.
Cowork OS: Five-Part System
- The Body (workspace folder)
- The Brain (CLAUDE.md + Memory MD)
- The Hands (connectors + MCP)
- Skills (saved workflows)
- Scheduled Tasks (automations)
A body metaphor for structuring a Claude workspace: each part has a distinct job, and the system only fully functions when all five are in place.
Good vs. Bad CLAUDE.md
- Bad: Be helpful and professional
- Bad: Write in a good tone
- Good: Short direct answers no fillers
- Good: Never use em dashes
- Good: Lead with benefits not technical specs
Specificity is the only thing that makes a CLAUDE.md file actually change behavior. Vague instructions are indistinguishable from no instructions.
Lines you could clip.
"Set it up the right way, and it becomes a full system that knows you, works inside your real files, and runs your work in the background."
"Think of this as your AI employee. You really want to give it good instructions."
"A skill is basically a job that we can teach Claude to do one single time, and it always knows how to run this specific workflow whenever we trigger it."
Things they pointed at.
How they asked for the click.
"If you want more videos like this, subscribe. And if you want to dive even deeper, join my School community."
Standard subscribe plus paid community pitch. School community is where the 50-skill pack lives. Low friction on the free prompts, soft upsell at the end.
Word for word.
Five components that turn Claude into a system.
Claude Code stays a cluttered chat tool until you wire five components together -- and each one builds on the last.
- The workspace folder is the foundation: Claude reads and writes real files there, so how you organize the folder is how you organize its context. One folder per project area prevents client work bleeding into personal notes.
- A CLAUDE.md file is an employee handbook, not a greeting card. Vague rules like be professional do nothing. Specific rules like never use em dashes, lead with benefits, short sentences change every response immediately.
- Memory grows from use, not setup. You do not fill out a memory file upfront -- you just say remember this and Claude appends it. The only maintenance it needs is periodic pruning when old context becomes stale.
- Connectors turn Claude into an operator. Linking Gmail and Google Calendar takes two minutes and lets Claude draft replies, summarize your inbox, and create calendar events without you copying and pasting anything.
- Skills are the compounding unit. A skill saved once runs on demand forever. The value is not the first use but the hundredth, which is why a skills dashboard to track what you have built is worth creating early.
- Scheduled tasks are the multiplier. A morning briefing that pulls your inbox, calendar, and AI headlines into an HTML dashboard and sends it to Slack at 7AM costs nothing to run after the first setup and it runs whether you are working or asleep.
- Token cost is the one real constraint on automations. Complex daily tasks burn credits; running a scheduled task too frequently will drain an account. Match cadence to actual need.
- The keep-awake toggle is the most overlooked setting: scheduled tasks only fire when the computer is on. If your machine sleeps at night, morning automations will not run unless you enable keep-awake.































































