python-odoo-cursor-rules
Guidelines for Python and Odoo enterprise application development with ORM, XML views, and module architecture best practices.
What this skill does
# 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.route` decorator - Organize modules with well-documented `__manifest__.py` files - 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 1. Follow Odoo's "Convention Over Configuration" approach 2. Prioritize security with ACLs, record rules, and data validations 3. Maintain modular structure separating models, views, controllers 4. Write comprehensive tests and clear documentation 5. Use Odoo's built-in features and extend through inheritance
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.