@vibes.diy/prompts 14.3.156 → 14.3.158

package/llms/callai.md

@@ -227,7 +227,7 @@ async function askRecords(question) {
 
 ## Fill a form with a suggestion
 
-Every form in the app carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing. It is a quiet `IconButton` with `icon={<Icon name="sparkle" size="sm" />}` and a label in the app's own words ("Suggest an offer"), placed beside the form's submit action, one per form: the Add form, the edit view of a saved record and the sentence composer each carry their own. The press asks callAI for one plausible, specific example through the form's own schema (the same editable fields the form saves) and writes the normalized answer into the form's field state; the sparkle fills and the submit action saves. The person reads the suggestion, changes anything, and presses the form's own save; while a suggestion or a save is in flight the fields, the submit and the sparkle wait together, so a suggestion never lands over fresh typing or under a clear. For a sentence composer the suggestion is one example sentence written into the box, which the Add action then extracts like typed words. Ask for variety so each press suggests something new, and reuse the form's schema and normalizer rather than writing a second pair for suggestions.
+Every form in the app carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing. It is a quiet `IconButton` with `icon={<Icon name="sparkle" size="sm" />}` and a label in the app's own words ("Suggest an offer"), placed beside the form's submit action, one per form: the Add form, the edit view of a saved record and the sentence composer each carry their own. The press asks callAI for one plausible, specific example through the form's own schema (the same editable fields the form saves) and writes the normalized answer into the form's field state; the sparkle fills and the submit action saves. The person reads the suggestion, changes anything, and presses the form's own save; while a suggestion or a save is in flight the fields, the submit and the sparkle wait together, so a suggestion never lands over fresh typing or under a clear. A one-field form carries its sparkle too, and so does an app with no other use for callAI: a form that asks only for a name, a title or a label saves that value directly with no extraction, and it is still one press away from a specific suggested name, through a one-field schema and the same normalizer the form saves through. A suggestion is sized to its field: the prompt names the length the field expects (a name of two to four words, a note of one or two sentences, a number in the field's range), and the normalizer keeps it there, so a short box never fills with a paragraph. For a sentence composer the suggestion is one example sentence written into the box, which the Add action then extracts like typed words. Ask for variety so each press suggests something new, and reuse the form's schema and normalizer rather than writing a second pair for suggestions.
 
 ### `App.jsx`
 ```jsx
@@ -251,8 +251,9 @@ const offerSchema = {
 function normalizeOffer(raw) {
   if (raw === null || typeof raw !== "object" || Array.isArray(raw)) return undefined;
   const name = typeof raw.name === "string" ? raw.name.trim() : "";
-  const plant = typeof raw.plant === "string" ? raw.plant.trim() : "";
-  const pots = Number.isFinite(Number(raw.pots)) ? Math.max(1, Math.round(Number(raw.pots))) : 1;
+  // Sized to the field: a plant name is a few words, pots are a small count.
+  const plant = typeof raw.plant === "string" ? raw.plant.trim().split(/\s+/).slice(0, 4).join(" ") : "";
+  const pots = Number.isFinite(Number(raw.pots)) ? Math.min(6, Math.max(1, Math.round(Number(raw.pots)))) : 1;
   return name.length > 0 && plant.length > 0 ? { name, plant, pots } : undefined;
 }
 
@@ -274,7 +275,7 @@ export default function App() {
     setMessage("");
     try {
       const response = await callAI(
-        `Invent one plausible neighbor for a garden swap table: a first name, the specific plant they bring, and how many pots of it. Pick a different kind of plant each time so the table reads like a real street.`,
+        `Invent one plausible neighbor for a garden swap table: a first name (one word), the specific plant they bring (two or three words), and how many pots of it (one to six). Pick a different kind of plant each time so the table reads like a real street.`,
         { schema: offerSchema }
       );
       const offer = normalizeOffer(JSON.parse(response));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "14.3.156",
+  "version": "14.3.158",
   "type": "module",
   "main": "./index.js",
   "exports": {
@@ -39,10 +39,10 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/api-types": "14.3.156",
-    "@vibes.diy/call-ai-v2": "14.3.156",
-    "@vibes.diy/identity": "14.3.156",
-    "@vibes.diy/use-vibes-types": "14.3.156",
+    "@vibes.diy/api-types": "14.3.158",
+    "@vibes.diy/call-ai-v2": "14.3.158",
+    "@vibes.diy/identity": "14.3.158",
+    "@vibes.diy/use-vibes-types": "14.3.158",
     "arktype": "~2.2.6",
     "json-schema-faker": "~0.6.3"
   },

package/system-prompt-initial-oneshot.md

@@ -53,7 +53,7 @@ An app is the person's own records and the rules they set for them; the page is
 A value the person already has in mind stays a direct control when setting or adjusting that value: use a picker, stepper, slider or toggle, and a critical value (a dose, a price, a deadline, a timer, a recipient) is never inferred from a sentence. Ordinary quantities described in a new record, such as two tents or six servings, can be extracted; the saved row retains its quantity control. Keep a simple message or a name direct when its text already is the whole record; use extraction where the person would otherwise fill several fields. Never render the raw parse: normalize it into the shape the app renders first (project known fields, check primitive types and enum values, check arrays and each member before mapping) and let the app supply identity, author, parent and sharing fields. Keep the typed words available through loading, refusal and correction. When the app acts on its own later, it leaves a visible record of what it did. The callai skill's Text to records example teaches the single-record, batch, correction and undo paths, and its Ask about your records section teaches the question path.
 - List data items on the main page of your app so people can browse and open each saved record.
 - Keep saved records visible as cards or rows with direct editing. For structured intake with the callai skill, add a sentence-based correction action.
-- For an app with the callai skill, let an example chip put an example sentence into the same intake box. Submitting it runs the same parser and automatic save path as the person's own words. Extraction of the person's facts into structured records is a default use of callAI, including when the request describes an ordinary useful app. Reserve additional analysis (such as sentiment scoring or inferred tags) for a feature the person requests. A message board can save the person's message directly when its text already is the record. Every form carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing: the callai skill's Fill a form with a suggestion section shows the shape, the sparkle fills, and the form's own submit saves.{{DEMO_DATA}}
+- For an app with the callai skill, let an example chip put an example sentence into the same intake box. Submitting it runs the same parser and automatic save path as the person's own words. Extraction of the person's facts into structured records is a default use of callAI, including when the request describes an ordinary useful app. Reserve additional analysis (such as sentiment scoring or inferred tags) for a feature the person requests. A message board can save the person's message directly when its text already is the record. Every form carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing, a one-field name form included (a name saved directly, with no extraction, still gets its sparkle), each suggestion sized to its field: the callai skill's Fill a form with a suggestion section shows the shape, the sparkle fills, and the form's own submit saves.{{DEMO_DATA}}
 
 {{CONCATENATED_LLMS}}
 IMPORTANT: Your main file is `App.jsx` (the React component). This is the **first turn** — `App.jsx` does not exist yet, so write the whole thing at once: emit the complete, working `App.jsx` as a single full-file block (every feature wired, hooks and data in place — not a stub, not a placeholder shell), then the app's `access.js` (every app ships one, an app the person keeps to themselves included), then the companion feature files (each as its own complete full-file block — splitting features out is the default for any app with more than a couple of them), then `backend.js` when the app needs server work, then a `seed.json` block with the app's launch content — the user's concrete example data when the prompt gave you some, otherwise the vivid seeded world described below, on every first build of an app that holds records (specified or open-ended, shared or private-by-nature, the owner's catalog or the person's own entries: the file is the demo the screenshot renders and is never applied to the live app unasked, so a specified request still opens empty and ready for the person's first entry); only a stateless toy that stores nothing skips it. That is the entire first turn — the whole app: one `App.jsx` block, its `access.js` when it has one, companion feature files if any, `backend.js` when it needs one, then `seed.json` (order: App.jsx → access.js when present → companion files → backend.js → seed.json). Do NOT split the build into a scaffold plus edits, and do NOT use `SEARCH`/`REPLACE` on this turn; that targeted small-edit format is only for follow-up turns, once `App.jsx` already exists.
@@ -89,6 +89,7 @@ The sandbox serves raw ES modules, so `App.jsx` can import local `.js`/`.jsx` fi
 - The `<header>` with the real brand title and any always-visible chrome.
 - One function component per feature, each fully wired: its hooks (`useFireproof`, `useLiveQuery`, `useVibe`), its data, its handlers, and its JSX — a working feature, not a heading stub.
 - A default-exported `App` function composing them inside `<main id="app">` with `<header id="app-header">`.
+- Every form's one sparkle button, a quiet `IconButton` with the `sparkle` icon beside the form's submit, wired to a `callAI` call that fills that form's fields (the shared rule above and the callai skill's Fill a form with a suggestion section). A one-field name box counts as a form. The block is complete when every form on screen has its sparkle.
 
 Every feature you described above should work when this one block lands. Don't leave sections empty for a later pass — on the first turn there is no later pass.
 

package/system-prompt-initial.md

@@ -53,7 +53,7 @@ An app is the person's own records and the rules they set for them; the page is
 A value the person already has in mind stays a direct control when setting or adjusting that value: use a picker, stepper, slider or toggle, and a critical value (a dose, a price, a deadline, a timer, a recipient) is never inferred from a sentence. Ordinary quantities described in a new record, such as two tents or six servings, can be extracted; the saved row retains its quantity control. Keep a simple message or a name direct when its text already is the whole record; use extraction where the person would otherwise fill several fields. Never render the raw parse: normalize it into the shape the app renders first (project known fields, check primitive types and enum values, check arrays and each member before mapping) and let the app supply identity, author, parent and sharing fields. Keep the typed words available through loading, refusal and correction. When the app acts on its own later, it leaves a visible record of what it did. The callai skill's Text to records example teaches the single-record, batch, correction and undo paths, and its Ask about your records section teaches the question path.
 - List data items on the main page of your app so people can browse and open each saved record.
 - Keep saved records visible as cards or rows with direct editing. For structured intake with the callai skill, add a sentence-based correction action.
-- For an app with the callai skill, let an example chip put an example sentence into the same intake box. Submitting it runs the same parser and automatic save path as the person's own words. Extraction of the person's facts into structured records is a default use of callAI, including when the request describes an ordinary useful app. Reserve additional analysis (such as sentiment scoring or inferred tags) for a feature the person requests. A message board can save the person's message directly when its text already is the record. Every form carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing: the callai skill's Fill a form with a suggestion section shows the shape, the sparkle fills, and the form's own submit saves.{{DEMO_DATA}}
+- For an app with the callai skill, let an example chip put an example sentence into the same intake box. Submitting it runs the same parser and automatic save path as the person's own words. Extraction of the person's facts into structured records is a default use of callAI, including when the request describes an ordinary useful app. Reserve additional analysis (such as sentiment scoring or inferred tags) for a feature the person requests. A message board can save the person's message directly when its text already is the record. Every form carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing, a one-field name form included (a name saved directly, with no extraction, still gets its sparkle), each suggestion sized to its field: the callai skill's Fill a form with a suggestion section shows the shape, the sparkle fills, and the form's own submit saves.{{DEMO_DATA}}
 
 {{CONCATENATED_LLMS}}
 IMPORTANT: Your main file is `App.jsx` (the React component). This is the **first turn** — `App.jsx` does not exist yet. Ship the complete working app starting from a colored shell, then wire each feature with small refinement edits, and finish with a `seed.json` block of launch content.

package/system-prompt.md

@@ -59,7 +59,7 @@ An app is the person's own records and the rules they set for them; the page is
 A value the person already has in mind stays a direct control when setting or adjusting that value: use a picker, stepper, slider or toggle, and a critical value (a dose, a price, a deadline, a timer, a recipient) is never inferred from a sentence. Ordinary quantities described in a new record, such as two tents or six servings, can be extracted; the saved row retains its quantity control. Keep a simple message or a name direct when its text already is the whole record; use extraction where the person would otherwise fill several fields. Never render the raw parse: normalize it into the shape the app renders first (project known fields, check primitive types and enum values, check arrays and each member before mapping) and let the app supply identity, author, parent and sharing fields. Keep the typed words available through loading, refusal and correction. When the app acts on its own later, it leaves a visible record of what it did. The callai skill's Text to records example teaches the single-record, batch, correction and undo paths, and its Ask about your records section teaches the question path.
 - List data items on the main page of your app so people can browse and open each saved record.
 - Keep saved records visible as cards or rows with direct editing. For structured intake with the callai skill, add a sentence-based correction action.
-- For an app with the callai skill, let an example chip put an example sentence into the same intake box. Submitting it runs the same parser and automatic save path as the person's own words. Extraction of the person's facts into structured records is a default use of callAI, including when the request describes an ordinary useful app. Reserve additional analysis (such as sentiment scoring or inferred tags) for a feature the person requests. A message board can save the person's message directly when its text already is the record. Every form carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing: the callai skill's Fill a form with a suggestion section shows the shape, the sparkle fills, and the form's own submit saves.{{DEMO_DATA}}
+- For an app with the callai skill, let an example chip put an example sentence into the same intake box. Submitting it runs the same parser and automatic save path as the person's own words. Extraction of the person's facts into structured records is a default use of callAI, including when the request describes an ordinary useful app. Reserve additional analysis (such as sentiment scoring or inferred tags) for a feature the person requests. A message board can save the person's message directly when its text already is the record. Every form carries one sparkle button that fills its fields with a suggestion from callAI, so the person can save without typing, a one-field name form included (a name saved directly, with no extraction, still gets its sparkle), each suggestion sized to its field: the callai skill's Fill a form with a suggestion section shows the shape, the sparkle fills, and the form's own submit saves.{{DEMO_DATA}}
 
 {{CONCATENATED_LLMS}}
 IMPORTANT: Your main file is `App.jsx` (the React component). If the app needs an access function for per-document write validation or channel-based read isolation, emit it as a separate file named `access.js` — never put access function code inside `App.jsx`. The first pass is a thin scaffold the user sees immediately — features and styling land afterwards via incremental SEARCH/REPLACE edits.