Claude Opus 5.5: 7 Prompting Habits to Update
ملخص
Pixel shares Anthropic’s guide to using Claude Opus 5.5 for knowledge work, including why removing phrases like “think hard” may speed up responses without a clear quality drop. The announcement covers connecting files and apps, defining what a finished result should look like, and a chart-to-report prompt example.
DEV Community
Your Old Claude Prompts Might Need an Update
Hey devs! If you still add “think hard” to your Claude prompts, try leaving it out. In its Opus 5.5 tests, Anthropic found that removing instructions like “think hard” and “think carefully” made replies start sooner, with no clear drop in quality. That caught my attention because it is an easy habit to keep carrying from one model to the next. On November 12, 2026, Anthropic published its guide to using Claude Opus 5.5 for knowledge work. It covers seven prompting habits to revisit. I tried the examples in Claude. Below, I’ll show you the prompts, the effort setting, and what happened when I asked it to turn a chart into a report. You can also watch my full video walkthrough on YouTube. 1. Connect your files and apps Give Claude access to the material the task depends on. If you need a report based on a spreadsheet and a meeting note, provide both. Tell Claude which files to use and what you want it to produce. You can upload the files directly or use a connector to the app where they live. Connecting an app is useful when Claude needs to find several related documents. On Team and Enterprise plans, an owner must enable a connector before members can use it. Start with the sources. A detailed prompt still leaves Claude guessing if the spreadsheet it needs is missing. 2. Say what “done” looks like In your first message, describe three things: What you want to achieve. What the finished output should look like. When Claude should stop and ask you a question. Here is the prompt I used with a chart: Make a 1-page report on this. Use the data from this chart.
Ask me if data is missing.
Claude asked who the chart covered, whether I had exact figures, what an annual data point meant, and who would read the report. I told it to keep the context generic, use its approximate readings, treat the annual point as an annual average, and write for management. After those answers, it created a report with a summary and a chart. The useful part was seeing the assumptions before they became part of the report. The finished file still needs checking against the source data. Here is a template you can adapt: Goal: [what you want to achieve]
Result: [the finished file, its format, and its audience]
Ask me first if: [missing data or decisions you need to make]
3. Drop “think hard” Thinking is always on for Opus 5.5. Anthropic says the model adjusts how much it thinks based on your request and the effort setting. Compare these two prompts from my walkthrough. The first repeats the thinking instruction but leaves the task vague: Think hard about this. Think step by step and be very careful.
Analyze our sales data and tell me what's wrong.
Think really hard before you answer.
What does “wrong” mean here? Which period should Claude analyze? What should it return? The second prompt answers those questions: Look at the attached sales file for Q3. Find the 3 biggest reasons
sales dropped. Give me a 1-page summary with a simple chart.
If any data is missing, stop and ask me first.
This gives Claude something concrete to work toward. My screenshots illustrate the prompt change; they are not a measured comparison of answer quality. For your own task, check whether the response answers the question and supports its findings with the supplied data. 4. Start at Medium effort Anthropic recommends starting Opus 5.5 at Medium and increasing the effort when it stalls on your task. To change it, click the model name next to the send button, open Effort, and select Medium. Before changing the setting, check whether Claude has enough context. Did you attach the correct file? Did you explain the output? Is a decision missing? More thinking time won’t supply a missing spreadsheet. 5. Attach the chart instead of typing its numbers If you have a chart, screenshot, or diagram, attach it and explain what you want to learn. For my example, I started with: What is in the chart?
Claude described the axes and series, then created a table of approximate values. It als...

Powered by Readybot.io