Identity · Outputs · Templates
The 3-folder setup
Three folders Claude reads every session so you stop re-explaining yourself
Browser Claude forgets every chat. Cowork reads files from disk every time you open it. You set up three folders (who you are, what you ship, what you reuse), drop in three ABOUT ME files, and point Global Instructions at them once. From then on every Cowork session starts with full context. No briefing prompt at the top of every conversation.
Worth knowing:Once your three files are in place, you stop pasting context into prompts. Most prompts get shorter. Claude's first reply is closer to what you actually wanted, every time.
Browser-Claude users tired of re-briefingAnyone who shares Claude with a teammateCreators with a consistent voice or POV
Start Lesson 1 →One worked workflow, end to end
Cowork Projects
Scoped memory that remembers within a project and forgets across boundaries
A Cowork Project is a workspace with its own files, its own context, and its own memory of what you discussed. Different from Browser Projects (which sync across devices), Cowork Projects live on your machine and execute work locally. This lesson walks you through one workflow end to end (a recurring newsletter), then names the other three you can adapt the same pattern to.
Worth knowing:Cowork Projects forget across boundaries on purpose. The newsletter project doesn't accidentally read your client research. Different work, different memory.
Anyone with recurring work (newsletters, reports, weekly reviews)Freelancers juggling 3+ clients in ClaudePeople burned by context bleed in long chats
Start Lesson 2 →Build once, run anywhere
Skills + Scheduled Tasks
Reusable artifacts that run when you call them or on a clock
A Skill is a packaged prompt + instructions Claude can call by name (or auto-fire from natural language). You build one with Claude itself (no code), test it, then it shows up across every Cowork session. Scheduled Tasks run a Skill on a clock. Your weekly report at 8am Monday, your competitor scan at midnight Sunday. This lesson builds one of each.
Worth knowing:The Skill Creator is itself a Skill. You describe what you want in plain language, it interviews you, then writes the Skill. Building Skills is the easiest part once the first one exists.
Anyone with a prompt they paste more than weeklyOperators with a repeatable workflowAnyone who wants Claude doing work overnight
Start Lesson 3 →Build your text-file twin
Voice extraction
A voice file that lets Claude write in your voice, not the default
Default Claude writes like Default Claude. A voice file fixes that. You run a long structured interview with yourself (taste, references, what you would never say, what you say all the time), Claude compiles it into a portable voice document, and that file goes into your identity folder. Every piece of writing Claude produces from that point reads like you wrote it. Includes the security note Ruben skipped: where NOT to store this file.
Worth knowing:The voice file is also a hiring document, a brand brief, and a positioning statement in disguise. Once it exists, you reuse it for everything that needs to sound like you.
Writers, founders, and anyone with a public voiceAnyone whose Claude output sounds genericSolo operators whose voice IS the product
Start Lesson 4 →