Using Your Project as Context to Set Up .dinorules

​

Example Prompt

Analyze my selected dbt™ project files and create a .dinorules that capture my existing SQL formatting, naming conventions, folder structure, and documentation patterns.

​

Step-by-Step Instructions

1. Open DinoAI by clicking the DinoAI icon (🪄) in the right panel
2. Select Agent Mode if it’s not already selected
3. Add files as context using the ”@” icon in the DinoAI panel. Select representative files from different folders:
   1. Staging models (e.g., stg_customers.sql, stg_orders.sql)
   2. Intermediate models (e.g., int_customer_orders.sql)
   3. Marts models (e.g., dim_customers.sql, fct_sales.sql)
   4. Your dbt_project.yml file
   5. Existing schema.yml files from each folder
4. Enter your prompt requesting .dinorules creation based on selected files
5. Review the generated .dinorules file preview
6. Accept the changes to create the file in your project root
7. Test the rules by generating new models to ensure they follow the established patterns

​

Example Output

Project Context
- Domain: E-commerce analytics
- Data Stack: dbt™ with Snowflake
- Project Structure: source → staging → intermediate → marts hierarchy

SQL Formatting Standards (Based on Analyzed Files)
- Keywords: Always uppercase (SELECT, FROM, WHERE, etc.)
- Indentation: 4 spaces, no tabs
- Comma Style: Trailing commas in SELECT statements
- Aliasing: Always alias tables (use 'u' for users, 'o' for orders)
- CTEs: Prefer CTEs over subqueries for readability
- Comments: Add comments for complex business logic

Naming Conventions (Extracted from Current Models)
- Models: snake_case with prefixes (stg_, int_, dim_, fct_)
- Columns: snake_case, descriptive names
- Tables: Singular nouns (user, not users)
- Primary Keys: Always end with '_id' (user_id, order_id)

Folder Structure and Materializations
- staging/: Views only, basic transformations
- intermediate/: Views, complex business logic
- marts/: Tables or incremental, final business models
- All models tagged by domain and layer

Documentation Requirements
- All models require descriptions
- Business-critical columns need descriptions
- Primary keys need unique and not_null tests
- Foreign keys need relationships tests

Business Logic Patterns
- Always use UTC for timestamps
- Standardize null handling with COALESCE
- Use consistent date formatting (YYYY-MM-DD)
- Apply consistent rounding rules (2 decimal places for currency)

Quality Standards
- All models must compile without warnings
- Use consistent test patterns across similar model types
- Maintain referential integrity through proper testing

​

How It Works

1. File Analysis: DinoAI analyzes the structure and patterns in your selected files
2. Pattern Recognition: It identifies consistent naming conventions, SQL formatting styles, and organizational patterns
3. Rule Generation: It creates a .dinorules file that codifies these discovered patterns
4. Standard Application: The generated rules ensure future AI-generated code matches your established standards

​

Key Benefits

• Consistency: Ensures all future AI-generated code matches your existing standards
• Team Alignment: Codifies implicit knowledge that experienced team members understand
• Efficiency: Creates comprehensive rules without starting from scratch

• New Project Setup: Establish standards when transitioning from manual to AI-assisted development
• Team Onboarding: Document implicit conventions for new team members
• Standard Formalization: Convert organic patterns into explicit rules