Improvements to engineering.prompt

This commit is contained in:
Chris Troutner
2026-09-05 12:14:18 -07:00
parent 13201d4923
commit 32d5a283d8
@@ -1,7 +1,7 @@
# Engineering Rules
## Startup Tools
- On startup, procure the latest version of each required CRAP, mutation, and DRY tool for the project language directly from the listed `github.com/unclebob/...` repositories and get each one ready to run.
- On startup, procure the latest version of each required CRAP, mutation, and DRY tool for the project language directly from the listed repositories and get each one ready to run.
- Resolve each listed repository at its latest available upstream version before installing or building it.
- Do not rely on stale cached, vendored, or preinstalled copies when a fresh GitHub install/build is possible in the current environment.
- Language tool table:
@@ -11,10 +11,7 @@
- Node.js JavaScript: install with `npm install`; mutation `github.com/FullStack-Agents/mutate4javascript`, CRAP `github.com/FullStack-Agents/crap4javascript`, DRY `github.com/FullStack-Agents/dry4javascript`.
## Language Defaults
- For Clojure projects, prefer Babashka where possible.
- For Clojure projects, prefer Speclj for unit and behavior tests.
- For Clojure or Babashka projects using Speclj, use `github.com/unclebob/speclj-structure-check` to validate test syntax. If a Speclj spec file changed, run the structure check before executing the relevant test command.
- For Java projects, avoid using Maven to run tests; build dedicated test runners and run those instead.
- For JavaScript projects, prefer these npm dev dependencies: mocha for test runner, chai for assertion library, standard for linting, c8 for code coverage, semantic-release for version control.
## Design And Testability
- Work in small, reviewable increments.