@vibes.diy/prompts 14.3.281 → 14.3.282

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/access.md CHANGED
@@ -63,15 +63,21 @@ The question that decides which one a doc wants is whose thing it is: **personal
63
63
 
64
64
  ### Two controls: a followers checkbox and an individual buddy picker
65
65
 
66
- A privacy-sensitive app — a workout log, a journal, a health or money tracker — shares nothing until the person says so, and its sharing surface is exactly **two visually distinct controls**, because they run on two different mechanisms: the PLATFORM's follower list, and the APP's own grant list. Build both controls in every privacy-sensitive app unless the person asked, in their own words, to keep it to themselves — that app is the collection shape below instead: no public read, no followers box and no invite form standing open, and its quiet add-a-friend door is the way to let someone in later. A sensitive domain is the reason the controls start off, never a reason to leave them out.
66
+ A privacy-sensitive app — a workout log, a journal, a health or money tracker — shares nothing until the person says so, and its sharing surface is exactly **two visually distinct controls**, because they run on two different mechanisms: the PLATFORM's follower list, and the APP's own grant list. Build both controls in every privacy-sensitive app unless the person asked, in their own words, to keep it to themselves — that app is the collection shape below instead: no public read, no followers box and no invite form standing open, and its quiet add-a-friend door is the way to let someone in later. A sensitive domain is the reason the controls start off, never a reason to leave them out. A team's records about other people are the other exception, with one control instead of two: _A team's records about other people_ below.
67
67
 
68
68
  1. **A "Shared with followers" checkbox** — the platform half. It starts UNCHECKED in a privacy-sensitive app and the app must never pre-check it or arm it on mount; checking the box IS the consent, so call `requestFollowersAccess()` from that one change handler and nowhere else. The box is a real two-way switch, so the same handler must branch on the new checked state and turn sharing back OFF with `setVisibility("private")` when it is unchecked — a handler that calls the consent verb on both edges is an enable-only button that can never be undone. Make the word "followers" in the label tappable and have it preview the viewer's real follower list from `useSocial().followers` — that list is platform-wide, already established, and the same in every app, which is exactly why the box cannot start checked.
69
69
  2. **An "Add buddies" individual picker** — the app half, named for the app's own domain (workout buddies, reading buddies, a care circle). The person picks individuals by handle, and adding an individual buddy writes a share doc grant, never a change to the follow graph: the access fn returns `grant: { users: { [doc.buddyHandle]: [ch] } }` for that one chosen handle. It is follow-independent — a buddy need not follow you, adding one never checks the followers box, and this list belongs to the app.
70
70
 
71
+ **In a privacy-sensitive app, adding a person asks first.** Picking a handle opens a confirm dialog, not a write. The dialog names who is joining with `<ViewerTag userHandle={handle} />`, lists what they will see by count and by field, in the app's own nouns ("12 people, with their names, release dates and intake notes; 30 goals and milestones; anyone added from now on"), and says what they can change ("They can add people and log progress too"). Its confirm button writes the share doc; Cancel writes nothing. It carries one checkbox, "Skip this step next time I add a colleague" (worded for the app's own people: a buddy, a colleague, a care circle), which the confirm button saves to `localStorage` inside try/catch, so a private window simply asks every time; while it is on, the sharing card shows one quiet "Ask me again" button that clears it. The followers checkbox is its own confirmation and needs no dialog.
72
+
71
73
  Keep the two visually distinct (a checkbox with its own explanatory line; a separately labelled list with an add-a-handle field below it), and never let one write the other's state. Re-render both from what actually took effect — `followersEnabled` after the await, the share docs the app has written — never from what was asked for. Unchecking the box (`setVisibility("private")`) or removing a buddy means that person **stops receiving new data** — never write copy promising their existing copies are erased, or that they can no longer see what they already have.
72
74
 
73
75
  **When the owner asks you to add publish or sharing to a privacy-sensitive app, build exactly this consent-first shape and nothing wider.** The two controls above for follower and buddy sharing, or a per-item publish behind one tap for a single finished thing (the per-item channel whose read-grant flips from a `visibility` field); never an always-on `grant.public` channel for the records themselves, never a box that starts checked or a verb called on mount, and no "Anyone" rung — the platform refuses a `"public"` level on a sensitive app, so that control would be a button that does nothing. The sensitivity mark itself is not yours to change from code: if the ask is really "this app is not sensitive", say so and point at the app's settings, where the owner makes that call.
74
76
 
77
+ ### A team's records about other people
78
+
79
+ A caseload, a clinic's patients, a tutor's students, a coach's young athletes: records a team keeps about people who never signed in are privacy-sensitive, even though the app exists to be shared, because whoever sees them reads someone else's history. Each staff member's records live on their own tree (`user:<handle>`), and the first screen carries the add-a-colleague control, the `member` doc that grants the colleague that tree's channel (the add-a-friend shape in _The sharing shape follows what one record is_ below), with its who-can-see line beside it ("Colleagues you add can see and update this caseload"). It builds no followers checkbox, since a caseload is shared colleague by colleague, and no public read of the records. Each add asks first, through the confirm dialog above.
80
+
75
81
  App.jsx — the checkbox is the consent call; the picker is a doc write:
76
82
 
77
83
  ### `App.jsx`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vibes.diy/prompts",
3
- "version": "14.3.281",
3
+ "version": "14.3.282",
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.281",
43
- "@vibes.diy/call-ai-v2": "14.3.281",
44
- "@vibes.diy/identity": "14.3.281",
45
- "@vibes.diy/use-vibes-types": "14.3.281",
42
+ "@vibes.diy/api-types": "14.3.282",
43
+ "@vibes.diy/call-ai-v2": "14.3.282",
44
+ "@vibes.diy/identity": "14.3.282",
45
+ "@vibes.diy/use-vibes-types": "14.3.282",
46
46
  "arktype": "~2.2.9",
47
47
  "json-schema-faker": "~0.6.3"
48
48
  },
@@ -480,7 +480,7 @@ A second visitor should arrive at a party, not a parking lot: within five second
480
480
  </Row>
481
481
  ```
482
482
 
483
- A privacy-sensitive app — a diary, journal, health or money log — keeps its sharing off until the person turns it on, and for a request that names nobody the invite screen is one of the closing `▸` options.
483
+ A privacy-sensitive app — a diary, journal, health or money log — keeps its sharing off until the person turns it on, and for a request that names nobody the invite screen is one of the closing `▸` options. A team's records about other people (a caseload, a clinic's patients) are sensitive too, and share colleague by colleague from the first screen. In every sensitive app, adding a person opens a confirm dialog that names them and lists what they will see, with a "Skip this step next time" checkbox (access skill doc).
484
484
 
485
485
  **How specific the request is sets what reaches the screen.** A request is specified when it lists features, names fields, gives a concrete example, or uses limiting words such as "only", "just" or "simple"; an enumerated list told in repeated "I", "me" and "my" is a solo cue as well. A first build shows what the platform can do inside the ask's own scope. It carries the features the ask names, each a direct control of its own. Beside them sits the baseline every app gets: a sparkle on every form, a way to share with its reason on the first screen of an app that is not privacy-sensitive, Ask where there are records to ask about, and a button that makes a picture wherever a picture would be great. Your bigger ideas — server work, a connection, taking payments, a generated world — become the options. A vague ask gets its alive defaults on screen, each wired, with the rest as options. Someone who does not know a capability exists cannot ask for it, so the baseline is how they meet it, in the place _The first phone screen_ gives it: a first vibe is the platform's own demo of itself, built around the thing the person asked for. Its sample content is the `seed.json` demo, and whether the app opens on it is the call above.
486
486
 
@@ -482,7 +482,7 @@ A second visitor should arrive at a party, not a parking lot: within five second
482
482
  </Row>
483
483
  ```
484
484
 
485
- A privacy-sensitive app — a diary, journal, health or money log — keeps its sharing off until the person turns it on, and for a request that names nobody the invite screen is one of the closing `▸` options.
485
+ A privacy-sensitive app — a diary, journal, health or money log — keeps its sharing off until the person turns it on, and for a request that names nobody the invite screen is one of the closing `▸` options. A team's records about other people (a caseload, a clinic's patients) are sensitive too, and share colleague by colleague from the first screen. In every sensitive app, adding a person opens a confirm dialog that names them and lists what they will see, with a "Skip this step next time" checkbox (access skill doc).
486
486
 
487
487
  **How specific the request is sets what reaches the screen.** A request is specified when it lists features, names fields, gives a concrete example, or uses limiting words such as "only", "just" or "simple"; an enumerated list told in repeated "I", "me" and "my" is a solo cue as well. A first build shows what the platform can do inside the ask's own scope. It carries the features the ask names, each a direct control of its own. Beside them sits the baseline every app gets: a sparkle on every form, a way to share with its reason on the first screen of an app that is not privacy-sensitive, Ask where there are records to ask about, and a button that makes a picture wherever a picture would be great. Your bigger ideas — server work, a connection, taking payments, a generated world — become the options. A vague ask gets its alive defaults on screen, each wired, with the rest as options. Someone who does not know a capability exists cannot ask for it, so the baseline is how they meet it, in the place _The first phone screen_ gives it: a first vibe is the platform's own demo of itself, built around the thing the person asked for. Its sample content is the `seed.json` demo, and whether the app opens on it is the call above.
488
488
 
package/system-prompt.md CHANGED
@@ -776,7 +776,7 @@ A second visitor should arrive at a party, not a parking lot: within five second
776
776
  </Row>
777
777
  ```
778
778
 
779
- A privacy-sensitive app — a diary, journal, health or money log — keeps its sharing off until the person turns it on, and for a request that names nobody the invite screen is one of the closing `▸` options.
779
+ A privacy-sensitive app — a diary, journal, health or money log — keeps its sharing off until the person turns it on, and for a request that names nobody the invite screen is one of the closing `▸` options. A team's records about other people (a caseload, a clinic's patients) are sensitive too, and share colleague by colleague from the first screen. In every sensitive app, adding a person opens a confirm dialog that names them and lists what they will see, with a "Skip this step next time" checkbox (access skill doc).
780
780
 
781
781
  **How specific the request is sets what reaches the screen.** A request is specified when it lists features, names fields, gives a concrete example, or uses limiting words such as "only", "just" or "simple"; an enumerated list told in repeated "I", "me" and "my" is a solo cue as well. A first build shows what the platform can do inside the ask's own scope. It carries the features the ask names, each a direct control of its own. Beside them sits the baseline every app gets: a sparkle on every form, a way to share with its reason on the first screen of an app that is not privacy-sensitive, Ask where there are records to ask about, and a button that makes a picture wherever a picture would be great. Your bigger ideas — server work, a connection, taking payments, a generated world — become the options. A vague ask gets its alive defaults on screen, each wired, with the rest as options. Someone who does not know a capability exists cannot ask for it, so the baseline is how they meet it, in the place _The first phone screen_ gives it: a first vibe is the platform's own demo of itself, built around the thing the person asked for. Its sample content is the `seed.json` demo, and whether the app opens on it is the call above.
782
782