@vibes.diy/prompts 14.1.6 → 14.1.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "14.1.6",
+  "version": "14.1.8",
   "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.6",
-    "@vibes.diy/identity": "14.1.6",
-    "@vibes.diy/use-vibes-types": "14.1.6",
+    "@vibes.diy/call-ai-v2": "14.1.8",
+    "@vibes.diy/identity": "14.1.8",
+    "@vibes.diy/use-vibes-types": "14.1.8",
     "arktype": "~2.2.3",
     "json-schema-faker": "~0.6.3"
   },

package/system-prompt-initial-oneshot.md

@@ -84,6 +84,7 @@ Every feature you described above should work when this one block lands. Don't l
   <div ref={chatRef} className="max-h-64 overflow-y-auto">{messages}</div>
   ```
 - **Load Google Fonts with `&display=swap` (or `&display=optional`), never `&display=block`.** Append it to the Fonts URL so text paints immediately in a fallback instead of staying invisible for seconds on slow connections (flash of invisible text) — e.g. `https://fonts.googleapis.com/css2?family=Inter:wght@400;700&display=swap`.
+- **The bottom-right corner belongs to the platform — never pin your own control there.** The Vibes Switch (the logo) floats over every app in that corner, so a `fixed` element anchored to both `bottom` and `right` lands underneath it: no floating add/compose button, no chat bubble, no scroll-to-top disc in that spot. Anchor a floating action bottom-left or bottom-center instead, or fold it into the layout — a header button, or a full-width sticky bar (the platform already reserves scroll clearance below your app for one).
 **All app data is shared and world-readable by default** — the runtime decides access, not your code. Don't write UI copy that promises privacy ("only you can see this", "private") unless the app was actually asked to be private; per-document write rules and channel-based read isolation are **designed later, at publish**. Still gate every write surface on `useVibe(dbName).can` — that liveness gate is universal (everyone is allowed until rules exist).
 
 After your last code block, add a short 1-2 sentence message describing the core workflow the app supports.

package/system-prompt-initial.md

@@ -80,6 +80,7 @@ The sandbox serves raw ES modules, so `App.jsx` can import local `.js`/`.jsx` fi
   <div ref={chatRef} className="max-h-64 overflow-y-auto">{messages}</div>
   ```
 - **Load Google Fonts with `&display=swap` (or `&display=optional`), never `&display=block`.** Append it to the Fonts URL so text paints immediately in a fallback instead of staying invisible for seconds on slow connections (flash of invisible text) — e.g. `https://fonts.googleapis.com/css2?family=Inter:wght@400;700&display=swap`.
+- **The bottom-right corner belongs to the platform — never pin your own control there.** The Vibes Switch (the logo) floats over every app in that corner, so a `fixed` element anchored to both `bottom` and `right` lands underneath it: no floating add/compose button, no chat bubble, no scroll-to-top disc in that spot. Anchor a floating action bottom-left or bottom-center instead, or fold it into the layout — a header button, or a full-width sticky bar (the platform already reserves scroll clearance below your app for one).
 - NO hooks beyond `useVibe`/`useViewer`, NO data wiring — those land in the feature edits.
 
 Target ~40–60 lines. The shell should look like a real app with empty sections, not a blank page.

package/system-prompt.md

@@ -89,6 +89,7 @@ The sandbox serves raw ES modules, so `App.jsx` can import local `.js`/`.jsx` fi
   <div ref={chatRef} className="max-h-64 overflow-y-auto">{messages}</div>
   ```
 - **Load Google Fonts with `&display=swap` (or `&display=optional`), never `&display=block`.** Append it to the Fonts URL so text paints immediately in a fallback instead of staying invisible for seconds on slow connections (flash of invisible text) — e.g. `https://fonts.googleapis.com/css2?family=Inter:wght@400;700&display=swap`.
+- **The bottom-right corner belongs to the platform — never pin your own control there.** The Vibes Switch (the logo) floats over every app in that corner, so a `fixed` element anchored to both `bottom` and `right` lands underneath it: no floating add/compose button, no chat bubble, no scroll-to-top disc in that spot. Anchor a floating action bottom-left or bottom-center instead, or fold it into the layout — a header button, or a full-width sticky bar (the platform already reserves scroll clearance below your app for one).
 
 **If the app needs an `access.js`** — privacy, sharing, teams, roles, or approval — the access skill doc (included on permission-shaped turns) carries the emit format, placement, and worked examples; emit `access.js` before any `App.jsx` edit that writes a doc type it gates. Gate every write surface on `useVibe(dbName).can` regardless of whether the app has an `access.js`.