Claude Cowork: Set Up Your AI Working Partner in 30 Minutes

Mar 13, 2026 · 10 min read

You've used Claude before. You've written something detailed, got back something technically fine but completely generic, spent 20 minutes editing it to sound like you, and wondered why you bothered.

Then you tried again the next day. Same problem. Every session starts cold. The machine has zero memory of who you are, how you think, or what you're building.

So you compensate. You cram your professional identity into every prompt. Voice guidelines. Priorities. Standards. Every single time.

Claude Cowork solves this. And the setup takes less than 30 minutes.

What Claude Cowork Actually Does

Cowork is a tool built into the Claude Desktop app. You give it access to a folder on your computer. It reads your files, creates new ones, runs multi-step tasks, and delivers finished work directly to that folder.

No command line. No code. You describe what "done" looks like, and the machine plans, executes, and delivers.

The key difference from regular Claude chat: Cowork works with your actual files. You stop copying and pasting things in and out of a chat window. You delegate real work, walk away, and come back to a finished deliverable.

But here's the part most people miss in the setup. Cowork reads context at two levels: global instructions that load before every session, and project-level files that load when you point it at a specific folder. Set both, and every session starts with full context instead of a blank slate.

That context is the difference between a generic tool and a working partner.

The SIM Card: One File That Changes Everything

Think about your phone before you insert a SIM. It's a capable device. It connects to Wi-Fi, runs apps, takes photos. But it doesn't know who you are.

AI works the same way. Claude, out of the box, is powerful but generic. Every response starts from nothing because there's no context for you, your work, your voice, or your direction.

Install your SIM card and the experience transforms. You're working with a partner that knows your expertise, matches your communication style, understands your priorities, and produces work that sounds like it came from someone on your team.

Your SIM card lives in Cowork's global instructions. It loads automatically before every session, every project, every task. You set it once.

The difference shows up immediately. A 200-word prompt explaining your role, voice, format, audience, and quality bar every single time becomes ten words: "Create a client summary from the files in /project-x/notes. Match my usual format." Same output quality. A fraction of the effort.

How to Set Up Claude Cowork Step by Step

Step 1: Get Cowork Running (5 minutes)

Download the Claude Desktop app from claude.ai/download. You need a paid plan. Open the app and click the Cowork tab.

You should see a clean workspace. If you're prompted to select a folder, that comes next.

Step 2: Set Up Your Workspace (5 minutes)

Your AI workspace has two layers.

First, your global instructions. These live in the Claude Desktop settings (Settings > Cowork > Global Instructions). This is your SIM card. It loads automatically before every session, every project, every task. Set it once.

Second, your project folders. Create a main workspace folder on your computer, then one subfolder per project or area of work:

Claude-Workspace/
  Coaching-Programme/
    CLAUDE.md
    context/
    outputs/
  Client-Proposals/
    CLAUDE.md
    context/
    outputs/
  Content-Creation/
    CLAUDE.md
    context/
    outputs/

Each project gets its own CLAUDE.md file. This is a plain text file that Cowork reads automatically when you point it at that folder. No special setup required. The filename itself is the trigger.

The context/ folder holds persistent reference material for that project: your brand guidelines, your audience profile, your programme structure. Material that stays relevant across many sessions.

The outputs/ folder is where Claude saves deliverables. You tell it to do this in the CLAUDE.md (more on that in a moment).

When you need Claude to work on something specific, drop the raw material (a transcript, rough notes, a client brief) straight into the project folder. Once Claude has processed it, delete it or move it to an archive. This keeps the folder clean between sessions.

Important: Don't share your entire Documents directory. Keep the scope contained. Cowork has real read/write access to whatever you share.

Step 3a: Install Your SIM Card (10 minutes)

Go to Settings > Cowork > Global Instructions. This is where you define who you are across every project. It covers the Self dimension of the Amplify OS™ framework: your expertise, your voice, your values, your quality standards, your working preferences.

This loads before every session. You never type it again.

Include 2-3 samples of writing you're proud of. Add your anti-patterns: "never write like this." The more specific you are here, the less editing you do on the other side.

Use the Amplify OS™ Builder to create your SIM card.

Step 3b: Write Your First Project Brief (10 minutes)

Open a text editor and create a file called CLAUDE.md in one of your project folders. This is the operational context for this specific project. It covers the Systems and Strategy dimensions: what this project is, who's involved, what the goals are, and how Claude should work within it.

The filename CLAUDE.md is special. When you point Cowork at a folder containing a file with this exact name, it reads that file automatically before doing anything else. You don't need to mention it in your prompt. The name is the trigger.

A good CLAUDE.md is short. Twenty lines is plenty. Here's a working example:

# Client Onboarding Programme

## What this is
12-week group programme for coaches integrating AI into their practice.
Delivery via Zoom. 30 participants. Starts March 2026.

## Key context
See context/programme-structure.md for module breakdown
See context/participant-profile.md for audience details

## Working rules
- Read all files in /context before starting any task
- Save all deliverables to /outputs with descriptive filenames
- Match my voice from global instructions
- Ask clarifying questions before making assumptions
- Never delete files without explicit approval

The CLAUDE.md is a pointer, not a dump. It tells Claude what this project is and where to find the detail. The context/ folder holds the deeper reference material.

How This Maps to the Amplify OS™ Framework

If you've seen my work before, you'll recognise the architecture. The workspace you just built is the Amplify OS™ framework expressed as a folder structure:

Identity Core (Self) = Your global instructions. Who you are, your voice, your values. Set once. Loads every session.
Operational Context (Systems + Strategy) = Your CLAUDE.md and context/ folder per project. What this project is, how it works, where it's headed.
Task Context = The prompt you type and any files you drop in for this specific task. Use it, then clear it.

Three layers. Three concepts. Each one has a clear home. The SIM card lives in settings. The project brief lives in the folder. The task lives in your prompt.

Three Claude Cowork Workflows to Try Today

Don't just read about this. Pick one and run it now.

Workflow 1: The Voice Test

Once your global instructions are set, open a new Cowork session and type:

Read my context files. Then write a short LinkedIn post about a challenge I'd typically face in my work. Match my voice exactly.

Read the output. Does it sound like you? If it reads like a generic AI post, your SIM card needs more specificity. Add writing samples. Add your anti-patterns ("never write like this"). Run it again.

This single test tells you how strong your SIM card is.

Workflow 2: The Messy Folder

Find a folder on your computer with 30+ disorganised files. Point Cowork at it and ask:

Organise these files into sensible subfolders. Rename them with consistent naming conventions. Create a log of every change you make so I can review it.

What takes you an hour takes Cowork a few minutes. And because it has your global instructions, the naming conventions and folder logic should match how you actually work.

Workflow 3: From Raw Notes to Finished Output

Drop some rough notes, a meeting transcript, or a collection of client feedback into a project folder. Then:

Synthesise everything in this folder into a structured summary. Include key themes, decisions made, and action items. Save the result to /outputs.

When it's done, move or delete the raw files. The project folder stays clean. The deliverable is in outputs/ ready to use.

This is where the partnership becomes real. You provided the raw material. The machine shaped it. You review and refine. The output should be 80% there on the first pass if your SIM card is well-built.

Common Claude Cowork Problems (and How to Fix Them)

What Happens	What It Means	What to Do
Output is generic	SIM card is thin on voice	Add more writing samples and anti-patterns to your global instructions
Output misses the point	Task brief was vague	Be specific about what "done" looks like before asking
Technically right but wrong tone	Voice section needs work	Add examples of "never write like this" to your global instructions
Claude asks good questions before starting	Everything is working well	Let it run: this is the goal
Excellent on first pass	SIM card is dialled in	Celebrate it. This is what partnership looks like.

Making Claude Cowork a Daily System

One solved problem is useful. A repeatable workflow that runs every week without you thinking about it is a business advantage.

Three moves to get there:

Stop doing it manually. You just proved the machine can handle it. Let it.

Turn your task into a reusable brief. Save the prompt that worked. Structure your recurring prompts using the ACT framework to get consistent results. Set up the folder structure so files flow in and outputs flow out. If it's recurring, use Cowork's /schedule command to automate it.

Redirect your attention. What does this free you up to do? The client call. The strategic decision. The creative work that requires your full presence. Focus there.

The people who get the compound return from Claude Cowork refine their global instructions after every session and build one workflow at a time. Not ten. One. Get that one dialled in. Then add the next.

Start Here

Three things to do right now:

Install your SIM card. Use the Amplify OS™ Builder to create it. Paste the result into your global instructions.
Write one CLAUDE.md. Pick your most active project. Twenty lines. Point Cowork at the folder and run a task.
Refine after. Whatever the output got wrong, fix it in your SIM card or project brief. That's the compound return.

The setup takes an afternoon. The return shows up every day after that.

Your wisdom, your relationships, your judgment: those stay yours. The machine handles the production mechanics. That's the partnership.

Launch the Amplify OS™ Builder and start building your AI working partner.