Getting Started
Cross-stack rules and conventions applied across all Ozone projects
General Standards define rules that apply to every project, regardless of language, framework, or platform.
These standards exist to keep all Ozone systems consistent, predictable, and easy to collaborate on, especially as teams and products scale.
What’s Covered
- Naming and formatting conventions
- Environment and configuration management
- API design and communication principles
- Shared practices that improve long-term maintainability
Why This Matters
Without shared standards:
- Code becomes inconsistent
- Onboarding takes longer
- Bugs and miscommunication increase
These rules ensure that any engineer can move between projects with minimal context switching.