Claude · Mistakes

Prompting mistakes

Fix generic answers, replies that miss your question, easy agreement, and prompts that bundle unrelated jobs.

Claude prompting mistakes

How to tell which mistake you made

Look at the answer you got. If it's correct but could apply to anyone, the prompt was vague. If it discusses your situation but gives you nothing to use, the request was missing or unclear. If some parts are strong and others are thin or absent, you bundled too much. If it praises your idea, you may have shown which answer you wanted.

Rewrite the prompt, not the answer

When an answer misses, a follow-up correction feels quicker, but each one adds to the conversation. Anthropic's Claude Code guide says that after two failed corrections, you should clear the session and write a better prompt. Rule of thumb, not a vendor figure: use the same approach in chat when your second correction hasn't fixed it.

Frequently asked
Why are Claude's answers so generic?

The prompt probably left out the reader, purpose or standard, so Claude wrote for a typical case. Anthropic's docs say the more precisely you explain what you want, the better the result.

Why does Claude agree with everything I say?

AI assistants can drift toward what a user seems to want, as Anthropic's research on sycophancy describes. Present options neutrally, set your criteria first, and turn memory off for that chat from the + menu.

Should I put several tasks in one Claude prompt?

You can if they're related and listed clearly. Anthropic's docs recommend numbered steps when order or completeness matters. Split them into separate turns when you need to check one result before the next step.

How long should a Claude prompt be?

As long as it needs to be to cover the reader, purpose, facts and standard. Length itself doesn't help. A short prompt with clear limits usually does better than a long one with none.