Tips, Tricks, and Troubleshooting

You’ve been using Cowork for a few lessons now. This is the lesson that makes you significantly better at it — the patterns and pitfalls that separate people who find Cowork “pretty cool” from people who can’t imagine working without it.

🔄 Quick Recall: From the connectors lesson, remember the principle of incremental trust — start with one connector, expand as you build confidence. That same philosophy applies to everything in this lesson.

Prompting Patterns That Work

The instructions.md Pattern

This is the single highest-value trick in this course.

Create a file called instructions.md in your working folder:

# My Cowork Preferences

## Identity
- I'm a marketing manager at a B2B SaaS startup
- My audience is primarily CTOs and VP-level decision makers

## Formatting
- Use markdown for all documents
- Headings: sentence case (not Title Case)
- Bullet points over numbered lists unless order matters
- Keep paragraphs to 3 sentences or fewer

## Naming
- Files: lowercase-with-dashes.md
- Dates: YYYY-MM-DD format
- Never use spaces in filenames

## Tone
- Professional but not corporate
- Direct, clear, no fluff
- Use "we" not "the company"

Then start every Cowork session with:

Read instructions.md first, then: [your actual task]

This gives you pseudo-persistence. Your preferences carry into every session without re-explaining them.

The Checkpoint Pattern

For tasks longer than 5 minutes, add checkpoints:

Do this in phases:

Phase 1: Read all the files and tell me what you found. STOP and wait for my approval.
Phase 2: Create the analysis. STOP and show me before saving.
Phase 3: Generate the final report and save it.

This prevents Cowork from running ahead and producing something you didn’t want. It’s slower, but the output quality is dramatically higher.

The Example Pattern

When you want output in a specific format, show an example:

Create meeting notes for today's standup. Use this format:

---
## Standup Notes — [date]
**Attendees:** [names]

### Updates
- **[Name]:** [what they're working on]

### Blockers
- [blocker description] → [proposed solution]

### Action Items
| Item | Owner | Due |
|------|-------|-----|
| [item] | [name] | [date] |
---

The attendees were Alex, Jordan, and Sam. [describe what happened]

Cowork follows the format exactly. No guessing, no “interpretation.”

✅ Quick Check: What’s the purpose of the instructions.md file? (It gives Cowork your persistent preferences without re-explaining them every session.)

Common Mistakes (and Fixes)

Mistake 1: Vague Prompts

The pattern: replace abstract verbs (“clean,” “fix,” “improve”) with concrete actions (“sort,” “change,” “shorten”).

Mistake 2: Too Many Files at Once

Cowork’s context window is large but not infinite. Signs you’ve overloaded it:

• Output quality drops halfway through
• It “forgets” instructions you gave at the start
• File references start mixing up

Fix: Batch your work. 10-15 files per pass is a reliable sweet spot.

Mistake 3: Not Reviewing Before Approving

When Cowork shows its plan, actually read it. Don’t just click approve. Common things to catch:

• “I’ll delete duplicates” — wait, what counts as a duplicate?
• “I’ll reorganize the folder structure” — into what structure, specifically?
• “I’ll update the formatting” — which formatting, in which files?

If the plan is vague, ask for specifics before approving.

Mistake 4: Starting Over Instead of Refining

When the output isn’t right, your instinct might be to write a brand new prompt. Don’t. Cowork keeps full session context. A short follow-up is almost always faster:

Almost there. Two changes:
1. The summary is too long — cut to 3 bullets max
2. You used the wrong date for the March data — it should be March 2026, not 2025

Two sentences instead of rewriting your entire prompt.

Troubleshooting Guide

“Cowork seems slow”

Cowork processes tasks sequentially. Complex multi-file tasks take time. A few things that help:

• Close other Claude conversations (they share your usage quota)
• Break the task into smaller chunks
• If you’re on Pro, consider Max for heavier workloads

“It made changes I didn’t approve”

This shouldn’t happen — approval gates should catch destructive actions. But if it does:

• Check your version of Claude Desktop (update if outdated)
• For future tasks, add explicit constraints: “Do NOT modify any existing files without asking me first”
• Use the “create new file” approach instead of “edit in place”

“The connector stopped working”

Connectors occasionally drop their authorization. Quick fixes:

1. Go to Settings → Connectors → Disconnect the broken one
2. Reconnect it (re-authorize)
3. If it keeps failing, use the local file fallback — export from the tool, put it in your Cowork folder

“I hit my usage limit”

Cowork uses significantly more tokens than regular chat because it reads files, plans steps, and generates output. On Pro:

• You’ll hit limits faster during intensive sessions
• Consider batching heavy work into one focused session rather than many short ones
• Max 5x ($100/month) gives roughly 5x the capacity

“Output is wrong or hallucinated”

Cowork can get facts wrong, especially when synthesizing information from multiple files. Always:

• Spot-check specific numbers and names
• Cross-reference generated summaries with source files
• Add “include the source filename for each data point” to your prompts for traceability

✅ Quick Check: What’s the first thing to check when Cowork produces unexpected output? (Your prompt — was it specific enough?)

Power User Tips

Tip 1: Name your output files descriptively. “report.md” is worse than “q1-marketing-report-2026-03-19.md”. Cowork follows whatever naming pattern you set.

Tip 2: Use Cowork for templates. Create templates for recurring work, then use Cowork to fill them with fresh data each time.

Tip 3: Chain tasks within a session. “Now do the same thing for the April data” works because Cowork remembers the session context.

Tip 4: Use scheduling for recurring tasks. Cowork supports scheduled, recurring tasks. If you do the same report every Monday, set it up once.

Tip 5: Read Cowork’s plan out loud. If the plan sounds wrong when you say it aloud, it’ll produce wrong output. This catches ambiguity fast.

Key Takeaways

• The instructions.md pattern gives you pseudo-persistence between sessions
• Checkpoints prevent Cowork from running ahead and wasting work
• Vague prompts are the #1 cause of bad output — be specific
• Batch large file operations into groups of 10-15
• Refine within a session instead of starting over
• Always spot-check numbers and facts in generated output

Up Next

Final lesson — the capstone. You’ll design and build a complete automated workflow for something you actually do every week. The goal: save yourself real time, starting this week.