Skip to content

Team Engineering Playbook

Internal Use Only | Standard operating procedures, architecture decisions, and onboarding guides.

To contribute to this guide, please create a new .md file in this directory and link it in the table above.

  1. Branching: Use feature/ticket-id naming.
  2. Commits: Follow Conventional Commits (e.g., feat:, fix:, docs:).
  3. Reviews: At least one peer approval required before merging to main.
  • DevOps/Infra: [Name/Slack Channel]
  • Security: [Name/Slack Channel]