engineering-excellence
Skill0 starsChanged 3 months agoMITView on GitHub
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).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 2867203296/hermes-agenttheir own version, first seen Aug 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 2867203296/hermes-agent★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- .cursor/rules/skill-authoring.mdcCursor rule
- backend-type-bridgerSkill
- composable-patternsSkill
- dart-type-bridgerSkill
- design-handoff-flutterSkill
- design-system-generalizerSkill
- flutter-engineeringSkill
- flutter-patternsSkill
- heyeddi-designSkill
- heyeddi-handoffSkill
- heyeddi-intakeSkill
- heyeddi-orchestratorSkill
- heyeddi-productSkill
- heyeddi-pr-respondSkill
- heyeddi-pr-reviewSkill
- no-duplicate-uiSkill
- pre-merge-gateSkill
- primevue-openprops-architectSkill
- project-engineeringSkill
- ux-flow-auditorSkill
- verify-buildSkill
- visual-auditorSkill
- backend-type-bridgerSkill
- composable-patternsSkill
- dart-type-bridgerSkill
- design-handoff-flutterSkill
- design-system-generalizerSkill
- engineering-excellenceSkill
- flutter-engineeringSkill
- flutter-patternsSkill
- heyeddi-ci-configSkill
- heyeddi-ci-failsSkill
- heyeddi-ci-guideSkill
- heyeddi-ci-runnersSkill
- heyeddi-designSkill
- heyeddi-handoffSkill
- heyeddi-intakeSkill
- heyeddi-orchestratorSkill
- heyeddi-productSkill
- heyeddi-pr-respondSkill
- heyeddi-pr-reviewSkill
- heyeddi-setupSkill
- heyeddiSkill
- no-duplicate-uiSkill
- pre-merge-gateSkill
- primevue-openprops-architectSkill
- project-engineeringSkill
- taste-penpotSkill
- ux-flow-auditorSkill
- verify-buildSkill
- visual-auditorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
All artifacts go under
.heyeddi/docs/: never repo root. - Distinctive: line 15
After a feature ships: capture how it works
- Distinctive: line 16
Before adding abstractions: check reuse catalog
- Very specific: line 36
While coding: read reuse-catalog.md before new components/composables/services
- Very specific: line 37
After meaningful change: update architecture.md module map and add reuse rows
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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-obviousInstructions
- First time in project:
python scripts/init_engineering_docs.py --project-root <root> - While coding: read
reuse-catalog.mdbefore new components/composables/services - After meaningful change: update
architecture.mdmodule map and add reuse rows - Non-obvious trade-off:
append_decision.py --title … --context … --decision … - Before merge (non-trivial):
audit_engineering.py --check(add--strictfor 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

