Engineering excellence

Skill HeyEddi-com/skills/evals/runs/2026-07-04T22-58-59Z/engineering-excellence-audit/.cursor/skills/engineering-excellence

Audits code for KISS, YAGNI, DRY, SOLID, and testability; maintains living engineering notes under .heyeddi/docs/engineering/. Use when refactoring, before merge, or when the user asks for simple scalable design, architecture notes, reuse catalog, or engineering ADRs — not for visual UX (use ux-flow-auditor) or CI gates (use pre-merge-gate).From its SKILL.md

Install

npx -y skills add HeyEddi-com/skills --skill engineering-excellence

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 614 tokens by cl100k_base, as published. Nobody here has run it

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

First time in project: python scripts/init_engineering_docs.py --project-root <root>
While coding: read reuse-catalog.md before new components/composables/services
After meaningful change: update architecture.md module map and add reuse rows
Non-obvious trade-off: append_decision.py --title … --context … --decision …
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
YAGNI	Flag abstraction names without clear reuse
DRY	Maintain `reuse-catalog.md`; chain `@no-duplicate-ui` for UI
SOLID	Warn on fat routers; views thin, services fat
Testable	Note views missing smoke specs

`.heyeddi/` outputs

Path	Purpose
`.heyeddi/docs/engineering/architecture.md`	System map, data flow, boundaries
`.heyeddi/docs/engineering/reuse-catalog.md`	What exists — do not rebuild
`.heyeddi/docs/engineering/decisions.md`	Engineering ADRs (not design log)
`.heyeddi/docs/engineering-audit-<date>.md`	Point-in-time audit report

Design decisions stay in .heyeddi/design.md Decision log — do not mix.

Chain

@project-engineering — scaffold first
@composable-patterns / @backend-type-bridger — after architecture notes exist
@pre-merge-gate — final CI; this skill is advisory + docs

What ships with it: 11 files

18.0 KB alongside SKILL.md, 5 of them executable

context/

reference/

subagents.md371 B

scripts/

manifest.json1.7 KB