@vibes.diy/prompts 10.7.4 → 10.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "10.7.4",
+  "version": "10.8.0",
   "type": "module",
   "main": "./index.js",
   "description": "",
@@ -24,9 +24,9 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/call-ai-v2": "^10.7.4",
-    "@vibes.diy/identity": "^10.7.4",
-    "@vibes.diy/use-vibes-types": "^10.7.4",
+    "@vibes.diy/call-ai-v2": "^10.8.0",
+    "@vibes.diy/identity": "^10.8.0",
+    "@vibes.diy/use-vibes-types": "^10.8.0",
     "arktype": "~2.2.3",
     "json-schema-faker": "~0.6.2"
   },

package/system-prompt-initial-oneshot.md

@@ -152,6 +152,28 @@ A second visitor should arrive at a party, not a parking lot: within five second
 
 **Restraint — alive never means obnoxious.** No confetti on load; no popups nagging people to share. One or two well-placed delightful touches beat a wall of noise.
 
+### Put deep links and one-time params in the hash, then consume them
+
+Shareable state — an invite code, a referral, a selected day, a preselected item — belongs in the URL **fragment**, not the query: `https://vibes.diy/vibe/alice/picker#friend=bob` (no trailing slash before the `#`). The fragment never reaches the server, so every visitor still gets the fast cached page; a query param makes every share link a slow full render.
+
+Read the fragment with `URLSearchParams`, and **also listen for `hashchange`** — the platform mirrors the address bar's fragment into the app a beat after the first render, so a read at mount alone can come up empty. When a param is a **one-time action** (invite, referral, token), consume it and then clear it with `history.replaceState`; the platform mirrors your cleaned URL into the real address bar, so the link the visitor copies no longer replays the action.
+
+```jsx
+useEffect(() => {
+  const apply = () => {
+    const friend = new URLSearchParams(location.hash.slice(1)).get("friend");
+    if (!friend) return;
+    addFriend(friend);
+    history.replaceState(null, "", location.pathname + location.search); // consumed — scrub it
+  };
+  apply();
+  window.addEventListener("hashchange", apply);
+  return () => window.removeEventListener("hashchange", apply);
+}, []);
+```
+
+Build the share link the same way — `` `${location.origin}${location.pathname}#friend=${me}` `` — and never write a one-time param into the query.
+
 ## 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

@@ -154,6 +154,28 @@ A second visitor should arrive at a party, not a parking lot: within five second
 
 **Restraint — alive never means obnoxious.** No confetti on load; no popups nagging people to share. One or two well-placed delightful touches beat a wall of noise.
 
+### Put deep links and one-time params in the hash, then consume them
+
+Shareable state — an invite code, a referral, a selected day, a preselected item — belongs in the URL **fragment**, not the query: `https://vibes.diy/vibe/alice/picker#friend=bob` (no trailing slash before the `#`). The fragment never reaches the server, so every visitor still gets the fast cached page; a query param makes every share link a slow full render.
+
+Read the fragment with `URLSearchParams`, and **also listen for `hashchange`** — the platform mirrors the address bar's fragment into the app a beat after the first render, so a read at mount alone can come up empty. When a param is a **one-time action** (invite, referral, token), consume it and then clear it with `history.replaceState`; the platform mirrors your cleaned URL into the real address bar, so the link the visitor copies no longer replays the action.
+
+```jsx
+useEffect(() => {
+  const apply = () => {
+    const friend = new URLSearchParams(location.hash.slice(1)).get("friend");
+    if (!friend) return;
+    addFriend(friend);
+    history.replaceState(null, "", location.pathname + location.search); // consumed — scrub it
+  };
+  apply();
+  window.addEventListener("hashchange", apply);
+  return () => window.removeEventListener("hashchange", apply);
+}, []);
+```
+
+Build the share link the same way — `` `${location.origin}${location.pathname}#friend=${me}` `` — and never write a one-time param into the query.
+
 ## 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

@@ -665,6 +665,28 @@ A second visitor should arrive at a party, not a parking lot: within five second
 
 **Restraint — alive never means obnoxious.** No confetti on load; no popups nagging people to share. One or two well-placed delightful touches beat a wall of noise.
 
+### Put deep links and one-time params in the hash, then consume them
+
+Shareable state — an invite code, a referral, a selected day, a preselected item — belongs in the URL **fragment**, not the query: `https://vibes.diy/vibe/alice/picker#friend=bob` (no trailing slash before the `#`). The fragment never reaches the server, so every visitor still gets the fast cached page; a query param makes every share link a slow full render.
+
+Read the fragment with `URLSearchParams`, and **also listen for `hashchange`** — the platform mirrors the address bar's fragment into the app a beat after the first render, so a read at mount alone can come up empty. When a param is a **one-time action** (invite, referral, token), consume it and then clear it with `history.replaceState`; the platform mirrors your cleaned URL into the real address bar, so the link the visitor copies no longer replays the action.
+
+```jsx
+useEffect(() => {
+  const apply = () => {
+    const friend = new URLSearchParams(location.hash.slice(1)).get("friend");
+    if (!friend) return;
+    addFriend(friend);
+    history.replaceState(null, "", location.pathname + location.search); // consumed — scrub it
+  };
+  apply();
+  window.addEventListener("hashchange", apply);
+  return () => window.removeEventListener("hashchange", apply);
+}, []);
+```
+
+Build the share link the same way — `` `${location.origin}${location.pathname}#friend=${me}` `` — and never write a one-time param into the query.
+
 ## 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.