Opus 5 is so much better with these rules in claude.md
retained text
I'm a Max 5x user who's been vibe coding for the past 4 months. Don't get me wrong, I still think Opus 5 is amazing when paired with Fable that plans/designs/writes out an implementation plan. But similar to the experiences of others in this sub, it hurts my head to deal with excessive verbosity and invented jargon in explanations. While suffering, I discovered the 8 rules below almost by accident, and the output is night and day: 1. Open with one paragraph on what the thing *is*, before any finding about it. 2. Name things in the user's world, not the code's: describe real-world entities and user-facing effects rather than internal variables, schema fields, or algorithmic parameters. Translate a formula into its effect and let the tables carry the magnitudes. 3. Coin no new terms. A plain metaphor is fine; a specialized term of art that masquerades as ordinary English is worse than obvious jargon. Short labels inside a table are fine once the prose has defined them and the table reads without them. 4. Show an effect as a walkthrough with real named values, ending on a plain-language punchline that states the actual outcome. Never describe a defect in the abstract. 5. Use plain-English table headers that describe concrete cases rather than statistical shorthand like min/p10/p50/p90/max. 6. State the honest case against your own recommendation, at full strength. 7. End with "what I'd do": a recommendation, not a survey of the options. 8. For a check that passed, say what it was watching for and what its failure would have looked like on screen — not just that it passed. What are your thoughts on this?
document fetched 2026-09-14 00:35 · canonical https://reddit.com/r/ClaudeCode/comments/1wfd53p/opus_5_is_so_much_better_with_these_rules_in