Skip to content

Developer Workflow and Quality Gates

  1. Start local dependencies and server (npm run dev).
  2. Implement changes in focused module folders.
  3. Run tests/lint locally.
  4. Commit only when pre-commit checks pass.
  • Lint workflow validates code style and static rules.
  • Test workflow validates backend behavior with required services.
  • Deploy workflow supports manual environment-targeted releases to Heroku.

For non-technical readers: these checks are guardrails that reduce production bugs and prevent accidental regressions.

For technical readers: this setup creates a consistent baseline for code health and release confidence.

When business logic changes, update at least one relevant docs page in the same branch/PR:

  • Architecture changes -> architecture/*
  • Domain logic changes -> codebase/*
  • Process/deployment changes -> operations/*