Master Claude: Your AI-Powered Work Assistant / From skill to service
Troubleshooting common problems
About 10 minutes
Most problems with Claude fall into a few patterns. This lesson lists each one, its likely cause and what to try.
1. The answer is generic
Cause: the brief is too thin.
Fix: add the five parts from Lesson 4: task, context, inputs, constraints, format. Or ask Claude to interview you:
Before answering, ask me the questions you need to make this specific to my situation.
2. Claude states something false with confidence
Cause: the model can produce plausible but wrong details, especially names, figures, quotes and links.
Fix:
- Give it the source material instead of relying on its memory.
- Allow it to say it does not know:
If the documents do not answer this, say "not in the documents". Do not guess.
- Ask for quotes from the source for each key claim.
- Check the claim yourself.
3. It ignores an instruction
Causes: the instruction is buried, conflicts with another one, or has no reason attached.
Fix:
- Move the instruction near the end of the prompt, next to the task.
- Remove conflicting instructions in your Project or knowledge files.
- Add the reason.
- Ask Claude to check its output against your list of constraints.
4. The answer is too long or too short
Fix: give a number and a format. "Under 100 words, three bullet points" works better than "brief".
5. Long chat, worse answers
Cause: the chat contains many old drafts and changed instructions.
Fix: ask for a summary of decisions, start a new chat (inside the same Project), and paste the summary in.
6. No file appears when you ask for a document
Checks:
- Is Create and edit files turned on in Settings > Capabilities? On Team or Enterprise, an owner may need to enable it.
- Did you name the format, such as ".docx" or ".xlsx"? Without a format, Claude may answer in the chat instead.
- Is the file over 30 MB? That is the per-file limit.
7. Research is missing from the menu
Checks:
- Research needs a paid plan.
- Web search must be turned on.
- Look under the + button at the bottom left of the chat box.
8. You hit usage limits
Causes: long chats, large files and file creation all use more of your limit.
Fix: start fresh chats more often, trim files to the parts you need, and save heavy file work for when you need it. If you regularly hit limits, compare plans on the pricing page.
9. A connector stops working
The help centre suggests disconnecting the connector under Customize > Connectors and reconnecting the next time you use it. For Google, you can also remove Claude's access at myaccount.google.com/connections and connect again.
10. Claude Code: "command not found"
Fix:
- Open a new terminal window after installing.
- Run
claude --version. - If it still fails, the install folder is not on your PATH. Follow the "Troubleshoot installation" page linked from the quickstart.
On Windows, check which shell you are in. If you see 'irm' is not recognized, you are in CMD, not PowerShell. If you see The token '&&' is not a valid statement separator, you are in PowerShell, not CMD. Use the matching install command.
11. Claude Code does not follow your CLAUDE.md
Fixes:
- Make sure the file is in the folder where you start
claude, or a folder above it. - Keep instructions short and specific. The docs note that concise instructions are followed more consistently.
- Remove rules that contradict each other.
A general debugging routine
- Reproduce the problem in a fresh chat.
- Change one thing at a time.
- Keep the version that works, and note it in your prompt library.
Exercise
- Find a prompt that gave you a poor result during this course.
- Identify which problem above it matches.
- Apply the fix and compare the two results.
- Write the fix into your prompt library under "Known issues".