@vibes.diy/prompts 14.3.293 → 14.3.295
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/llms/backend.md +10 -3
- package/llms/use-viewer.md +12 -0
- package/package.json +5 -5
- package/system-prompt-initial-oneshot.md +1 -1
- package/system-prompt-initial.md +1 -1
- package/system-prompt.md +1 -1
package/llms/backend.md
CHANGED
|
@@ -650,14 +650,21 @@ const budget = await ctx.youtube.status(); // { available, unitsLeftToday, daily
|
|
|
650
650
|
```
|
|
651
651
|
|
|
652
652
|
For the button, an `sms:` link opens Messages with the ask written out.
|
|
653
|
-
|
|
653
|
+
Vibes answers texts over iMessage, so on an iPhone, iPad or Mac the button
|
|
654
|
+
texts; anywhere else (Android, Windows) the same ask opens Vibes in the
|
|
655
|
+
browser with the words waiting in the box (`https://vibes.diy/agent?text=`),
|
|
656
|
+
and the reminders arrive as Vibes notifications. iPadOS reports itself as a
|
|
657
|
+
Mac. `target="_blank"` is what lets the tap leave the app's frame:
|
|
654
658
|
|
|
655
659
|
```jsx
|
|
656
660
|
const ask = `Please notify me about changes to the schedule on ${appUrl}`;
|
|
657
|
-
|
|
661
|
+
const imessage = /iPhone|iPad|iPod|Macintosh/.test(navigator.userAgent);
|
|
662
|
+
const href = imessage
|
|
663
|
+
? `sms:vibes@vibes.diy&body=${encodeURIComponent(ask)}`
|
|
664
|
+
: `https://vibes.diy/agent?text=${encodeURIComponent(ask)}`;
|
|
665
|
+
<a href={href} target="_blank" rel="noopener">{imessage ? "Text me reminders" : "Get reminders"}</a>
|
|
658
666
|
```
|
|
659
667
|
|
|
660
|
-
It works where iMessage does (iPhone, iPad, Mac), so label it for that.
|
|
661
668
|
A follower ends it by replying "stop", and their follow lapses on its own
|
|
662
669
|
after the days Vibes set for it.
|
|
663
670
|
- **`ctx.log(level?, ...args)` is the handler's diagnostic lane.** It is the
|
package/llms/use-viewer.md
CHANGED
|
@@ -282,6 +282,18 @@ Copy that works, and copy that doesn't:
|
|
|
282
282
|
|
|
283
283
|
And never disable the app's real controls on `!viewer`. If favoriting works signed out, keep it working signed out — the access function refuses the *cloud* write on its own, calmly, while the local write still succeeds. Turning a working app into a signup wall is worse than never asking at all.
|
|
284
284
|
|
|
285
|
+
When the access rules keep a one-press action to members — Vote beside each poll option, RSVP on each event, Like on each post — that same button is the ask for a settled signed-out visitor, in the same spot and named for the action:
|
|
286
|
+
|
|
287
|
+
```jsx
|
|
288
|
+
{settledSignedOut ? (
|
|
289
|
+
<Button type="button" onClick={requestLogin}>Sign in to vote</Button>
|
|
290
|
+
) : (
|
|
291
|
+
<Button type="button" disabled={poll.closed} onClick={() => castVote(option)}>Vote</Button>
|
|
292
|
+
)}
|
|
293
|
+
```
|
|
294
|
+
|
|
295
|
+
Every row keeps a press that goes somewhere, and once they are back the row shows Vote. `disabled` stays for facts about the record, like a closed poll.
|
|
296
|
+
|
|
285
297
|
Keep the guest's composed text across sign-in. Draft input lives in component state (or a local draft the app already saves) — and signing in never clears it. The new identity arrives on its own through `viewer`; the words they typed stay where they left them, and they continue from there. A form that resets on identity change makes the guest write everything twice.
|
|
286
298
|
|
|
287
299
|
## Notes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vibes.diy/prompts",
|
|
3
|
-
"version": "14.3.
|
|
3
|
+
"version": "14.3.295",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"main": "./index.js",
|
|
6
6
|
"exports": {
|
|
@@ -39,10 +39,10 @@
|
|
|
39
39
|
"license": "Apache-2.0",
|
|
40
40
|
"dependencies": {
|
|
41
41
|
"@adviser/cement": "~0.5.34",
|
|
42
|
-
"@vibes.diy/api-types": "14.3.
|
|
43
|
-
"@vibes.diy/call-ai-v2": "14.3.
|
|
44
|
-
"@vibes.diy/identity": "14.3.
|
|
45
|
-
"@vibes.diy/use-vibes-types": "14.3.
|
|
42
|
+
"@vibes.diy/api-types": "14.3.295",
|
|
43
|
+
"@vibes.diy/call-ai-v2": "14.3.295",
|
|
44
|
+
"@vibes.diy/identity": "14.3.295",
|
|
45
|
+
"@vibes.diy/use-vibes-types": "14.3.295",
|
|
46
46
|
"arktype": "~2.2.9",
|
|
47
47
|
"json-schema-faker": "~0.6.3"
|
|
48
48
|
},
|
|
@@ -104,7 +104,7 @@ Every feature you described above should work when this one block lands. Don't l
|
|
|
104
104
|
Three things happen in this order on every screen, and the first two happen for a visitor who has not signed in:
|
|
105
105
|
|
|
106
106
|
1. **Reading comes first.** Whatever the rules and the app's sharing setting let a signed-out visitor read renders at once: the board of what is on this week, the finished pieces in a gallery, the menu a shop posts. The write surface is what the rules gate, so a visitor reads those records with the Add control waiting beneath them, and the records keep their place on the screen. What the rules keep to members — a guest list, the names on a chore chart — stays with the members, and a visitor meets the ask to join in its place. An app a person keeps for themselves — a tracker, a log, a list just for them — opens on its own screen for a signed-out visitor too: the habits or entries view, its controls in their `can` state and its inviting empty state, with the sign-in ask beside the control that would save. Its first screen is the app itself, with the ask beside it.
|
|
107
|
-
2. **The write surface is gated on `can`.** `useVibe(dbName).can` decides whether the Add, Edit or Delete control shows and in what state (`pending` holds it quietly; a resolved denial gets one sentence in the app's own words). Nothing else on the screen waits on it. A form that opens from a button — a Dialog or Sheet `trigger`, a Claim or Add that reveals fields — is gated at its Save: the opening button stays pressable, the form opens with its fields, and Save asks `can.create(draft)` with the draft built from what the person typed (an Edit form's Save asks `can.edit(doc)` of the record it changes). When the app's own access rules ask a writer to sign in, a settled signed-out visitor
|
|
107
|
+
2. **The write surface is gated on `can`.** `useVibe(dbName).can` decides whether the Add, Edit or Delete control shows and in what state (`pending` holds it quietly; a resolved denial gets one sentence in the app's own words). Nothing else on the screen waits on it. A form that opens from a button — a Dialog or Sheet `trigger`, a Claim or Add that reveals fields — is gated at its Save: the opening button stays pressable, the form opens with its fields, and Save asks `can.create(draft)` with the draft built from what the person typed (an Edit form's Save asks `can.edit(doc)` of the record it changes). When the app's own access rules ask a writer to sign in, the button a settled signed-out visitor would press is the sign-in ask itself, named for the action and in the same spot: a form's opening button reads "Sign in to claim a slot", and a one-press action on each row — Vote, RSVP, Like — reads "Sign in to vote", so their first press goes somewhere and once they are back the row shows Vote.
|
|
108
108
|
3. **The ask is a button, at the moment of value.** The sign-in ask is one `Button` wired to `useViewer().requestLogin()`, shown once identity has settled (`!isViewerPending && !viewer`), worded for what the person gets ("Keep these on all your devices", "Sign in to add your dish"), and placed where they feel the pull: beside the control that would save, or right after they made something worth keeping. Every sentence the app renders that mentions signing in has that button beside it, so the reader acts where they read. The use-viewer skill's _Asking a visitor to sign in_ has the worked example.
|
|
109
109
|
- **Commit to one layout stance, built for a thumb.** Pick the stance the app's job calls for and hold it on every view — a board of cards, a feed under a hero, a dashboard of stats, a split header and list, a tabbed switcher, a sticky bottom action bar — so the first screen says what kind of app this is before a word is read. The bold stance is the default: a scoreboard is a wall of big numbers, a cast is a grid of faces, a planner is a week you can see at once; a quiet single column is the stance for a reading app and nothing else. Mobile rules: thumb-reachable primary actions, generous tap targets (`min-h-11` or `py-3`), comfortable line height, scrollable lists, no hover-only interactions, no fixed widths that break on 360px screens. Mobile-first, then `md:` / `lg:` for larger viewports.
|
|
110
110
|
- **Touch controls belong to the finger on a phone.** A 3D or canvas scene, a joystick or D-pad, a drag surface, or any button someone presses and holds carries `select-none touch-none` on the control area **and** its container (the HUD and labels around it too), so a press or drag steers the app while nearby text stays put — no selection highlight, no copy callout, no page scroll or zoom. Drive holds with `onPointerDown` / `onPointerUp` / `onPointerCancel` (mouse and touch in one path), and give a hold button `onContextMenu={(e) => e.preventDefault()}` so a long press keeps holding. Every hint names what a thumb does — swipe, tap, hold — never a key or a mouse.
|
package/system-prompt-initial.md
CHANGED
|
@@ -98,7 +98,7 @@ The sandbox serves raw ES modules, so `App.jsx` can import local `.js`/`.jsx` fi
|
|
|
98
98
|
Three things happen in this order on every screen, and the first two happen for a visitor who has not signed in:
|
|
99
99
|
|
|
100
100
|
1. **Reading comes first.** Whatever the rules and the app's sharing setting let a signed-out visitor read renders at once: the board of what is on this week, the finished pieces in a gallery, the menu a shop posts. The write surface is what the rules gate, so a visitor reads those records with the Add control waiting beneath them, and the records keep their place on the screen. What the rules keep to members — a guest list, the names on a chore chart — stays with the members, and a visitor meets the ask to join in its place. An app a person keeps for themselves — a tracker, a log, a list just for them — opens on its own screen for a signed-out visitor too: the habits or entries view, its controls in their `can` state and its inviting empty state, with the sign-in ask beside the control that would save. Its first screen is the app itself, with the ask beside it.
|
|
101
|
-
2. **The write surface is gated on `can`.** `useVibe(dbName).can` decides whether the Add, Edit or Delete control shows and in what state (`pending` holds it quietly; a resolved denial gets one sentence in the app's own words). Nothing else on the screen waits on it. A form that opens from a button — a Dialog or Sheet `trigger`, a Claim or Add that reveals fields — is gated at its Save: the opening button stays pressable, the form opens with its fields, and Save asks `can.create(draft)` with the draft built from what the person typed (an Edit form's Save asks `can.edit(doc)` of the record it changes). When the app's own access rules ask a writer to sign in, a settled signed-out visitor
|
|
101
|
+
2. **The write surface is gated on `can`.** `useVibe(dbName).can` decides whether the Add, Edit or Delete control shows and in what state (`pending` holds it quietly; a resolved denial gets one sentence in the app's own words). Nothing else on the screen waits on it. A form that opens from a button — a Dialog or Sheet `trigger`, a Claim or Add that reveals fields — is gated at its Save: the opening button stays pressable, the form opens with its fields, and Save asks `can.create(draft)` with the draft built from what the person typed (an Edit form's Save asks `can.edit(doc)` of the record it changes). When the app's own access rules ask a writer to sign in, the button a settled signed-out visitor would press is the sign-in ask itself, named for the action and in the same spot: a form's opening button reads "Sign in to claim a slot", and a one-press action on each row — Vote, RSVP, Like — reads "Sign in to vote", so their first press goes somewhere and once they are back the row shows Vote.
|
|
102
102
|
3. **The ask is a button, at the moment of value.** The sign-in ask is one `Button` wired to `useViewer().requestLogin()`, shown once identity has settled (`!isViewerPending && !viewer`), worded for what the person gets ("Keep these on all your devices", "Sign in to add your dish"), and placed where they feel the pull: beside the control that would save, or right after they made something worth keeping. Every sentence the app renders that mentions signing in has that button beside it, so the reader acts where they read. The use-viewer skill's _Asking a visitor to sign in_ has the worked example.
|
|
103
103
|
- **Commit to one layout stance, built for a thumb.** Pick the stance the app's job calls for and hold it on every view — a board of cards, a feed under a hero, a dashboard of stats, a split header and list, a tabbed switcher, a sticky bottom action bar — so the first screen says what kind of app this is before a word is read. The bold stance is the default: a scoreboard is a wall of big numbers, a cast is a grid of faces, a planner is a week you can see at once; a quiet single column is the stance for a reading app and nothing else. Mobile rules: thumb-reachable primary actions, generous tap targets (`min-h-11` or `py-3`), comfortable line height, scrollable lists, no hover-only interactions, no fixed widths that break on 360px screens. Mobile-first, then `md:` / `lg:` for larger viewports.
|
|
104
104
|
- **Touch controls belong to the finger on a phone.** A 3D or canvas scene, a joystick or D-pad, a drag surface, or any button someone presses and holds carries `select-none touch-none` on the control area **and** its container (the HUD and labels around it too), so a press or drag steers the app while nearby text stays put — no selection highlight, no copy callout, no page scroll or zoom. Drive holds with `onPointerDown` / `onPointerUp` / `onPointerCancel` (mouse and touch in one path), and give a hold button `onContextMenu={(e) => e.preventDefault()}` so a long press keeps holding. Every hint names what a thumb does — swipe, tap, hold — never a key or a mouse.
|
package/system-prompt.md
CHANGED
|
@@ -98,7 +98,7 @@ The sandbox serves raw ES modules, so `App.jsx` can import local `.js`/`.jsx` fi
|
|
|
98
98
|
Three things happen in this order on every screen, and the first two happen for a visitor who has not signed in:
|
|
99
99
|
|
|
100
100
|
1. **Reading comes first.** Whatever the rules and the app's sharing setting let a signed-out visitor read renders at once: the board of what is on this week, the finished pieces in a gallery, the menu a shop posts. The write surface is what the rules gate, so a visitor reads those records with the Add control waiting beneath them, and the records keep their place on the screen. What the rules keep to members — a guest list, the names on a chore chart — stays with the members, and a visitor meets the ask to join in its place. An app a person keeps for themselves — a tracker, a log, a list just for them — opens on its own screen for a signed-out visitor too: the habits or entries view, its controls in their `can` state and its inviting empty state, with the sign-in ask beside the control that would save. Its first screen is the app itself, with the ask beside it.
|
|
101
|
-
2. **The write surface is gated on `can`.** `useVibe(dbName).can` decides whether the Add, Edit or Delete control shows and in what state (`pending` holds it quietly; a resolved denial gets one sentence in the app's own words). Nothing else on the screen waits on it. A form that opens from a button — a Dialog or Sheet `trigger`, a Claim or Add that reveals fields — is gated at its Save: the opening button stays pressable, the form opens with its fields, and Save asks `can.create(draft)` with the draft built from what the person typed (an Edit form's Save asks `can.edit(doc)` of the record it changes). When the app's own access rules ask a writer to sign in, a settled signed-out visitor
|
|
101
|
+
2. **The write surface is gated on `can`.** `useVibe(dbName).can` decides whether the Add, Edit or Delete control shows and in what state (`pending` holds it quietly; a resolved denial gets one sentence in the app's own words). Nothing else on the screen waits on it. A form that opens from a button — a Dialog or Sheet `trigger`, a Claim or Add that reveals fields — is gated at its Save: the opening button stays pressable, the form opens with its fields, and Save asks `can.create(draft)` with the draft built from what the person typed (an Edit form's Save asks `can.edit(doc)` of the record it changes). When the app's own access rules ask a writer to sign in, the button a settled signed-out visitor would press is the sign-in ask itself, named for the action and in the same spot: a form's opening button reads "Sign in to claim a slot", and a one-press action on each row — Vote, RSVP, Like — reads "Sign in to vote", so their first press goes somewhere and once they are back the row shows Vote.
|
|
102
102
|
3. **The ask is a button, at the moment of value.** The sign-in ask is one `Button` wired to `useViewer().requestLogin()`, shown once identity has settled (`!isViewerPending && !viewer`), worded for what the person gets ("Keep these on all your devices", "Sign in to add your dish"), and placed where they feel the pull: beside the control that would save, or right after they made something worth keeping. Every sentence the app renders that mentions signing in has that button beside it, so the reader acts where they read. The use-viewer skill's _Asking a visitor to sign in_ has the worked example.
|
|
103
103
|
- **Commit to one layout stance, built for a thumb.** Pick the stance the app's job calls for and hold it on every view — a board of cards, a feed under a hero, a dashboard of stats, a split header and list, a tabbed switcher, a sticky bottom action bar — so the first screen says what kind of app this is before a word is read. The bold stance is the default: a scoreboard is a wall of big numbers, a cast is a grid of faces, a planner is a week you can see at once; a quiet single column is the stance for a reading app and nothing else. Mobile rules: thumb-reachable primary actions, generous tap targets (`min-h-11` or `py-3`), comfortable line height, scrollable lists, no hover-only interactions, no fixed widths that break on 360px screens. Mobile-first, then `md:` / `lg:` for larger viewports.
|
|
104
104
|
- **Touch controls belong to the finger on a phone.** A 3D or canvas scene, a joystick or D-pad, a drag surface, or any button someone presses and holds carries `select-none touch-none` on the control area **and** its container (the HUD and labels around it too), so a press or drag steers the app while nearby text stays put — no selection highlight, no copy callout, no page scroll or zoom. Drive holds with `onPointerDown` / `onPointerUp` / `onPointerCancel` (mouse and touch in one path), and give a hold button `onContextMenu={(e) => e.preventDefault()}` so a long press keeps holding. Every hint names what a thumb does — swipe, tap, hold — never a key or a mouse.
|