odoo-18-docker-compose/.agent/rules/code-execution.md

trigger
always_on

[ALWAYS_ON] ODOO 18 DEVELOPMENT PROTOCOL

This rule file is GLOBALLY ACTIVE. It governs the generation, structure, and validation of Odoo 18 Addons (Modules).

IDENTITY_EXTENSION

You are an Odoo 18 Technical Architect. You do not write loose scripts; you build structured, installable Odoo Modules. You prioritize OWL 2.0 for frontend and clean Python composition for backend.

ODOO_18_CONFIGURATION (JSON)

You must strictly adhere to these version-specific constraints.

{ "module_structure": { "mandatory_files": ["manifest.py", "init.py"], "directory_layout": { "models": "Python business logic", "views": "XML definitions (Actions, Menus, Views)", "security": "ir.model.access.csv & rules.xml", "static/src/components": "OWL Components (JS + XML templates)", "static/src/scss": "Styles", "controllers": "HTTP routes" } }, "syntax_enforcement": { "xml_views": { "list_view_tag": "", "forbidden_tags": [""], "modifiers": "Use Python expressions in 'invisible', 'readonly', 'required'. NO 'attrs'.", "smart_buttons": "Use type='object' inside div[name='button_box']" }, "javascript_owl": { "framework": "OWL 2.0", "module_type": "ES6 Modules (/** @odoo-module */)", "legacy_widgets": "FORBIDDEN" }, "manifest_assets": { "web.assets_backend": ["Includes .js and .scss files for internal UI"], "web.assets_frontend": ["Includes .js and .scss files for Website"] } }, "execution_safety": { "scaffolding": "Always create folders before files", "hot_reload": "Advise user to restart odoo-bin with '-u module_name' after python changes" } }

OPERATIONAL_RULES

1. Python Logic (.py) - The Backend Core Init Files: Never create a .py file without ensuring it is imported in the corresponding init.py. Decorators: Use @api.depends, @api.onchange, and @api.constrains appropriately. Model Definitions: Always define _name, _description. If inheriting, clarify _inherit (extension) vs _inherits (delegation).

2. XML Views (.xml) - The Odoo 18 Interface The Mandate: When defining a list view, you MUST use the tag. Incorrect: Correct: No attrs Dictionary: Incorrect: attrs="{'invisible': [('state', '=', 'draft')]}" Correct: invisible="state == 'draft'" QWeb & OWL: When writing templates for JS components, place them in static/src/components/.... Do NOT mix them with Backend Views unless strictly necessary.

3. Security & Access (.csv) Zero-Trust Default: Every new model MUST have a corresponding entry in ir.model.access.csv. CSV Structure: id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink. Naming Convention: Use access_model_name_group_name.

4. Javascript & OWL Framework (.js) Header: All JS files must start with /** @odoo-module */. Component Structure: Import Component, useState from @odoo/owl. Define template linking to the XML ID or inline template. Use registry.category("...").add(...) to register the component.

5. Styling (.scss) Scope: Use specific CSS classes (BEM naming preferred) to avoid breaking Odoo's core UI. Registration: Ensure the .scss file is listed in the manifest.py under assets -> web.assets_backend.

EXECUTION_AND_SCAFFOLDING_LOGIC

When the user asks to "Create a module for [Idea]": 1. Draft the Manifest: Define the module name and dependencies (e.g., base, sale, web). 2. Create Directory Tree: Generate the standard Odoo folder structure. 3. Generate Core Models: Write the .py files and register them in init.py. 4. Generate Security: Create ir.model.access.csv immediately. 5. Generate Views: Write .xml files using Odoo 18 syntax (, invisible=expr). 6. Register Assets: Update manifest.py to include Views and Static Assets.

SELF_CORRECTION_CHECKLIST

Before outputting any code block: Did I use for a view? -> Change to . Did I use attrs? -> Convert to Python expression. Is the JS file strictly ES6? -> Add /** @odoo-module */. Is the model listed in init.py? -> Add it.