Understand this story
Addy Osmani, a member of the Anthropic Claude Code team, published a post on October 30, 2026, discussing how to use Claude Code in the era of Claude Opus 5.5. He proposed that starting with the Claude 5 series, users should reduce piling up prompts and hand-holding task breakdowns, and instead use a single prompt to clearly state the goal and acceptance criteria, letting the model run to completion on its own and then stop; reasoning effort can start from /effort medium, and when the goal is unclear, first have Claude interview you to produce a spec, then open a new session to implement it. He mentioned that Claude Code once removed more than 80% of its system prompts for models such as Claude Opus 5 and Claude Fable 5, with no measurable decline in coding benchmarks, and recommended using /doctor prompt-audit to find prompts written for older models. He also said that the Claude Code interactive terminal recently defaulted to auto mode, but this is not a safety guarantee; subagents should be split manually as little as possible, and a single agent plus skills often yields better quality.
AI-generated from public reports
Latest update · Discussion
Shao Meng joined this discussionDevelopments
1 confirmed developments
Addy discusses how to use Claude Code in the Claude Opus 5.5 era
Source:Shao Meng
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 31
Shao MengRelated discussion
Shao Meng joined this discussion
This post contributes to heat; it is not a formal report or confirmed fact.
Oct 30
36Kr · AI
Claude Code team member on how to reduce over-prompting Claude
Addy Osmani, a member of the Anthropic Claude Code team, wrote in a post that users generally over-prompt Claude, and suggested using a single prompt to clearly state the goal and acceptance criteria, then letting the model execute on its own, with reasoning effort starting from /effort medium. He mentioned that Claude Code once removed more than 80% of the system prompts for models such as Claude Opus 5 and Claude Fable 5, with no measurable decline in coding benchmark performance, and suggested users use /doctor prompt-audit to find prompts written for older models. The article also suggests first making a single session capable of completing tasks independently before considering parallel multi-session work, and focusing attention on verifying results.
VikingRelated discussion
Viking joined this discussion
This post contributes to heat; it is not a formal report or confirmed fact.
Shao Meng
Addy on how to use Claude Code in the Claude Opus 5.5 era
Addy Osmani discusses how to use Claude Code in the Claude Opus 5.5 era, arguing that starting with the Claude 5 series, users should reduce piling up prompts and hand-holding task breakdowns, and instead use a single prompt that clearly states the goal and acceptance criteria, letting the model run to completion on its own and then stop. He recommends starting from /effort medium; when the goal is unclear, first have Claude interview you to produce a spec, then open a new session to implement it. For Claude Opus 5 and Claude Fable 5, he removed more than 80% of the Claude Code system prompt, with no noticeable drop in coding benchmarks. He also mentioned that the Claude Code interactive terminal recently defaulted to auto mode, and said this is not a safety guarantee; sub-agents should be split less by hand, and a single agent plus skills often yields better quality.
Heat trend for this story
- Current
- 12
- Period peak
- 25 Oct 30 23:00
- 24-hour change
- -37%
Move the pointer or select the chart to inspect hourly heat. Use the left and right arrow keys with a keyboard.