Chat thinks. Cowork does. Code builds. Design creates. Picking the wrong one is why the output keeps coming back generic. Here is when to reach for each, and how to chain them so the work actually leaves the chat window.
For a long time Chat was the only Claude, so that is the one almost everyone defaults to. It is also the wrong tool for roughly half of what people are pushing through it. Running EDGE and becomingscott in parallel with ADHD means leverage is the difference between things shipping and things stalling, and all four of these now sit in my daily rotation.
There are four distinct Claude products now, built for completely different jobs. Chat is the thinking partner. Cowork is the agent that takes action on your computer. Code reads and writes real code in your repo. Design generates the visual layer. When the output keeps coming back flat, it is usually because the thinking tool is being asked to do the building.
The real unlock is not any single Claude. It is chaining all four, using each one for what it actually does and handing the output to the next.
What follows is the cheat sheet. A side by side of what each Claude does, what it can access, when to reach for it, an example prompt per tool, and the chained workflows that combine all four.
The conversational Claude, built for writing, brainstorming, analysis, decisions, learning, and chewing through documents. You talk through an idea and it pressure-tests the weak parts. You paste in a doc and it summarises, then asks the questions you forgot to ask.
Web search, uploaded files including PDFs, docs, images, and code, Projects for persistent custom context that travels with you across chats, and Artifacts for documents and code that live inside the conversation.
Drafting copy, working through a hard decision, getting up to speed in a new domain quickly, pressure-testing a strategy, or synthesising a messy pile of notes. Anywhere you would otherwise spend an hour at a whiteboard or on the phone to a smart friend.
Operates your computer for you. It clicks through the browser, opens and edits files, runs multi-step workflows end to end, processes data at volume, and runs the same routine on a schedule. Where Chat tells you what to do, Cowork is the one that actually does it.
Your screen and browser, local files and folders, and scheduled task runners. If a person could do it by clicking around your desktop, Cowork can do it without you sitting there watching.
Repetitive multi-step workflows, pulling data out of tools that have no usable API, cleaning and renaming a folder of files, or running the same checklist every Monday morning. Anywhere you would otherwise hire a VA or block out an afternoon to just get through it.
Reads, writes, and refactors actual code in your repo. It builds features, scripts, automations, and entire apps from a plain English description, runs the tests, debugs the failures, and ships the result. It lives in your terminal or as an extension inside VS Code and JetBrains, sitting where the work actually happens.
Your repo, your local environment, your packages and dependencies, your tests, and your deploy commands. It can grep, edit, run, and commit, which is the whole loop a developer runs, only now you are reviewing the diff instead of typing it.
Shipping a feature, refactoring a tired module, debugging something gnarly, building the internal tool you would otherwise pay a SaaS for, automating a dev workflow, or spinning up a quick script that pulls one number from one place and posts it somewhere else. Anything code-shaped, basically.
Generates visual assets directly from a description. Pitch decks, landing page mockups, social graphics, brand explorations, 3D scenes, and product visualisations all sit inside its range. You describe what you want and Design produces it, then sits there waiting for you to push back on the bits that are not quite right.
Your prompt, any reference images you upload, the brand guidelines you hand it, and an iterative loop where you point at a specific element, ask for a change, and watch it revise without losing the rest.
Pitch decks, landing page mockups before you commit to building the real page, social tiles, and product mockups for a Figma file you have no patience to draw. Any visual where the prompt is clearer in your head than the pixels are, and where you would otherwise outsource it or lose an hour pushing shapes around in Canva.
Use Chat to think through the spec first, covering what the tool does, what it deliberately does not, and where it is likely to fail. Then hand a clean written spec to Code and let it build against that. The output is dramatically better than asking Code to figure out both the design and the implementation in one go.
Cowork is excellent at pulling raw inputs and ordinary at synthesis. Let it gather the data and dump it into one doc, then take that doc into Chat for the actual thinking. One agent pulls, the other processes, and the result is sharper than either could produce alone.
Mock the visual in Design first and only lock in the layout once it actually looks right. Then hand the mockup and the locked copy to Code and ask it to build the real thing in HTML and CSS. Skipping the Design step is the reason most landing pages built by devs end up looking engineered rather than designed.
Chat decides what needs to happen, including the sequence, the safety checks, and the edge cases worth catching. Cowork then executes those steps in order without needing you in the chair. This is how a single twenty minute conversation turns into half a day of finished work done while you are somewhere else entirely.
The anti-pattern is trying to do all four jobs inside Chat. It can fake the other three convincingly enough to feel like progress, but the output stays trapped in the chat window with no file on disk, no app shipped, and no deck anyone can actually open. Chat is the thinking partner. Cowork, Code, and Design are the hands that turn the thinking into something real.
Book a call. Happy to do the work directly, advise you through it, or connect you with the right person in my network. Every problem leaves with a path forward.
Book a Call →