Your Cowork Command Center

Claude Cowork Cheat Sheet 10 tips that turn the Claude desktop app into your personal operating system. No terminal required.

JJ Englert
@JJEnglert
Get Started
Chat vs. Code vs. Cowork
Chat gives you text. Claude Code runs in the terminal. Cowork gives you files — real .docx, .xlsx, .pptx saved to your computer. No terminal needed. Click the Cowork tab in Claude Desktop.
Import Your Memory
Switching from ChatGPT? Go to claude.com/import-memory, copy the prompt, paste it into your old AI, paste the output back. Under a minute. Review before importing — your old AI may have saved inaccurate info.
Quick Start Checklist
Download app → Sign in (paid plan) → Click Cowork tab → Create workspace folder → Write context files → Set Global Instructions → Install first plugin → Connect first tool → Run first task.
Available Plans
Pro ($20/mo), Max 5x ($100/mo), Max 20x ($200/mo), Team ($25+/seat), Enterprise. macOS + Windows. Your computer must stay awake and the app must stay open during tasks.
Build Your Brain
Global Instructions
Settings > Cowork > Edit. These load before everything else — before files, before your prompt. Include: your name/role, plan-before-execute rule, output format prefs, and safety guardrails. Don't leave this blank.
Context Files
Create about-me.md, brand-voice.md, and working-preferences.md in a 00_Context/ folder. These compound over time — update them after every session where output missed the mark.
Scope Your Folders
Never point Cowork at your entire Documents folder. More files = more noise = worse output. Use a dedicated workspace: ~/Cowork-Workspace/ with 00_Context/, projects/, and outputs/.
Plan Mode
One line in Global Instructions prevents 90% of mistakes: "Show a brief plan before taking action. Wait for my approval before executing." Think of it like working with a project manager.
Connect Everything
Slack
Summarize channels, find buried decisions, draft updates, post messages. Set: read = Allow, post = Ask. Customize > Connectors > Slack.
Google Calendar
Review your week, find back-to-back meetings, suggest focus time, create prep docs. Pairs well with Gmail for meeting prep. Customize > Connectors.
Gmail
Search inbox, extract data from emails, draft responses. Set Gmail tools to "Ask" so Claude confirms before sending. Allow reading automatically.
30+ Connectors
Notion, Google Drive, Figma, HubSpot, Linear, Jira, Asana, Snowflake, and 20+ more. Start with Slack, Google Drive, or Notion — highest leverage. Settings > Connectors.
Plugins & Skills
Install Plugins
Customize > Browse Plugins > Install. Plugins bundle skills, connectors, slash commands, and sub-agents for your role. Everything is markdown + JSON — no code, no build steps.
Start with Productivity
Install Productivity first (useful for any role), then add one that matches your job. Type / to see available slash commands from installed plugins.
Core Plugin List
Productivity, Marketing, Sales, Finance, Data Analysis, Legal, Product Management, Customer Support, HR, Engineering, Design, Operations, and more. Browse at claude.com/plugins.
Build Skills
Skills are precision playbooks for specific outcomes. Customize > Skills > create or add. One skill per outcome. Start with: x-post-writer, email-drafts, meeting-briefs.
Self-Improve Loop
After every strong result: update the skill with what worked, store the output in successful examples, summarize what changed. After every miss: add a gotcha — "Never do X." Good examples teach format. Bad examples teach boundaries. Both compound.
Customize Anything
Click Customize on any plugin to adjust it. Every plugin is just files on your machine. Read, edit, fork, and share them like regular documents.
Three Instruction Layers
1. Global Instructions (universal, every session). 2. Folder Instructions (project-specific context). 3. Your prompt (the task). They stack — most general to most specific.
Open-Source Plugins
All official plugins are open source at github.com/anthropics/knowledge-work-plugins. Fork them, customize them, build your own, share with your team.
Cowork Projects
What Projects Adds
Scoped memory between sessions, permanent instructions that never disappear, task history Claude can reference, and scheduled tasks tied to your workspace. Same Cowork — but now it remembers last Tuesday.
Orientation Prompt
Day one of every Project: "Read every file. Summarize what's here, what I use it for, and what instructions you'll follow." If something's off, your instructions need to be clearer. Fix before running real tasks.
Keep Instructions Short
5-8 lines. That's it. The more you write, the more Claude hedges. One clear rule beats three vague ones. Add one gotcha every time output is wrong — great Projects are built in weeks.
The Compound Effect
First report is good. Fourth is noticeably better. By month two, output feels like someone who's worked with you for a year. Instructions stay, examples stay, task history builds.
Power Moves
Scheduled Tasks
Type /schedule or click Scheduled in the sidebar. Set tasks to run daily, weekly, or on any cadence. App must stay open — dedicate an old machine as your always-on Cowork station.
Daily Briefing
Schedule for 6 AM every weekday: check urgent Slack DMs, scan Gmail, review today's calendar, output a briefing with urgent items, prep notes, conflicts, and top 3 priorities. Ready by 8 AM.
Workspace Map
Create a workspace-map.md with your full folder structure and instructions for how Claude should navigate it. Pattern: skill file + new posts + successful posts per platform.
CONTEXT.md Everywhere
Drop a CONTEXT.md in every Project with core business context — who you are, clients, tone, non-negotiables. Two minutes of setup, permanent payoff. Claude never has to ask who you are.
Permission Controls
Set each tool to Allow (auto), Ask (confirms first), or Block (never). Best default: let Claude read everything automatically, confirm before posting or sending.
Mobile Workaround
Push your workspace to a private GitHub repo. Open Claude Code on mobile and pull that repo for context — or use Dispatch to remotely access files on your desktop machine. Sync back to desktop for heavy execution.
Multi-Machine Sync
Projects don't cloud-sync yet. Workaround: keep your working folder in Dropbox, Google Drive, or iCloud. Files travel; task history doesn't — but that's most of the value.
Scaling to a Team
On Team or Enterprise, skills and plugins are shared across seats automatically. For full project sharing — context files, instructions, examples — keep the workspace folder in a private GitHub repo and have teammates clone it.
Safety Defaults
Add to Global Instructions: never delete files without confirmation, never modify files outside output folder, show plan before executing, ask rather than assume. Back up before your first real task.
Usage Strategy
Use Haiku or Sonnet as your daily driver for routine tasks — fast, cheap, good enough. Switch to Opus only when you need deep reasoning or complex multi-step work. Save tokens for where they compound.
New Chats > Long Threads
Inside a Project, start a new chat for each task. You get shared memory across all chats, but each session stays lean. One long chat = bloated context, messy history, harder for Claude to know what "done" looks like. Short chats, clear scope, shared memory.
Level Up to Claude Code
Once you've mastered Cowork, Claude Code runs in the terminal and can build entire projects. Same philosophy, more power. Install: curl -fsSL https://claude.ai/install.sh | bash