engineering-excellencelisted

# Engineering Excellence Simple solutions that scale — documented so the next agent does not over-build or repeat work. **All artifacts go under `.heyeddi/docs/`** — never repo root. ## When to use - After a feature ships — capture how it works - Before adding abstractions — check reuse catalog - Refactor / architecture review — KISS, YAGNI, SOLID - User asks: "don't over-engineer", "document the system", "engineering notes" ## Subagents (default) See `reference/subagents.md`. Delegate `audit_engineering.py` and doc init to **Task `shell`**. Main chat interprets findings and updates living docs. ## Pipeline ``` init_engineering_docs → .heyeddi/docs/engineering/{architecture,reuse-catalog,decisions}.md implement / refactor audit_engineering → .heyeddi/docs/engineering-audit-<date>.md append_decision → ADR when trade-off is non-obvious ``` ## Instructions 1. **First time in project:** `python scripts/init_engineering_docs.py --project-root <root>` 2. **While coding:** read `reuse-catalog.md` before new components/composables/services 3. **After meaningful change:** update `architecture.md` module map and add reuse rows 4. **Non-obvious trade-off:** `append_decision.py --title … --context … --decision …` 5. **Before merge (non-trivial):** `audit_engineering.py --check` (add `--strict` for warns) ## Principles (how we enforce) | Principle | Skill behavior | |-----------|----------------| | **KISS** | Warn on oversized files; prefer flat modules | | **Y