clean-code

From README

Clean Code Principles These principles apply to ALL code Bee produces, evaluates, or cleans up — regardless of architecture pattern, language, or framework. They are non-negotiable defaults. The target project's CLAUDE.md may add project-specific conventions on top of these. YAGNI — You Aren't Gonna Need It Don't build what nothing asks for. Before writing any code, abstraction, or interface, ask: does a test or acceptance criterion require this RIGHT NOW? One implementation? Skip the interface. Extract the interface when a second implementation actually arrives. No test demands it? Don't build it. "Might need it someday" is not a reason. Unused parameters, empty extension points, commented-out feature flags — all YAGNI violations. Remove them. DRY — Don't Repeat Yourself Every piece of knowledge should have a single, authoritative representation. Extract on the third occurrence, not the second. Two similar blocks might be coincidence. Three means there's a pattern.