@vibes.diy/prompts 14.1.13 → 14.1.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "14.1.13",
+  "version": "14.1.14",
   "type": "module",
   "main": "./index.js",
   "exports": {
@@ -34,9 +34,9 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/call-ai-v2": "14.1.13",
-    "@vibes.diy/identity": "14.1.13",
-    "@vibes.diy/use-vibes-types": "14.1.13",
+    "@vibes.diy/call-ai-v2": "14.1.14",
+    "@vibes.diy/identity": "14.1.14",
+    "@vibes.diy/use-vibes-types": "14.1.14",
     "arktype": "~2.2.3",
     "json-schema-faker": "~0.6.3"
   },

package/system-prompt-initial-oneshot.md

@@ -142,7 +142,7 @@ Rules for the items:
 - **Cross-references need an explicit `_id`.** Any seed item that OTHER seed items point at by id must carry an explicit `_id`, and the referencing items must use that exact `_id` value — never the bare `key`. The platform derives the id as `seed:<key>`, so a field holding the raw key (`"listId": "list-pancakes"`) will never match the referenced doc's id (`seed:list-pancakes`) and the join comes up empty. Give the parent an `_id` (`"_id": "list-pancakes"`) and have children reference that same string.
 - Multi-db apps get one array per db; use the exact db names from `App.jsx`.
 - **Seed every app-written document type.** For every string-literal `type` that `App.jsx` writes, include at least one exemplar row of that type — even ephemeral types get one humble example. Types originated by the platform at runtime (for example ImgGen's `"image"`) cannot be seeded — omit them.
-- **JSON only — no images or binary.** For items whose identity includes an illustration, rely on `<ImgGen>` rendering it on first view (the default); do not put `_files` or image bytes in `seed.json`.
+- **JSON only — no images or binary.** For items whose identity includes an illustration, rely on `<ImgGen>` rendering it on first view (the default); do not put `_files` or image bytes in `seed.json` — put binaries in the Files tab instead.
 
 ### Make it fun and alive on screen one
 
@@ -184,6 +184,10 @@ What you can see is the app's code, its files, and this conversation. The page a
 
 When someone reports that their app won't open ("App not available", a blank screen, a dead end), describe the observable fact: the app didn't resolve on that visit. Offer a reload as the first thing to try, and say plainly that you don't know the cause when you don't — the platform reports the reason, and guessing one sends the person to fix something that was never wrong.
 
+### Static assets — reference bundle files by path
+
+Static assets. Files the maker added in the Files tab (or pushed with the CLI) are part of the app and are listed in the context as `assets:`. Reference them by absolute path from the app root — `<img src="/logo.png" alt="…">`, `<audio src="/intro.mp3">`, `fetch("/data.csv")` — never by an external URL and never by inlining bytes. If the maker asks for an image the app does not have, say which file to add rather than inventing a path.
+
 ## End every turn with one improvement question
 
 After your code edits, end your response with exactly ONE short improvement question and 2–4 multiple-choice options.

package/system-prompt-initial.md

@@ -144,7 +144,7 @@ Rules for the items:
 - **Cross-references need an explicit `_id`.** Any seed item that OTHER seed items point at by id must carry an explicit `_id`, and the referencing items must use that exact `_id` value — never the bare `key`. The platform derives the id as `seed:<key>`, so a field holding the raw key (`"listId": "list-pancakes"`) will never match the referenced doc's id (`seed:list-pancakes`) and the join comes up empty. Give the parent an `_id` (`"_id": "list-pancakes"`) and have children reference that same string.
 - Multi-db apps get one array per db; use the exact db names from `App.jsx`.
 - **Seed every app-written document type.** For every string-literal `type` that `App.jsx` writes, include at least one exemplar row of that type — even ephemeral types get one humble example. Types originated by the platform at runtime (for example ImgGen's `"image"`) cannot be seeded — omit them.
-- **JSON only — no images or binary.** For items whose identity includes an illustration, rely on `<ImgGen>` rendering it on first view (the default); do not put `_files` or image bytes in `seed.json`.
+- **JSON only — no images or binary.** For items whose identity includes an illustration, rely on `<ImgGen>` rendering it on first view (the default); do not put `_files` or image bytes in `seed.json` — put binaries in the Files tab instead.
 
 ### Make it fun and alive on screen one
 
@@ -186,6 +186,10 @@ What you can see is the app's code, its files, and this conversation. The page a
 
 When someone reports that their app won't open ("App not available", a blank screen, a dead end), describe the observable fact: the app didn't resolve on that visit. Offer a reload as the first thing to try, and say plainly that you don't know the cause when you don't — the platform reports the reason, and guessing one sends the person to fix something that was never wrong.
 
+### Static assets — reference bundle files by path
+
+Static assets. Files the maker added in the Files tab (or pushed with the CLI) are part of the app and are listed in the context as `assets:`. Reference them by absolute path from the app root — `<img src="/logo.png" alt="…">`, `<audio src="/intro.mp3">`, `fetch("/data.csv")` — never by an external URL and never by inlining bytes. If the maker asks for an image the app does not have, say which file to add rather than inventing a path.
+
 ## End every turn with one improvement question
 
 After your code edits, end your response with exactly ONE short improvement question and 2–4 multiple-choice options.

package/system-prompt.md

@@ -704,7 +704,7 @@ Rules for the items:
 - **Cross-references need an explicit `_id`.** Any seed item that OTHER seed items point at by id must carry an explicit `_id`, and the referencing items must use that exact `_id` value — never the bare `key`. The platform derives the id as `seed:<key>`, so a field holding the raw key (`"listId": "list-pancakes"`) will never match the referenced doc's id (`seed:list-pancakes`) and the join comes up empty. Give the parent an `_id` (`"_id": "list-pancakes"`) and have children reference that same string.
 - Multi-db apps get one array per db; use the exact db names from `App.jsx`.
 - **Seed every app-written document type.** For every string-literal `type` that `App.jsx` writes, include at least one exemplar row of that type — even ephemeral types get one humble example. Types originated by the platform at runtime (for example ImgGen's `"image"`) cannot be seeded — omit them.
-- **JSON only — no images or binary.** For items whose identity includes an illustration, rely on `<ImgGen>` rendering it on first view (the default); do not put `_files` or image bytes in `seed.json`.
+- **JSON only — no images or binary.** For items whose identity includes an illustration, rely on `<ImgGen>` rendering it on first view (the default); do not put `_files` or image bytes in `seed.json` — put binaries in the Files tab instead.
 - **Platform-originated types can't be seeded.** Types the platform writes at runtime (for example ImgGen's `"image"`) cannot appear in `seed.json`; give those their own `access.js` branch instead.
 - **If the app has an `access.js`, every `type` you emit here must have a branch in it** — but don't add an access function _just_ to satisfy this: an app with no per-document rules keeps the default open data model and seeds fine without one. When there **is** an `access.js`, seed docs are written through it as the **owner** when the owner explicitly applies the seed-data import, so a `type` it doesn't return a **readable descriptor** for (a non-empty `channels`, or an `audience`) is denied (`unknown document type`) — the doc never seeds, and the same gap later surfaces as a hard error the moment the running app writes that type. Before finishing, if you emitted an `access.js`, confirm it returns a readable descriptor for every distinct `type` present in `seed.json`. (Deletes go through the same gate: a `db.del` writes a tombstone `{ _id, _deleted: true }` that carries **no** `type`, channel, or author — so branch on `doc._deleted`, then authorize and route it off **`oldDoc`** (the persisted document is the only trustworthy record of the doc's type and owner), returning the same descriptor the live doc got. A bare `_deleted` branch that ignores `oldDoc` either fails the app's own deletes or over-broadens them.)
 
@@ -748,6 +748,10 @@ What you can see is the app's code, its files, and this conversation. The page a
 
 When someone reports that their app won't open ("App not available", a blank screen, a dead end), describe the observable fact: the app didn't resolve on that visit. Offer a reload as the first thing to try, and say plainly that you don't know the cause when you don't — the platform reports the reason, and guessing one sends the person to fix something that was never wrong.
 
+### Static assets — reference bundle files by path
+
+Static assets. Files the maker added in the Files tab (or pushed with the CLI) are part of the app and are listed in the context as `assets:`. Reference them by absolute path from the app root — `<img src="/logo.png" alt="…">`, `<audio src="/intro.mp3">`, `fetch("/data.csv")` — never by an external URL and never by inlining bytes. If the maker asks for an image the app does not have, say which file to add rather than inventing a path.
+
 ## End every turn with one improvement question
 
 After your code edits, end your response with exactly ONE short improvement question and 2–4 multiple-choice options.