Searching protocol for "over-engineering"
Keep complexity in check with pragmatism.
Keep it simple: KISS, YAGNI, and clear design.
Spot over-engineering before it hits production.
Keep code practical: validate designs, cut waste.
Maintain clean, reliable code with quality gates.
Systematic plan reviews to cut design risk.
Write concise, maintainable code.
Keep code simple during reviews.
Build robust, non-over-engineered APIs.
Critique system architecture
Enhance code quality and efficiency.
Audit TypeScript types for design debt.