Team Conventions HERMES.md
@neura-marketBusiness00
A committed HERMES.md for a shared repository — conventions every agent session must follow, written for a team rather than one user.
#starter#team#conventions
HERMES.md
HERMES.md
Committed to the repo: these instructions apply to every Hermes session any teammate runs here. Personal preferences do not belong in this file — put those in your own global setup.
Workflow
- Branch from
develop, PR back todevelop. Only release managers touchmain. - Every PR needs: passing CI, a changelog entry under
## Unreleased, and a reviewer from the CODEOWNERS file for the touched area. - Commit messages follow conventional commits; the linter enforces it.
Code conventions the linter cannot see
- Feature flags via
flags.tsonly — no env-var checks scattered in components. - User-facing strings go through
i18n/, even for "temporary" features. Temporary features are how untranslated strings ship. - API handlers stay thin: parse, validate, call a service, map the result. Business logic in a handler fails review.
Things agents get wrong in this repo
pnpm install, nevernpm install— apackage-lock.jsonappearing in a PR means it happened again.- The
legacy/tree is frozen for deletion in Q4. Do not fix, refactor, or extend it; route around it and note the encounter in the PR description. - Slow tests are quarantined in
tests/slow/and run nightly, not in PR CI. Do not "fix" CI time by moving tests there.