How to Set Up Claude Cowork (Complete Playbook)

Source: Ruben Hassid on X
Original author: @rubenhassid
This post republishes and restructures the original long-form X article with all key visuals.

Why Cowork Matters

If you switched from ChatGPT to Claude, but still use Claude like a normal chat box, you’re missing the main upgrade: Cowork.

Cowork turns Claude into a file-aware operator:

• It reads your folders
• It asks clarifying questions
• It writes output files directly
• It supports plugins and connectors

The idea is simple: stop over-optimizing prompts, and start optimizing context files.

---

Claude Product Line (Quick Map)

• Claude Chat: standard chat interface
• Claude Projects: chat organized by project spaces
• Claude Code: coding-focused workflow for developers
• Claude Cowork: task workflow for knowledge workers
• Claude Skills: reusable workflows
• Claude Connectors: connect Claude to Slack/GDrive/Notion/etc.
• Claude Plugins: app-like extensions for specialized workflows

---

Step 1 — Install and Configure Cowork

1. Download Claude desktop app: claude.com/download
2. Use Pro plan (recommended in source article)
3. Open Cowork tab
4. Pick your working folder
5. Use Opus 4.6 + Extended thinking (as suggested in source)

---

Step 2 — Build Your Folder System

Create one parent folder (e.g., CLAUDE-COWORK) with four subfolders:

1. ABOUT ME/
2. PROJECTS/
3. TEMPLATES/
4. CLAUDE OUTPUTS/

This keeps context clean and limits risk, because Cowork has read/write access to shared folders.

---

Step 3 — Create Core Markdown Files

Start with:

• about-me.md
• anti-ai-writing-style.md

Core principle:

• One strong, intentional markdown file beats dozens of random uploads
• High-quality context reduces prompt length and improves output consistency

---

Step 4 — Set Global Instructions Once

In Claude settings: Settings → Cowork → Edit Global Instructions

Use persistent instructions for:

• What to read before every task
• Which folders are read-only
• Where to write outputs
• Naming conventions
• Clarification behavior (ask questions before execution)

---

Core Prompt Pattern (High-Leverage)

A reusable pattern from the article:

“I want to [TASK] to [SUCCESS CRITERIA]. First explore my folder, then use AskUserQuestion to gather context before executing.”

Why it works:

• You provide structure + success criteria
• Claude asks targeted questions
• It executes after alignment

---

Let Claude Ask You (AskUserQuestion)

This is a key Cowork behavior:

• Claude generates interactive clarification forms
• You answer quickly with options
• Claude refines plan and output

This feels less like “prompt wrestling” and more like managing a capable teammate.

---

Plugins in Cowork

Install path:

1. Open Cowork
2. Click Customize
3. Browse plugins
4. Install
5. Type / to see available plugin commands

Typical plugin use cases mentioned:

• Marketing drafting
• Data exploration
• Legal review

---

Connectors

Connectors integrate Claude with tools (e.g., Slack, Google Drive, Notion, Figma).

Path: Settings → Connectors → Add

After setup, Claude can reference and operate against connected tool data during workflows.

---

Real Use Cases from the Article

1. Newsletter writing (with style files + references)
2. Consulting deliverables (brief + templates + past work)
3. Competitive research (multi-document synthesis)
4. Automated weekly briefings (scheduled plugin-driven workflow)

---

Limitations (Important)

The original article highlights these tradeoffs:

• Heavy usage can consume quota fast
• Still preview-quality behavior; mistakes happen
• Desktop app must stay open for long-running sessions
• Not ideal for quick trivial Q&A
• Multi-agent runs can occasionally drift

---

30-Minute Starter Plan

• 0–5 min: install app + open Cowork
• 5–10 min: create 4-folder structure + first about-me.md
• 10–15 min: start first Cowork task with AskUserQuestion
• 15–20 min: install one relevant plugin
• 20–30 min: create a real deliverable for this week

---

Full Visual Gallery (All Extracted Images)

---

Attribution

• Original post: https://x.com/rubenhassid/status/2029514946640322593
• Author: Ruben Hassid (@rubenhassid)

If you are the original creator and want edits/removal/credit changes, contact ClawList and we’ll update immediately.