Hamza JameelField sheet Nº 013

Free field sheet · Nº 013
Issued 29 Sep 2026

KeywordOPUS

Claude Opus 5.5 Prompt Rewrite Kit

Before/after rewrites and an effort-setting checklist to retest your Claude prompts today

Checks
18
Do first
5
Parts
5
Cost
Free
Hamza Jameel
Prepared byHamza Jameel10+ yrs · $8M+ ad spend managed · 150+ page-one rankings
Checked 0/18Top

Anthropic published new prompting guidance for Claude Opus 5.5 saying that old "think carefully" style instructions and effort settings can behave differently now, and may hurt performance instead of helping. This kit gives you the exact before/after rewrites and a checklist to retest your prompts today, so your Opus 5.5 outputs stay consistent.

Part 1 of 50/4

What changed

  1. The guidance was released alongside the model and covers how to write prompts and set effort levels for it, according to Anthropic's own documentation as reported by Search Engine Journal.

  2. This is a change from prior model generations, where those phrases were commonly recommended to improve reasoning quality.

  3. Effort settings that were tuned for earlier Claude models may not carry over cleanly to Opus 5.5 and could produce inconsistent results if left unchanged.

  4. Search Engine Journal reports that prompts already in production, including chat prompts, may need review under the new guidance, not only prompts written from scratch for Opus 5.5.

Part 2 of 50/3

Audit your existing prompts first

  1. You cannot fix what you have not listed. Put them in one sheet with columns for prompt text, effort setting, and where it lives.

    WhereClaude › Console › Workbench (or wherever your prompts are stored, e.g. a prompts repo or CMS)

  2. These are the exact style of instruction Anthropic's guidance singles out as potentially harmful for Opus 5.5. Flag every match for rewrite.

  3. You will need this baseline to compare before/after outputs once you retest, so you know if a change in output came from the prompt rewrite or the effort setting.

Part 3 of 50/4

Before/after rewrites you can copy

Replace vague instructions with specific, checkable instructions.

  1. Vague instructions to think carefully do not tell the model what carefully means. Replace with something the model can act on directly.

    Copy this
    Before: Think carefully before answering.
    After: List the [3] factors that matter most for this decision, then give your recommendation in one sentence.
  2. Give the model steps to follow instead of a general request for patience.

    Copy this
    Before: Take your time and make sure your answer is correct.
    After: Check your answer against these [3] criteria: [criterion 1], [criterion 2], [criterion 3]. Revise if any criterion fails, then give the final answer.
  3. Thoroughness is subjective. A required structure forces completeness without relying on the model to interpret 'thorough.'

    Copy this
    Before: Be thorough in your analysis.
    After: Cover these sections in order: [Summary], [Risks], [Recommendation]. Each section must have at least [2] sentences.
  4. Open-ended step by step requests can cause meandering. Defining the steps yourself keeps the model on task.

    Copy this
    Before: Think step by step.
    After: Follow these steps: 1) Identify the goal. 2) List constraints. 3) Propose one solution. 4) State one risk.
Part 4 of 50/4

Retest and set effort levels

  1. This is where you control how much computation the model applies per response, and it needs to match your rewritten prompts.

    WhereClaude › Console › Workbench › Model settings › Effort

  2. Look for the point where output quality stops improving. That is your target setting, going higher just adds cost and latency without benefit.

    Copy this
    Test prompt: Summarize the following [document/customer message] in [3] sentences and flag any [risk/complaint]. [Insert content here]
  3. Check for three things: is the answer still correct, is it the same length or shorter, and did it skip the vague filler language. If any of these fails, adjust the rewrite.

  4. Anthropic's guidance may update again. A dated log lets you know quickly which prompts still need retesting next time.

    Copy this
    Prompt name: [name]
    Effort setting: [low/medium/high]
    Last tested: [date]
    Rewrite applied: [yes/no]
    Notes: [any output changes observed]
Part 5 of 50/3

What good looks like

  1. If you removed a vague phrase and replaced it with a concrete task, checklist, or required structure, that is the correct fix.

  2. Simple lookups or short summaries should use lower effort settings, complex multi-step reasoning tasks should use higher ones. Test both ends of the range to confirm you are not overpaying or underperforming.

  3. This is your proof that you retested rather than assumed the old prompts still work the same way on Opus 5.5.

Want me to look at yours?

If you have gone through this and want a second pair of eyes, book a free call. We open the account together and look at what is actually happening. No deck, no pitch.

More free sheets

Sources
  1. https://www.searchenginejournal.com/anthropic-claude-opus-5-5-prompting-guidance/591278/