Rules Library

- Always use CTEs for complex queries
- Use snake_case for all table and column names
- Include comments explaining business logic
- Prefer explicit JOINs over implicit joins
- Use meaningful aliases for tables

- Follow dbt style guide for model structure
- Always include model documentation
- Use ref() instead of direct table references
- Group related models in the same folder
- Include tests for critical models

- Follow PEP 8 style guide
- Use type hints for function parameters
- Include docstrings for all functions
- Maximum line length: 100 characters

- Write self-documenting code
- Keep functions focused and small
- Use descriptive variable names
- Comment complex business logic

- Always include README.md in new projects
- Document all environment variables
- Keep changelog updated
- Write clear commit messages

- Create feature branches for all changes
- Run tests before committing
- Review code before merging
- Update documentation with code changes

- Always validate data types
- Check for null values in critical columns
- Include data quality tests in dbt models
- Document data sources and transformations

- Use consistent metric definitions
- Document calculation methods
- Include time zone information in date fields
- Validate results against known benchmarks