Une ligne dans CLAUDE.md qui casse le réflexe over-engineering de Claude
Dev.to / 6/2/2026
💬 OpinionSignals & Early TrendsIdeas & Deep AnalysisTools & Practical Usage
Key Points
- The article explains how Claude repeatedly over-engineered solutions (e.g., adding Strategy pattern, registries, and multiple test files) even after earlier user “recadrage” attempts failed to persist across sessions.
- To counter this, the author added a specific convention to CLAUDE.md: default to the smallest change that fits, and introduce abstractions only after the second occurrence.
- The author details why the exact wording matters—using “Default to” instead of “Avoid” to prevent triggering the model’s counterproductive abstraction reflex, and using “That fits” to focus on meeting requirements rather than aesthetics.
- The guidance “second occurrence, not the third” is a personalized adaptation to solo development workflow, where the second time is the last moment the author remains sharp enough to reconsider abstractions.
- The piece concludes that exceptions should be handled by design (e.g., “Never the first”) but notes the “never” rule may be intentionally strict to prevent internal negotiation during the first decision point.
Continue reading this article on the original site.
Read original →
