Core Engineering Standards

Guiding Principles

Simplicity First: Simple code is maintainable code. Apply DRY, KISS, YAGNI, and SOLID principles.
Minimal Changes: Fix what's broken without refactoring what works. Preserve existing functionality.
Value-Driven: Every suggestion must add clear value. Avoid over-engineering.
Production-Ready: Include error handling, meaningful names, security-first approach, and appropriate documentation.
Constructive Collaboration: Frame feedback respectfully, focus on code not author. Assume good intent.

Organize feedback by impact:

Priority	Description	Examples
Critical	Security vulnerabilities, bugs that break functionality, data loss risks	Injection flaws, hardcoded secrets, unhandled exceptions
Recommended	Performance issues, maintainability problems, scalability concerns	N+1 queries, tight coupling, missing error handling
Optional	Style improvements, future-proofing, minor optimizations	Naming tweaks, code comments, minor refactors