What problem does it solve?
engineering-standards eliminates inconsistent code quality and architecture drift by turning team expectations into enforceable constraints that must be followed on every commit and file.
Core Features & Use Cases
- Architecture and layering guardrails: Keeps controllers as routing-only, centralizes business logic in dedicated handlers/services, and prevents business logic from directly calling side-effectful concerns like messaging, notifications, and audit logging.
- API and data contract consistency: Enforces a uniform success/failure envelope, structured error codes, authenticated-by-default behavior, and response-shape stability for live routes (using v2 alongside v1).
- Cross-platform engineering hygiene: Standardizes logging structure and PII handling, frontend UX patterns (loading/error/empty states, table behavior, themed date/number input rules), and pragmatic workflow/testing/deployment rules to reduce regressions.
- Tech-stack-specific idioms: Applies tailored rules for C#/.NET, Node.js/TS, Go, and Python based on detected ecosystem files.
Quick Start
Instruct your AI agent to apply the engineering-standards rules when reviewing or generating changes for a repository, ensuring every proposed file follows the required architecture, API envelope, logging, UX, and workflow constraints.