Tips & Best Practices
Cowork runs multi-step jobs on your files. Name files, show examples, and follow up when output needs changes.
Prompting practices that improve Cowork results
Five habits that make Cowork tasks more reliable. Each one below has a concrete example you can copy into your next project.
| Practice | One-line rule |
|---|---|
| Be specific | Name files, folders, output format, and what done looks like |
| Show examples | Include one good output sample and one thing to avoid |
| Plan before running | Ask Claude to show its plan before acting on multi-file jobs |
| Split large tasks | One prompt per phase: extract → merge → validate |
| Follow up | Refine results in the same project instead of re-running everything |
Write clear, specific prompts
Cowork needs the same details you would give a colleague: which files, what to change, where to save, and how to know the task is finished.
| Practice | Instead of… | Try… |
|---|---|---|
| Spreadsheet update | “Fix my spreadsheet.” No file names, no action, no output | “Open Q3-expenses.xlsx, add a Vendor column from vendor-list.csv (match on receipt ID), and save as Q3-final.xlsx in the same folder.” Files, action, mapping rule, and save location |
Use positive and negative examples
A single sample of correct output — plus one thing to exclude — removes ambiguity faster than a long list of rules. Reference an existing file when you have a format to match.
“Summarize each receipt in receipts/. Write one bullet per file. Do include vendor, date, and total. Do not include line-item detail or personal notes. Match the tone of last-month-summary.md.”
Office Depot — Mar 7 — $38.50
Note: call Sarah about…
Ask Claude to show its plan first
For jobs that touch several files or connectors, ask Claude to outline its plan before executing. You review the steps once instead of undoing a wrong batch edit.
| Practice | Instead of… | Try… |
|---|---|---|
| Multi-file job | “Update everything in this project folder.” No scope, no review step | “Think step by step: list files in receipts/, extract totals to CSV, then merge into Q3-expenses.xlsx. Show your plan before making changes.” Plan-first wording for multi-file Cowork runs |
Break complex tasks into smaller prompts
One Cowork run should have one main deliverable. When a workflow has extract, transform, and validate phases, run them as separate prompts inside the same project so each step can be checked before the next starts.
Goal: “Process all Q3 receipts into the master spreadsheet with flags”
- Extract — Pull raw data from source files into a simple intermediate format (CSV, JSON).
- Transform — Merge, format, or calculate — using output from step 1 as input.
- Validate — Flag errors, check totals, or compare against a reference file.
Iterate and ask follow-up questions
Cowork keeps task context inside a project. When output is mostly right, send a short follow-up — fix the three missing vendors, change the date format, re-run only the flagged rows — instead of repeating the full prompt.
Worked example — all practices together
Monthly expense report in one Cowork project
- Specific: “Process all PDFs in receipts/March/.”
- Examples: “Do: vendor, date, total per bullet. Do not: line items. Match last-month-summary.md.”
- Step by step: “Show your plan before writing to the spreadsheet.”
- Split: Prompt 1 — extract to CSV. Prompt 2 — merge into expenses.xlsx.
- Follow up: “Three vendors are blank — fill from vendor-list.csv.”
Before you continue
- Name files, actions, and outputs — vague prompts produce vague results.
- Use do / do not examples and reference files to lock in format.
- Plan first, split phases, and follow up in the same project to refine without restarting.
- Next: Introduction to Claude Chat — the chat interface for questions, writing, and file uploads.
What's Next
Introduction to Claude Chat — the chat interface for questions, writing, and file uploads.