Create a code style guide

Create a code style guide for a [Language] engineering team. Cover the following areas with concrete examples for each: naming conventions for variables, functions, classes, constants, and files; preferred file and module organisation patterns; comment and documentation standards; preferred code patterns such as functional versus object-oriented, synchronous versus async, error handling style; a list of patterns or anti-patterns the team has explicitly decided to avoid and why; and the tooling setup including linter and formatter configuration that automatically enforces the guide so reviews can focus on logic rather than style.