theme-create
Odoo theme scaffolding and creation pipeline. Generates complete, installable Odoo theme modules with proper file structure, SCSS configuration, page templates, mirror models, theme.utils activation, and auto-fix installation. Supports Odoo 14-19. <example> Context: User wants to create a new Odoo website theme user: "Create a new website theme for Odoo 17" assistant: "I will use the theme-create skill to scaffold a complete theme module." <commentary>Core trigger - new theme creation.</commentary> </example> <example> Context: User wants to scaffold a theme from Figma user: "Build an Odoo 17 theme from this Figma design" assistant: "I will scaffold the theme module and extract design tokens from Figma." <commentary>Theme creation with Figma extraction.</commentary> </example> <example> Context: User wants mirror models for multi-website user: "Create theme mirror models for my website pages" assistant: "I will generate theme.ir.ui.view and theme.website.page records." <commentary>Mirror model generation.</commentary> </example> <example> Context: User wants to fix a broken theme installation user: "My theme won't install, I get an undefined variable error" assistant: "I will diagnose the SCSS load order issue and fix the map-merge pattern." <commentary>Theme installation debugging.</commentary> </example>
What this skill does
# Theme Creation Skill
## Critical Rules
1. **NEVER modify core Odoo** in `odoo/` or `odoo/addons/`
2. **NEVER use `map-merge()`** with core Odoo variables in theme SCSS — they're undefined at load time
3. **NEVER use `ir.asset`** records for Google Fonts — use `$o-theme-font-configs`
4. **ALWAYS use `('prepend', ...)`** for primary_variables.scss in asset bundles
5. **H6 is ALWAYS 16px** (1rem) — the fixed base reference
6. All manifests must include `author: 'TaqaTechno'`, `website`, `support`, `license: 'LGPL-3'`
## Generated Theme Structure (v8.0)
```
theme_<name>/
├── __init__.py # Imports models
├── __manifest__.py # With proper asset bundles
├── models/
│ ├── __init__.py # Imports theme_<name>
│ └── theme_<name>.py # theme.utils implementation (REQUIRED!)
├── security/
│ └── ir.model.access.csv
├── data/
│ ├── assets.xml # Minimal (fonts via SCSS, not ir.asset!)
│ ├── menu.xml
│ └── pages/ # Individual page files (best practice)
│ ├── home_page.xml # Inherits website.homepage
│ ├── aboutus_page.xml # theme.website.page
│ ├── contactus_page.xml # Inherits website.contactus
│ └── services_page.xml # theme.website.page
├── views/
│ ├── layout/
│ │ └── templates.xml # Base layout templates
│ └── snippets/
│ └── custom_snippets.xml
└── static/src/
├── scss/
│ ├── primary_variables.scss # Theme variables + font configs
│ └── theme.scss # Additional custom styles
├── js/
│ └── theme.js # publicWidget implementations
└── img/
```
## Manifest Template
```python
{
'name': 'Theme <Name>',
'version': '<odoo_version>.0.1.0.0',
'category': 'Theme/Creative',
'summary': 'Custom theme for <client>',
'author': 'TaqaTechno',
'website': 'https://www.taqatechno.com/',
'support': '[email protected]',
'license': 'LGPL-3',
'depends': ['website'],
'data': [
'security/ir.model.access.csv',
'views/layout/templates.xml',
'views/snippets/custom_snippets.xml',
'data/menu.xml',
'data/pages/home_page.xml',
'data/pages/aboutus_page.xml',
'data/pages/contactus_page.xml',
],
'assets': {
'web._assets_primary_variables': [
('prepend', 'theme_<name>/static/src/scss/primary_variables.scss'),
],
'web.assets_frontend': [
'theme_<name>/static/src/scss/theme.scss',
'theme_<name>/static/src/js/theme.js',
],
},
'installable': True,
'auto_install': False,
'application': False,
}
```
## SCSS Load Order (Critical)
```
1. YOUR theme's primary_variables.scss (via 'prepend') ← FIRST
2. Odoo core primary_variables.scss ← SECOND
3. Other SCSS files
CONSEQUENCE:
- CANNOT use map-merge() with core variables (they don't exist yet!)
- MUST define standalone variables
- Use 'color-palettes-name': 'default-1' to reference existing palettes
WRONG: $o-color-palettes: map-merge($o-color-palettes, (...));
RIGHT: $o-website-values-palettes: ( ( 'color-palettes-name': 'default-1' ) );
```
## primary_variables.scss Template
```scss
// ===================================================================
// Theme: <Name> — Generated by TaqaTechno
// PREPENDED before Odoo core — DO NOT use map-merge()!
// ===================================================================
// === Font Configuration (STANDALONE) ===
$o-theme-font-configs: (
'Inter': (
'family': ('Inter', sans-serif),
'url': 'Inter:300,300i,400,400i,500,500i,600,600i,700,700i',
),
);
// === Website Values Palette (MASTER CONFIGURATION) ===
$o-website-values-palettes: (
(
'color-palettes-name': 'default-1',
// Typography
'font': 'Inter',
'headings-font': 'Inter',
'navbar-font': 'Inter',
'buttons-font': 'Inter',
// Header (NO custom header.xml needed!)
'header-template': 'default',
'header-links-style': 'default',
'logo-height': 3rem,
'fixed-logo-height': 2rem,
// Buttons
'btn-padding-y': 0.45rem,
'btn-padding-x': 1.35rem,
'btn-border-radius': 0.25rem,
// Footer (NO custom footer.xml needed!)
'footer-template': 'default',
'footer-scrolltop': true,
// Links & Layout
'link-underline': 'hover',
'layout': 'full',
)
);
// === Typography Multipliers ===
$o-theme-h1-font-size-multiplier: (64 / 16); // 64px
$o-theme-h2-font-size-multiplier: (48 / 16); // 48px
$o-theme-h3-font-size-multiplier: (32 / 16); // 32px
$o-theme-h4-font-size-multiplier: (24 / 16); // 24px
$o-theme-h5-font-size-multiplier: (20 / 16); // 20px
$o-theme-h6-font-size-multiplier: (16 / 16); // 16px (FIXED)
```
## Page Creation Patterns
### Homepage (inherits website.homepage)
```xml
<template id="view_home" inherit_id="website.homepage" name="Home">
<xpath expr="//div[@id='wrap']" position="replace">
<div id="wrap" class="oe_structure">
<!-- Homepage content -->
</div>
</xpath>
</template>
```
### Contact (inherits website.contactus)
```xml
<template id="view_contact" inherit_id="website.contactus" name="Contact">
<xpath expr="//h1" position="replace">
<h1>Get in Touch</h1>
</xpath>
</template>
```
### Custom Pages (theme.website.page)
```xml
<template id="view_about" name="About">
<t t-call="website.layout">
<div id="wrap" class="oe_structure">
<section class="s_title pt96 pb48">
<div class="container"><h1>About Us</h1></div>
</section>
</div>
</t>
</template>
<record id="page_about" model="theme.website.page">
<field name="view_id" ref="view_about"/>
<field name="is_published" eval="True"/>
<field name="url">/about</field>
</record>
```
## Theme Mirror Model Architecture
```
theme.ir.ui.view (Template) → ir.ui.view (Actual, with website_id)
theme.website.page (Template) → website.page (Actual, with website_id)
```
Each website gets independent copies, enabling theme reuse across multiple sites.
## theme.utils Activation (REQUIRED)
Every theme MUST include `models/theme_<name>.py`:
```python
from odoo import models
class Theme<Name>(models.AbstractModel):
_inherit = 'theme.utils'
def _theme_<name>_post_copy(self, mod):
"""Called automatically when theme is installed on a website."""
# Enable header template
self.enable_view('website.template_header_default')
# Enable footer template
self.enable_view('website.template_footer_contact')
# Show logo, not brand name
self.enable_view('website.option_header_brand_logo')
self.disable_view('website.option_header_brand_name')
```
**Method name MUST be** `_theme_{technical_name}_post_copy` where technical_name matches the folder name.
**Available methods**: `enable_view(xml_id)`, `disable_view(xml_id)`, `enable_asset(xml_id)`, `disable_asset(xml_id)`
## Installation & Testing
```bash
# 1. Update module list
python -m odoo -c conf/<PROJECT>.conf -d <DB> --update-list
# 2. Install theme
python -m odoo -c conf/<PROJECT>.conf -d <DB> -i theme_<name> --stop-after-init
# 3. If errors, auto-fix and retry (up to 3 attempts)
```
### Common Auto-Fix Patterns
| Error | Fix |
|-------|-----|
| `Undefined variable "$o-color-palettes"` | Remove map-merge, use standalone |
| `Undefined variable "$o-theme-font-configs"` | Define standalone (no map-merge) |
| `SyntaxError in SCSS` | Parse error location, fix syntax |
| `Module not found` | Add dependency to manifest |
| `Malformed Google Fonts @import` | Remove ir.asset, use $o-theme-font-configs |
### Testing Checklist
- [ ] Theme installs without errors
- [ ] CSS compilation succeeds
- [ ] No SCSS/JS errors in bRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.