@base44/app-plugin-commerce 0.6.0 → 0.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@base44/app-plugin-commerce",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "Base44 Commerce plugin — entities, backend functions, shared commerce engine, admin UI and the commerce skill, shipped as copyable source",
   "keywords": [
     "base44",

package/skills/commerce/SKILL.md

@@ -22,10 +22,12 @@ the file that mentioned them.
 
 ## Installing right now?
 
-Read **[`install/01-install.md`](./install/01-install.md)** and follow it. It
-routes you to `install/02-storefront.md` when you start the UI and
-`install/03-data.md` when you seed the catalog — in that order, at those
-moments. Read nothing else up front.
+Read all three stages **in one turn** — [`install/01-install.md`](./install/01-install.md),
+[`install/02-storefront.md`](./install/02-storefront.md),
+[`install/03-data.md`](./install/03-data.md) — then work them in that order:
+install, then the storefront UI, then the catalog. Every install runs all three,
+so fetching them one at a time defers nothing you will not read anyway and costs
+a model round trip per file. Read nothing *else* up front.
 
 ## Four things to hold from the start
 
@@ -109,7 +111,9 @@ const { products, has_next } = res.data.data;
 
 ## Where to look for what
 
-Open a file when its work starts — not while planning.
+Open a file when its work starts — not while planning. The exception is the
+three `install/` stages: an install reads all of them, so they come as one
+batch (above).
 
 | Topic | Open when | Size |
 |---|---|---|
@@ -132,10 +136,13 @@ Open a file when its work starts — not while planning.
 | [`docs/api-admin.md`](./docs/api-admin.md) | changing admin pages, automating admin functions, the full seed contract | 24K |
 
 **The read budget.** Content you pull into context is re-read on every later
-call, so a file opened while planning costs many times what it costs opened at
-the moment it is used. Open one reference when its task starts, take what you
-need, and when a stage's checklist passes, record its carry-forward lines and
-treat the file as gone.
+call, so a file you *might* not need costs many times more when opened while
+planning than at the moment it is used. That is the rule for `references/` and
+`docs/`: open one when its task starts, take what you need, and when a stage's
+checklist passes, record its carry-forward lines and treat the file as gone.
+Deferring is worth a round trip only when it might save the read entirely — so
+it is the wrong instinct for the three install stages, which every install
+reads. Batch those.
 
 **The install stages are self-contained.** Every request and response shape they
 build against is written out in them — `install/02-storefront.md` carries a table