Structuring the Claude "Odoo" project: ecosystem reference docs

Context

The Claude project dedicated to Odoo was empty (just logos and brand guidelines). What was missing was a reference document consolidating all validated technical connections so every conversation could start with the right context without having to re-explain everything.

What was built

• cobra_connexions_ecosysteme.md — 165 lines: Odoo SaaS instance, GitHub, Shopify, Irokoo, local tools, snapshot of the 9 custom modules, CDC numbering, autonomy strategy
• A ready-to-use prompt to kick off the conversation on cobra_field_security (CDC-18)
• Validated recommendation: keep everything in the existing Odoo project

What was tricky

• The Odoo SaaS vs Odoo.sh distinction needed to be spelled out in black and white
• The "ship as much as possible without Irokoo" strategy shifts the default reflex (native Odoo first, CDC as a last resort)

Stack

Markdown, Claude project (knowledge base), conversation memory.

What this illustrates

Claude as the architect of its own project knowledge base. The "structuring session" pattern before diving into development: often pays for itself by the very next session.