Your Opus 5.5 Prompt Checklist
Anthropic's own guide to prompting Opus 5.5 and Claude Code, boiled down to the five changes that matter, with the exact text to paste and the catch
2min read
1prompts to copy
5numbered steps
3sections
Opus 5.5 works longer on its own and thinks before every reply, so the old prompt habits can get in the way. This is the checklist from Anthropic's guide, in the order to try it.
The checklist
- Delete "think carefully" lines from your prompts. Opus 5.5 already thinks before every reply.
- Hand over the whole task in one message. Name the finish line, like "the tests pass" or "every endpoint is migrated", and say when it should stop and ask. Then let it work.
- In Claude Code, you can type a new message and press Enter while it works. Example from the guide: "Also keep the old endpoint names as aliases."
- Put stop rules in your CLAUDE.md (text below). Keep permission prompts on for destructive commands too.
- When a long run ends, read what it needs from you first.
PROMPT
PASTE INTO CLAUDE.md When a step doesn't need my input, keep going. Put status notes in the same message as your next action. Stop and ask only when you can't continue without me, or before anything destructive: deleting data, force-pushing, or changing anything outside this repository.
Keep reading
Free, for an email.
Unlocks 2 more sections, the document version, and every other guide on the site, for free. Enter your email once to keep reading.
45,000+ follow where these guides come from.No spam. Unsubscribe in one click.