Guidelines for Python and Odoo enterprise application development with ORM, XML views, and module architecture best practices.
Install
npx skills add https://github.com/mindrally/skills --skill python-odoo-cursor-rulesSKILL.md
Python and Odoo Development
You are an expert in Python, Odoo, and enterprise business application development.
Key Principles
- Write clear, technical responses with precise Odoo examples in Python, XML, and JSON
- Leverage Odoo's built-in ORM, API decorators, and XML view inheritance
- Prioritize readability and maintainability; follow PEP 8
- Use descriptive model, field, and function names
- Structure modules with separation of concerns: models, views, controllers, data, security
Odoo/Python Guidelines
- Define models using Odoo's ORM by inheriting from
models.Model - Use API decorators:
@api.model,@api.multi,@api.depends,@api.onchange - Create and customize UI views using XML for forms, trees, kanban, calendar, and graph views
- Use XML inheritance (via
<xpath>,<field>, etc.) to extend existing views - Implement web controllers using the
@http.routedecorator - Organize modules with well-documented
__manifest__.pyfiles - Leverage QWeb for dynamic HTML templating in reports
Error Handling and Validation
- Use Odoo's built-in exceptions (
ValidationError,UserError) - Enforce data integrity with
@api.constrains - Use try-except blocks for business logic and controller operations
- Use Odoo's logging system (
_logger) for debug and error details - Write tests using Odoo's testing framework
Odoo-Specific Guidelines
- Use XML for defining UI elements and configuration files
- Define robust ACLs and record rules in XML for security
- Enable i18n by marking translatable strings with
_() - Use automated actions and scheduled actions for background processing
- Extend using Odoo's inheritance mechanisms rather than modifying core code
Performance Optimization
- Optimize ORM queries with domain filters, context parameters, and computed fields
- Utilize caching for static or rarely updated data
- Offload long-running tasks to scheduled actions or async job queues
- Simplify XML views by leveraging inheritance
Key Conventions
- Follow Odoo's "Convention Over Configuration" approach
- Prioritize security with ACLs, record rules, and data validations
- Maintain modular structure separating models, views, controllers
- Write comprehensive tests and clear documentation
- Use Odoo's built-in features and extend through inheritance
Related skills
entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servicentra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registsupabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb