28/09/2026
Opus 5.5 brings a massive shift in how we work with AI across Claude Code and the Claude app.
We’re finally moving away from micromanaging every single prompt and babysitting the output. Instead, the dynamic has shifted to steering autonomous workflows: defining clear boundaries, setting clear success criteria, and letting the model do the heavy lifting.
Inspired by Addy Osmani’s recent breakdown, here are some practical, game-changing habits to adopt right now:
👉 1. Define what “done” looks like, then step back
Instead of guiding the model step by step, give it the entire problem and define the finish line up front.
👉 2. Ditch “think step by step”
Opus 5.5 handles deep reasoning natively. Old prompt hacks like “think hard” or “think step by step” only slow things down with no real quality bump. In fact, if you just want a quick reply to a straightforward question, tell it: “Answer directly.”
👉 3. Set rules of engagement in CLAUDE.md
Give the model explicit autonomy boundaries in your config file. Tell it: “When a step doesn’t need input, keep going. Stop and ask only when blocked or before anything destructive (like deleting data or force-pushing).” This prevents unnecessary pauses on routine tasks.
👉 4. Use TASKS.md to prevent context loss
Context windows get summarized during long sessions, but a persistent local file never forgets. Keep a `TASKS.md` file in your repo so Opus can log progress, check off items, and stay anchored across hours of ex*****on.
👉 5. Scale audits with subagents
Need to review a massive codebase? Fan out audits across parallel subagents, then have Opus aggregate the evidence into a single, structured summary table.
👉 6. Check pending decisions first
When a long run wraps up, don't get lost reading the full log right away. Jump straight to the open decisions or blockers that need your human input, then review the code changes.
👉 7. Handy Claude Code power tips
• Type `/fast` when doing interactive back-and-forth work to maximize token output speed.
• Drop screenshots and diagrams directly into the chat: Opus 5.5 understands layout hierarchies, connected nodes, and visual flows effortlessly.
• If a safety filter unexpectedly shifts you to an older model, quickly switch back using `/model` or hit Esc twice to rephrase your prompt.
Have you tried Opus 5.5? I'm having a great time with it.
How are you adjusting your prompting habits?