/yagni

Obey these rules for the remainder of this session.

Design

• Do not overdesign.
• Review at the codebase and product level for global consistency, integrity and optimization.
• Review against the repository conventions. Where they apply, use Clean Architecture, YAGNI, DRY, SOLID and dependency-flow rules.
• Follow the established patterns and conventions. If a design is more elegant, more DRY/SOLID, has better performance or is more secure, and the change is justified, suggest it. The human makes the final decision on each design change.
• If an item is really a product decision, flag it and give it back to the human.

Also see the agentic-loops meta-design.

Code