The house engineering standards bar. Use whenever code is being written, reviewed, or refactored to ensure conformance to KISS / DRY / SOLID / YAGNI principles, package/module boundaries, naming conventions, error-handling discipline, logging hygiene, and dependency direction. Every implementation skill, code-review pass, and developer agent reads this — it is the single source of truth for the engineering bar. Pushy trigger because skills tend to under-trigger on standards.