Imported from khoadd879/odoo_testing (
AGENTS.md). Install upstream withnpx skills add khoadd879/odoo_testing. Copyright stays with the author.
AGENTS.md — Fashion eCommerce
Binding instructions for coding agents working in this repository. The repo is the source of truth; read the active feature docs before changing code and update them whenever scope changes.
1. Project identity
| Field | Value |
|---|---|
| Project | Fashion eCommerce |
| Odoo version | 19.0 |
| Docker project | odoo_fashion |
| Database | fashion_store |
| Host URL | http://localhost:8070 |
| Odoo ports | host 8070 → 8069; host 8073 → 8072 |
| Custom addons | ./custom_addons |
| Active module | fashion_ecommerce |
| Repo root | /home/khoa/Company/odoo_testing |
Never touch the legacy project at /home/khoa/Company/odoo.
Never use its compose project, network, volumes, filestore, or ports.
2. Architecture boundary
Native Odoo modules own products, variants, carts, checkout, orders, payments, delivery, stock, portal, and website editing. Custom code may extend those modules but must not replace their core flows.
The fashion_ecommerce module owns only:
- storefront branding and homepage QWeb;
- project SCSS and owned static assets;
- public product categories;
- size/color attributes and reproducible starter products.
AI chatbot and CRM lead automation are out of scope until the native eCommerce purchase flow is complete.
3. Workflow rules
- Read
docs/PROGRESS.mdand the active feature indocs/FEATURE_LIST.jsonbefore changing code. - Work on one independently verifiable feature at a time.
- Prefer native Odoo 19 and compatible OCA modules over custom logic.
- Never patch Odoo core.
- Preserve unrelated user changes.
- Verify real behavior before claiming completion.
- Update
docs/PROGRESS.mdanddocs/FEATURE_LIST.jsonwith fresh evidence. - Before deleting project-owned Docker volumes, create and verify an
offline backup. Only
odoo_fashion_dbandodoo_fashion_dataare in scope.
4. Definition of done
A feature is done only when:
- code/config is committed in this repo;
docker compose -p odoo_fashion up -dsucceeds;- the relevant module install/update succeeds;
/and/shopreturn HTTP 200 when storefront work is involved;- no new traceback or critical log entry exists;
- every acceptance criterion has fresh evidence;
./scripts/agent_check.shexits 0;- progress and feature-list docs are current.
5. Approved commands
docker compose -p odoo_fashion up -d
docker compose -p odoo_fashion stop
docker compose -p odoo_fashion ps
docker compose -p odoo_fashion logs --tail=200 odoo
./scripts/update-module.sh fashion_ecommerce
./scripts/update-module.sh fashion_ecommerce --install
./scripts/agent_check.sh
Do not run docker compose down against the legacy project. Do not
delete broad directories or volumes. Use exact project-owned targets.
6. When blocked
Capture the failing command and full relevant error. Record the
blocker in docs/PROGRESS.md, fix the smallest root cause first, and
do not mark the feature done while the blocker remains.