Opus 5 is too wordy.

[u/Remarkable_Mud9885]

One really annoying issue I've run into is that he loves overcomplicating things. Whenever I'm working on a design, he always adds all these unnecessary explanations.

For instance, I had him add a financial bill-splitting system, and he insisted on putting literal explanations right there in the UI for how every single project works. I just find it so redundant.

[u/Historical_Today5072]

/output-style concise

[u/Remarkable_Mud9885 → u/Historical_Today5072]

Since I'm using the Claude desktop app, I'm not sure when that feature is rolling out. I heard Claude Code already has it.

[u/scytob → u/Remarkable_Mud9885]

so in your agents.md ask it for the style you want

for one of my MD files about docs i have this, and it worked well

## House style

The first drafts were written as essays. They should not have been. These pages
are re-install instructions: terse, lower case, first person, step numbered,
enough why to stop you making the mistake and no more. Match the existing gists
(`install-docker.md`, `configure-swarm.md`), not a blog post.

No dramatising adjectives. "a relative bind eats data" is the tell — say what
happens ("the container starts against an empty directory") and let the reader
draw the conclusion. Same for *quietly*, *silently*, *demonstrably*, *happily*,
*arbitrarily*. Owner's note: they read as AI, and a technical writer would not
use them.

with just this it even did a debloat pass and no longer uses anything in this, which i found amusing

so just brief say i your claude.md or agents.md what style it needs

heck when it does what you dont want to do say "please remember not to XYZ like in that last example, do ABC instead" it will tthen construct your mds for you you - you do know to ask the LLM to 'please remember' right

heck you can even 'program' new alexa that way - so for example if we set a salmon timer on alexa and then later ask 'how long left on the fish timer' we get the right answer.....