Brooke Wright
Brooke Wright · @wright_mode
Free Guide

My full Claude Cowork setup guide

The five steps I actually run, with the three prompts that do the hard bits for you — the interview that writes your global instructions, the one that builds your voice profile, and the one that builds your first automation.

ADHD-friendly No code required Beginner → Advanced Built by Brooke
Something went wrong. Please try again.

No spam. Unsubscribe anytime.

The 5-step setup, with the three prompts that do the work for you Jump to the 5 steps → See all options
Wright Mode — Free Resource

My full Claude Cowork setup guide

The five steps that take Claude from a generic chatbot to something that knows you, is plugged into your tools, writes in your voice and runs jobs on a schedule. Three copy-paste prompts do most of the work.

5 steps, about an hour 3 copy-paste prompts No code Desktop app, paid plan Full reference underneath

What's inside

This is the whole thing — the setup I actually run. Five steps, three copy-paste prompts, about an hour if you do it properly. Do them in order; each one feeds the next. Everything after this section is the deeper reference if you want it.

What you'll have at the end

A Claude that knows who you are, is connected to your real tools, writes in your voice instead of a robot's, and has at least one job running on a schedule without you asking.

1

Use Cowork, not chat

This is the step people skip, and it's the one that changes everything. Chat talks about your work. Cowork does it — it opens a real folder on your computer, reads and edits the actual files in it, and connects to your tools. Open the Claude desktop app, click the Cowork tab, tick Work in a folder, and point it at one folder. Start with a low-stakes one, not your whole Documents directory.

Why the folder matters more than it sounds

A chat forgets your files the second you close it. A folder is a workspace that persists — Claude can put things in it, come back to them tomorrow, and build on what's already there. That's the difference between a clever assistant and one that gets work done.

2

Tell it who you are

Out of the box Claude knows nothing about you, so everything it produces is generic. Don't try to write your own instructions from a blank page — that's hard, and you'll forget half of it. Run the prompt below in Cowork instead. It interviews you, then writes the instructions for you. When it hands you the final block, copy it into Settings → personalisation → your instructions so it applies to every chat from then on, not just this one.

I want you to write my global instructions — the standing context you'll have about me in every future conversation. Don't write them yet. Interview me first. Ask me one question at a time, and wait for my answer before the next one. Cover: what my business actually does and who it serves, what I spend most of my week doing, what I'm technical about and what I'm genuinely not, the tools I use daily, how I like to be spoken to, what I never want you to do, and the mistakes an assistant new to me would make in the first week. Go deeper when an answer is vague. If I say "I help business owners", ask which ones, at what stage, with what problem. Don't accept the first version of anything. Ask follow-ups until you could write my instructions without guessing at anything — usually around 10 to 15 questions. Then say "I've got enough" and write them. Format the final version as a clean block I can copy straight into Claude's settings. Write it in second person addressed to you ("Brooke runs...", "Always...", "Never..."). Keep it under 500 words — long instructions get skimmed. No preamble, no explanation, just the block.

Answer honestly, not impressively

This is the highest-leverage hour in the whole setup. If you tell it you're a strategic visionary it will write like one at you forever. Tell it you're a one-woman business who hates spreadsheets and it will actually be useful.

3

Connect your tools

Go to Settings → customise → capabilities. That's where you switch on the connections — Gmail, Google Drive, Google Calendar, Notion and the rest are sitting right there. Turn on the ones you actually live in, not all of them. Each one you enable is another place Claude can read from and write to without you copying anything across.

Your tool isn't in the list?

Search "[tool name] MCP connector". MCP is the open standard that lets any app plug into Claude, and most tools worth using now have one — built by the company or by someone in the community. If nothing comes up, that tool genuinely isn't connectable yet. Move on rather than fighting it.

Turn on what you'll use, not everything

Every connection is real access to a real account. Gmail on means it can read your inbox. Start with two or three you'd be comfortable explaining to a client, get used to what it does with them, and add more when you actually need them.

4

Build it a voice profile

Telling Claude to "write like me" does nothing — it has no idea what that means. Show it instead. Gather 10 to 20 samples of your real writing: sent emails, LinkedIn posts, captions, even text messages to a friend. Variety beats volume here. A polished newsletter and a fired-off text teach it two different registers, and the gap between them is where your actual voice lives. Drop them all in your Cowork folder as one file or several, then run this.

In this folder are samples of my real writing — emails, posts, messages. Read all of them, then build me a voice profile. Analyse, don't compliment. I want: 1. Sentence rhythm. How long, how varied, where I break the rules. 2. My actual vocabulary — the words and phrases I reach for repeatedly. Quote real examples from the samples. 3. How I open. How I close. Do these change between formal and casual samples? 4. Punctuation habits, including the ones that are technically wrong. 5. What I never do. This matters as much as what I do. 6. How the tone shifts between contexts, and what stays constant underneath. Then write it up as a voice profile I can save and reuse — specific enough that another writer could produce a passable draft from it. No vague adjectives like "warm" or "conversational" unless you immediately show me the exact sentence pattern that creates that effect. Finish with the three tells that would make something obviously NOT written by me. Save it as voice-profile.md in this folder.

Then actually test it

Ask it to write something short using the profile — a reply to a real email you've got sitting there. Read it out loud. If it sounds like you, you're done. If it doesn't, tell Claude exactly which bit is off and have it update the file. Two rounds of that and it's usually right.

5

Have it build your first automation

Now it knows you, it's connected to your tools, and it writes like you. This last prompt makes it review all of that and work out what's worth automating — then build it. Don't guess at what to automate yourself. It's read more about your week than you've consciously thought about it.

Review everything you now know about me — my global instructions, my voice profile, the files in this folder, and the tools you're connected to. Before you suggest anything, ask me whatever you still need to know: what eats my week, what I keep forgetting, what I do every Monday that I resent, what has to happen on a schedule whether I'm on top of things or not. Then give me the three highest-leverage scheduled tasks you could run for me. For each one: what it does, when it runs, which of my connected tools it needs, roughly how much time it saves me a week, and honestly what could go wrong with it. Rank them by time saved divided by risk — I want the boring reliable one first, not the impressive fragile one. Wait for me to pick. Once I choose, build it properly: set up the scheduled task, and write any skill it needs to run so it works the same way every time rather than being reinvented on each run. Save the skills in this folder so I can read and edit them. When it's built, tell me in plain English what will happen, when it will first run, and exactly how I turn it off.

Start it on something boring

Your first scheduled task should be something you genuinely wouldn't mind getting wrong for a week — a Monday summary, a folder tidy, a "what's due this week" digest. Watch it run a few times before you hand it anything that touches a client. The desktop app has to be open and your computer awake for a scheduled task to fire, so pick a time you're normally at your desk.

If you only do two of the five

Do steps 2 and 4. The global instructions and the voice profile are what turn Claude from a generic chatbot into something that sounds like it works for you. Connections and automations are the payoff, but those two are the foundation.


Claude isn't one tool — it's three. Each mode is designed for a different way of working, and picking the right one determines whether you're doing the work yourself or getting it done for you.

💬 Chat

The conversation mode. Ask questions, get answers.

  • Works on web, mobile, and desktop
  • You manually upload files and copy-paste outputs
  • Great for ideation, drafts, and quick questions
  • Free / Pro $20/mo / Max $100/mo

🤝 Cowork

The assistant mode. You brief, Claude executes.

  • Desktop app only (Mac + Windows)
  • Direct access to your local files
  • Delivers finished outputs — Excel, PowerPoint, Word, PDFs
  • Parallel sub-agents, 38+ connectors, browser automation
  • Pro, Max, Team & Enterprise

⚡ Code

The developer tool. Terminal-based powerhouse.

  • Full computer control, GitHub integration
  • For developers comfortable with the command line
  • Unlimited power, no GUI hand-holding
  • Pro, Max, Team & Enterprise
Feature Chat Cowork Code
Access your files – ✓ ✓
Works autonomously – ✓ ✓
Parallel sub-tasks – ✓ ✓
No technical skills needed ✓ ✓ –
Creates files in folders – ✓ ✓
Browse the web ✓ ✓ ✓
Plugins / Skills – ✓ ✓
Mobile access ✓ Dispatch –
Scheduled tasks – ✓ –

The bottom line

Use Chat when you need answers, ideas, or content inside a conversation.

Use Cowork when you want finished files delivered to your computer — without touching a terminal.

Use Code when you're a developer who wants full control.

Watch the full walkthrough

Claude Cowork: from beginner to expert in 18 minutes


If you can describe what you want in plain English, you already have all the skills you need.

You need

Claude Desktop app (Mac or Windows) — free to download from claude.com/download.

A paid plan — Pro ($20/mo), Max ($100/mo), Team, or Enterprise.

You don't need

A terminal, coding knowledge, or Claude Code. Cowork is fully point-and-click. If you can use a word processor, you can use this.

1

Download Claude Desktop

Head to claude.com/download and grab the app for Mac or Windows. The download is free, but you'll need a paid plan to access Cowork mode.

2

Find the mode selector

Three tabs along the top: Chat, Cowork, and Code. Click Cowork.

3

Tick "Work in a folder"

Select a folder on your computer and grant Claude read/edit permission for that folder only. Start with something low-stakes — a test folder, not your entire Documents directory.

4

Describe what you want done

Type your request in plain language. Claude creates a plan, breaks it into steps, and works through them. You can watch in real time, steer if needed, or walk away and come back to finished work.

Important

The Claude Desktop app must stay open and your computer must be awake while Cowork runs. Close the app = session ends. Scheduled tasks have the same requirement.


Cowork isn't just "chat with file access." It's a fundamentally different way of working — Claude doesn't just answer, it delivers.

📁

Real file access

Reads, edits, and creates files directly on your machine. No upload limits, no copy-paste gymnastics.

📊

Pro output formats

Excel with working formulas, PowerPoint decks, Word docs, PDFs — saved straight to your folder.

🔀

Sub-agents in parallel

Complex task? Claude spins up multiple sub-agents working simultaneously on different parts.

🔌

38+ connectors

Slack, Gmail, Google Drive, Notion, Figma, GitHub and more. Connect once, use everywhere.

🌐

Browser automation

Pair with Claude in Chrome to research sites, fill forms, and pull data from web pages.

💡

Global instructions

Set your tone, format preferences, and role context once in Settings. Applies to every session.

Tip: batching is your friend

Cowork uses more of your usage allocation than regular chat. Batch related work into single sessions and use Chat for quick questions. Save Cowork for the tasks where you want finished outputs.


Launched in March 2025, Projects changed how Cowork organises work. Instead of every conversation sharing the same context, you get isolated workspaces — each with its own files, memory, and instructions.

What Projects are

A self-contained workspace for one area of your business. Each project holds its own files, links, custom instructions, scheduled tasks, and persistent conversation history. No cross-contamination between projects.

🧠

Persistent memory

Claude remembers context between tasks within the project. Your brand voice, client details, previous decisions — no more re-explaining.

📥

Import from Chat

Already have Claude Chat projects with useful context? Import them into Cowork with one click.

📁

Dedicated file access

Each project links to its own local folders. Client work stays in the client project, content stays in the content project.

⏰

Project-scoped scheduling

Schedule tasks within a specific project's context. A weekly report in your analytics project won't pull from your marketing folder.

How to create your first project

1
Open Cowork in Claude Desktop
2
Click "Projects" in the left sidebar → "New Project"
3
Give it a name and select a working folder
4
Add project-specific instructions (optional but powerful — your brand voice, key terms, preferred formats)
5
Start working — Claude builds context as you go. The more you use a project, the smarter it gets.

Tip: Projects = no more context-switching tax

Before Projects, every Cowork session shared context — Claude could carry assumptions from your marketing task into your finance task. Projects fix this. Each workspace is completely isolated.


Skills are portable processes that work everywhere — any project, any chat. They teach Claude HOW to do something specific. Think of them as SOPs that Claude follows automatically.

What Skills Are

  • A reusable process written in plain markdown
  • Loads only when triggered (lightweight on context)
  • Works across Claude.ai, Cowork, and Claude Code
  • No coding needed — just describe the process
  • Build once, use forever across all your work

What Skills Are NOT

  • Not a workspace (that's a Project)
  • Not a plugin (that's a bundle of skills + connectors)
  • Not memory — skills don't remember past runs
  • Not project-specific — they're global
  • Not complex — a single markdown file is all you need

Built-in skills

docx — Word documents pptx — PowerPoint decks xlsx — Excel spreadsheets pdf — PDF creation canvas-design — Visual design skill-creator — Build your own

Build your own skills

Use the Skill Creator inside Cowork — describe what you want and Claude assembles it into a reusable skill. Or write a simple markdown file yourself with the objective, required inputs, steps, and expected outputs.


They sound similar. They're not the same thing. Here's the actual difference.

Feature Projects 📁 Skills ⚡
Purpose Organise context + files for one area of work Encode a repeatable process
Memory ✅ Remembers across tasks ❌ No memory — it's a process template
Scope Scoped to that project only Available globally across everything
File access Links to local folders + files Can reference files but doesn't store them
Where it works Cowork only (desktop app) Cowork, Claude.ai, Claude Code, API
Context load Loads all project files + history every session Loads only when triggered (lightweight)
Scheduling ✅ Schedule tasks within the project ❌ Not schedulable on their own
Best analogy A filing cabinet for one client or area An SOP your whole team follows

When to use what

Managing all your content creation — scripts, outlines, metadata Project
Getting Claude to always write captions in your brand voice Skill
Running your weekly email newsletter with all past issues stored Project
Creating a "vibe check" process that reviews any piece of content Skill
Processing client consult transcripts with all client files Project
Responding to DMs with consistent tone across every platform Skill
Building a YouTube content system with competitor analysis + scripts + scheduling Both ✨

The Power Move: Use Both Together

A Project gives Claude all the context it needs. A Skill gives it the exact process to follow. Together? You've got a system that compounds over time.

Client Project 📁 + Email Responder Skill ⚡ → On-brand client replies every time ✨

What it is

Write a prompt once. Tell Cowork how often to run it. No code, no APIs, no cron jobs. Claude runs the full task on schedule — with your files, connectors, and plugins all working together.

How to set one up

Two ways — both take about 2 minutes.

Type /schedule inside any Cowork task and Claude walks you through it. Or click Scheduled in the left sidebar → "New task".

Morning brief

Daily 7:30am — Check Slack + calendar, flag anything urgent, save summary to markdown

Weekly report

Fridays 4pm — Pull project notes, summarise deliverables, format as client update

File cleanup

Weekly — Organise Downloads folder by type, delete duplicates older than 30 days

Competitor scan

Mondays — Check industry news, drop formatted summary into research folder

Hourly Daily Weekdays only Weekly Monthly On demand

Good to know

After the first run, Claude rewrites your prompt based on what it learned — which connectors to use, where the files are. The second run is usually better than the first.


Send Claude to work from anywhere

Dispatch is a persistent thread that syncs between your phone and desktop. Message Claude on your phone on the way to a meeting — it works on your desktop using your local files and connectors while you're out.

Think of it as a WhatsApp with your AI assistant — but it's actually getting things done on your computer.

You on mobile → Dispatch thread → Claude on desktop → Finished file saved

What you need

Pro or Max plan + both the Claude Desktop app (must be open) and the Claude mobile app. Open Cowork → click "Dispatch" in the left sidebar. Your connectors, plugins, and file access all carry over.

Safety note

Dispatch gives your phone control over your desktop. A task sent from your phone can read, create or move real files. Start with low-stakes folders while you find your feet.


What plugins do

Each plugin bundles skills + connectors + sub-agents into one install. Instead of briefing Claude on your workflow every time, install a plugin and Claude shows up knowing what to do. Find them at claude.com/plugins or Settings → Customise.

Marketplace plugins

Anthropic ships plugins for productivity, product management, legal, finance, marketing, and data. Third-party verified plugins also available. Enterprise admins can build private marketplaces and auto-install plugins for the whole team.

Build your own

Use the Plugin Create tool inside Cowork — describe what you want and Claude assembles the skills, connectors, and commands into a plugin package. Anthropic's plugin collection is open-sourced on GitHub if you want to fork anything.

How context layers work in Cowork

1 Global instructions — Settings → Cowork → Edit Global Instructions. Add your role, tone, standing context. Applies everywhere.
2 Project instructions — Each project can have its own instructions. Claude also updates these as it learns.
3 Context files — Drop a markdown file into your working folder with background info, brand guidelines, or past decisions.
4 Plugins + Skills — Load specialist processes on demand. Lightweight, only active when triggered.

Privacy note

Cowork conversation history is stored locally on your device, not on Anthropic's servers. Claude always shows you its planned actions before executing — especially for anything that modifies or deletes files.


Ready to go deeper?

Pick the option that matches where you're at.