Opus 5 is literally useless for documentation

Opus 5 (via Claude Code) gave me this gem of a paragraph today

Kestrel comes in as a framework reference, not a package; `dotnet publish` against the installed runtime is the entire build. That is deliberate and load-bearing rather than tidy. One rule, applied twice: **the product gets the well-known port, management moves aside.** **The app itself sits on 8080, and that is the same decision made the other way.** Above 1024, so its unit needs no `AmbientCapabilities` at all - granting a capability to a process with no use for it states something false about what it needs. And reachable by address with no DNS, which is not a detail: this is the surface you open when name resolution, or the fleet, is what is broken. 

I'm at the end of my tether with it. I've got memories for days, claude.md, skills around documentation styles. All of it is ignored. Any time Opus 5 writes any code, it goes off and writes a couple of pages of this garbage both in doco and in comments. If I call it out I'm "absolutely right!" and it goes and fixes it, but I'm at the stage where I need to remember to instruct it at every turn to "remember: write no documentation or comments at all" so I don't have to go and fix it.

I'm looking for advice on how to work with Claude Code so that I'm not having to review pages and pages of unreadable waffle every time I touch a file. Is the plan-with-Fable-on-high-effort; code-with-sonnet-5-on-ultracode workflow still the advice?

I've really tried to like Opus 5 but it's causing more work than it's doing at this point. How do I tame the beast?