@vibes.diy/prompts 14.3.207 → 14.3.209

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/callai.md CHANGED
@@ -10,7 +10,7 @@ Name what the app does in the app's own words. The function name `callAI` stays
10
10
 
11
11
  ## Text to records
12
12
 
13
- When the person's own words describe input in the shape they already have it — typing entries in their own words, pasting a chat, replies or a list, a photo, adding things however they like — the sentence composer is the front door they asked for. When a specified request names its fields or features and describes no such input, the front door is a plain Add form for those fields; adding by sentence is the first of the closing `▸` options, phrased for this app, such as "Add plants by typing a sentence like 'basil and two tomatoes, bed 3'", and Ask is an option too. An open-ended request may open with the composer as one of its one or two alive defaults. Keep quantity steppers, claim buttons, and toggles on existing records as direct controls; they complement sentence creation. A name-only list, a simple message, and a timer stay direct because their input already is the whole record or an explicit setting.
13
+ When the person's own words describe input in the shape they already have it — typing entries in their own words, pasting a chat, replies or a list, a photo, adding things however they like — the sentence composer is the front door they asked for. When a specified request names its fields or features and describes no such input, the front door is a plain Add form for those fields; adding by sentence is the first of the closing `▸` options, phrased for this app, such as "Add plants by typing a sentence like 'basil and two tomatoes, bed 3'"; Ask sits beside the records from the first build, part of every app's baseline. An open-ended request opens with the composer among its alive defaults. Keep quantity steppers, claim buttons, and toggles on existing records as direct controls; they complement sentence creation. A name-only list, a simple message, and a timer stay direct because their input already is the whole record or an explicit setting.
14
14
 
15
15
  When the composer is on screen, wire these visible actions in the same build, using the app's own record names. One composer has Add and Ask actions. Add extracts and normalizes facts, saves each record immediately, and shows saved records with edit actions; one item and a pasted batch share this action. Each saved row has Change by sentence: selecting it changes Add to Apply correction, which saves onto that same record id. Ask sends the typed question with the relevant saved records and displays a read-only answer beside the composer. Edit opens the selected row’s populated fields. One parent-owned Undo restores the latest successful creation batch or the previous document from either a sentence correction or a field edit.
16
16
 
package/llms/image-gen.md CHANGED
@@ -170,7 +170,7 @@ export default function App() {
170
170
 
171
171
  ## Illustrations That Are Part of an Item's Identity
172
172
 
173
- When an item's picture is intrinsic to what it is — a card in a deck, a creature in a bestiary, a product in a catalog, a character in a cast — render `<ImgGen>` **by default** for every such item that lacks an image, so the illustration appears as soon as the item does. Because ImgGen auto-generates when the target doc has a `prompt` but no `_files` yet, mounting it directly on the item is all it takes:
173
+ When the ask names the pictures and an item's picture is what it is — a deck of illustrated cards, a bestiary, a character cast with portraits, a catalog shown as photos — render `<ImgGen>` **by default** for every such item that lacks an image, so the illustration appears as soon as the item does. Because ImgGen auto-generates when the target doc has a `prompt` but no `_files` yet, mounting it directly on the item is all it takes:
174
174
 
175
175
  ```jsx
176
176
  <ImgGen
@@ -180,7 +180,7 @@ When an item's picture is intrinsic to what it is — a card in a deck, a creatu
180
180
  />
181
181
  ```
182
182
 
183
- Let the first picture arrive with the item itself, so every card opens already illustrated and the app reads as a picture app from the first glance. For these items, buttons and `showControls` are for *regenerating* an image that already exists. Pictures that are extras rather than identity — an avatar upload, a one-off hero graphic, and the text-first snippets below — come from an explicit action the person chooses.
183
+ A picture the person asked for by name — the hero of an illustrated journal, the portrait a character maker exists for — arrives with the item itself, so that card opens already illustrated. Every other picture a record would be better with waits for a press: the card carries a quiet `IconButton` with the `photo` icon, labelled in the app's words ("Paint the cover", "Picture this dish"), inside the empty frame where the picture will land, and the press mounts `<ImgGen>` on that record's `_id` with the record's own prompt and saves the picture on it, so every later visitor sees it with no step. Once a picture exists, buttons and `showControls` are for *regenerating* it. Pictures that are extras rather than identity — an avatar upload, a one-off hero graphic, and the text-first snippets below — come from the same kind of explicit action.
184
184
 
185
185
  ## Pictures on Request for Text-First Snippets
186
186
 
package/llms/stripe.js CHANGED
@@ -1,7 +1,7 @@
1
1
  export const stripeConfig = {
2
2
  name: "stripe",
3
3
  label: "Stripe payments",
4
- description: "Taking real money through Stripe Checkout: load it whenever the person asks for money to move — pay the bill, split the check, a restaurant check, pay at the table or at the counter, a tip or a tip jar, donate or a donation page, sell tickets, sell products buyers pay for, buy now or purchase online, a charge, a deposit, dues, a checkout, pay with Stripe, or the word Stripe — one-time charges into the owner's own Stripe account through ctx.stripe, connected once with Connect Stripe (a monthly or yearly subscription is the stripe-subscriptions skill): what is for sale and its price is the owner's product catalog, product records in the app's database that only the owner writes (access.js) from the app's own Products screen, starting empty with the owner's first product, and backend.js charges the price it reads from the product the buyer names, never an amount from the browser or a constant in backend.js; guest checkout by default for paying a venue (a check, a tip, a donation — no sign-in, the payment keyed to the thing paid and its session, written by backend.js for the guest) and a signed-in order where the record is the buyer's to keep (dues on a roster, my orders), one payer paying the whole check by default with splitting as a second choice and the balance reserved with a revision-checked write before any session opens, the Connect Stripe setup item read from ctx.stripe.status(), test mode first with the order's mode passed on every call and live once the owner takes this app live, every Stripe call in backend.js with no Stripe.js in the page, one pending order then one Checkout Session opened in a new tab, an order marked paid only after the backend reads the session back from Stripe and matches it to the order, integer amounts in cents, and a scheduled sweep that settles orders whose buyer never came back. A storefront, plans page or booking page that only records orders takes no payment and does not need this; offer it as the [pay] option instead",
4
+ description: "Taking real money through Stripe Checkout: load it whenever the person asks for money to move — pay the bill, split the check, a restaurant check, pay at the table or at the counter, a tip or a tip jar, donate or a donation page, sell tickets, sell products buyers pay for, buy now or purchase online, a charge, a deposit, dues, a checkout, a client paying an invoice online (pay an invoice, bill a client), pay with Stripe, or the word Stripe — one-time charges into the owner's own Stripe account through ctx.stripe, connected once with Connect Stripe (a monthly or yearly subscription is the stripe-subscriptions skill): what is for sale and its price is the owner's product catalog, product records in the app's database that only the owner writes (access.js) from the app's own Products screen, starting empty with the owner's first product, and backend.js charges the price it reads from the product the buyer names, never an amount from the browser or a constant in backend.js; guest checkout by default for paying a venue (a check, a tip, a donation, an invoice paid by link with a pay-by date and an overdue state — no sign-in, the payment keyed to the thing paid and its session, written by backend.js for the guest) and a signed-in order where the record is the buyer's to keep (dues on a roster, my orders), one payer paying the whole check by default with splitting as a second choice and the balance reserved with a revision-checked write before any session opens, the Connect Stripe setup item read from ctx.stripe.status(), test mode first with the order's mode passed on every call and live once the owner takes this app live, every Stripe call in backend.js with no Stripe.js in the page, one pending order then one Checkout Session opened in a new tab, an order marked paid only after the backend reads the session back from Stripe and matches it to the order, integer amounts in cents, and a scheduled sweep that settles orders whose buyer never came back. A storefront, plans page, booking page or invoice maker that only records orders or marks invoices paid by hand takes no payment and does not need this; offer it as the [pay] option instead",
5
5
  cues: [
6
6
  "stripe",
7
7
  "take payments",
@@ -30,6 +30,16 @@ export const stripeConfig = {
30
30
  "donation",
31
31
  "donations",
32
32
  "pay with stripe",
33
+ "pay an invoice",
34
+ "pay the invoice",
35
+ "pay invoices",
36
+ "pay their invoice",
37
+ "pay my invoice",
38
+ "invoice payment",
39
+ "invoice payments",
40
+ "bill a client",
41
+ "bill clients",
42
+ "bill my clients",
33
43
  ],
34
44
  routeCues: [
35
45
  "with stripe",
@@ -1 +1 @@
1
- {"version":3,"file":"stripe.js","sourceRoot":"","sources":["../../jsr/llms/stripe.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,YAAY,GAAc;IACrC,IAAI,EAAE,QAAQ;IACd,KAAK,EAAE,iBAAiB;IACxB,WAAW,EACT,s8DAAs8D;IACx8D,IAAI,EAAE;QACJ,QAAQ;QACR,eAAe;QACf,cAAc;QACd,iBAAiB;QACjB,eAAe;QACf,cAAc;QACd,aAAa;QACb,UAAU;QACV,SAAS;QACT,MAAM;QACN,cAAc;QACd,SAAS;QACT,YAAY;QACZ,iBAAiB;QACjB,iBAAiB;QACjB,QAAQ;QACR,SAAS;QACT,cAAc;QACd,iBAAiB;QACjB,kBAAkB;QAClB,kBAAkB;QAClB,oBAAoB;QACpB,SAAS;QACT,QAAQ;QACR,UAAU;QACV,WAAW;QACX,iBAAiB;KAClB;IAKD,SAAS,EAAE;QACT,aAAa;QACb,gBAAgB;QAChB,YAAY;QACZ,cAAc;QACd,iBAAiB;QACjB,gBAAgB;QAChB,aAAa;QACb,cAAc;QACd,eAAe;QACf,cAAc;QACd,eAAe;QACf,eAAe;QACf,iBAAiB;KAClB;IAGD,aAAa,EAAE,CAAC,WAAW,EAAE,cAAc,EAAE,eAAe,EAAE,SAAS,EAAE,WAAW,EAAE,SAAS,CAAC;CACjG,CAAC"}
1
+ {"version":3,"file":"stripe.js","sourceRoot":"","sources":["../../jsr/llms/stripe.ts"],"names":[],"mappings":"AAWA,MAAM,CAAC,MAAM,YAAY,GAAc;IACrC,IAAI,EAAE,QAAQ;IACd,KAAK,EAAE,iBAAiB;IACxB,WAAW,EACT,wnEAAwnE;IAC1nE,IAAI,EAAE;QACJ,QAAQ;QACR,eAAe;QACf,cAAc;QACd,iBAAiB;QACjB,eAAe;QACf,cAAc;QACd,aAAa;QACb,UAAU;QACV,SAAS;QACT,MAAM;QACN,cAAc;QACd,SAAS;QACT,YAAY;QACZ,iBAAiB;QACjB,iBAAiB;QACjB,QAAQ;QACR,SAAS;QACT,cAAc;QACd,iBAAiB;QACjB,kBAAkB;QAClB,kBAAkB;QAClB,oBAAoB;QACpB,SAAS;QACT,QAAQ;QACR,UAAU;QACV,WAAW;QACX,iBAAiB;QAGjB,gBAAgB;QAChB,iBAAiB;QACjB,cAAc;QACd,mBAAmB;QACnB,gBAAgB;QAChB,iBAAiB;QACjB,kBAAkB;QAClB,eAAe;QACf,cAAc;QACd,iBAAiB;KAClB;IAKD,SAAS,EAAE;QACT,aAAa;QACb,gBAAgB;QAChB,YAAY;QACZ,cAAc;QACd,iBAAiB;QACjB,gBAAgB;QAChB,aAAa;QACb,cAAc;QACd,eAAe;QACf,cAAc;QACd,eAAe;QACf,eAAe;QACf,iBAAiB;KAClB;IAGD,aAAa,EAAE,CAAC,WAAW,EAAE,cAAc,EAAE,eAAe,EAAE,SAAS,EAAE,WAAW,EAAE,SAAS,CAAC;CACjG,CAAC"}
package/llms/stripe.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  When someone asks to **take money** — pay the bill at a table, split the check,
4
4
  take tips or donations, charge for a booking, collect dues, sell tickets, take
5
- a deposit, sell a download — build it on **Stripe
5
+ a deposit, sell a download, have a client pay an invoice — build it on **Stripe
6
6
  Checkout** from `backend.js`, through `ctx.stripe` — the owner connects their
7
7
  Stripe account once with **Connect Stripe**, and the platform holds the
8
8
  credential. This is a `backend.js` feature (see the backend docs for the
@@ -19,9 +19,12 @@ closing row's capability option is `▸ [pay] Take card payments with Stripe`,
19
19
  gold when nothing else fits better, and a tap on it is the ask. Words that are
20
20
  the ask: "charge", "pay", "paid", "payment", "pay the bill", "split the check",
21
21
  "tip", "donate", "deposit", "dues", "tickets", "sell", "buy now", "purchase online",
22
- "checkout", "Stripe".
22
+ "checkout", "pay an invoice", "pay the invoice online", "bill a client", "Stripe".
23
23
  Words that are not: "orders",
24
- "price", "plans", "cart" — those describe records, not money moving.
24
+ "price", "plans", "cart" — those describe records, not money moving. "Invoice"
25
+ on its own is not the ask either: an invoice maker where the owner writes
26
+ invoices and marks them paid by hand is bookkeeping, and stays that way until
27
+ the person asks for the client to pay through the app.
25
28
 
26
29
  **One-time charges only.** This recipe takes a payment and records that it
27
30
  happened. It does not mirror a Stripe subscription — cancellation, a failed
@@ -61,12 +64,14 @@ order keeps the price it was made at.
61
64
  A payment to a venue is guest checkout: the payer needs no Vibes DIY account, the payment record is keyed to the thing being paid and its Checkout Session, and backend.js writes it on the guest's behalf.
62
65
 
63
66
  A restaurant check, a split-the-check page, a tip jar, a donation page, a
64
- pay-at-the-counter page, event tickets bought on the spot — the payer is a
67
+ pay-at-the-counter page, event tickets bought on the spot, a client paying an
68
+ invoice — the payer is a
65
69
  guest at the owner's place, and Stripe's own page asks for their email and
66
70
  sends the receipt. Security rests on Stripe, not on a sign-in: the backend
67
71
  reads every session back from Stripe before anything counts as paid.
68
72
  *Guest checkout at a venue* at the end of this page is that recipe, with a
69
- table's check as the worked example.
73
+ table's check as the worked example, and *Invoices* after it is the same
74
+ recipe for a client paying a bill.
70
75
 
71
76
  Sign-in is the shape when the record belongs to a person over time: a member's
72
77
  dues on the roster, a booking under their name, a "my orders" or "my tickets"
@@ -983,6 +988,12 @@ pay-at-the-counter page is the same recipe with one line and no splitting.
983
988
  Staff open a check with its lines, its link goes on the table as a QR code,
984
989
  and anyone at the table opens it and pays, with no account.
985
990
 
991
+ A check may carry an optional pay-by date (`payBy`, a `YYYY-MM-DD` string the
992
+ owner picks, with the owner's time zone as `tz`). The page shows it under the
993
+ total, and a check past that date in the owner's time zone, with money still
994
+ left, reads *Overdue* on the owner's list and the payer's page alike.
995
+ A table's check rarely needs one; an invoice always has one.
996
+
986
997
  A check is paid by one payer by default: one primary button pays the whole remaining balance plus the tip, and splitting is a second choice the table opens.
987
998
 
988
999
  Below the primary *Pay $X*, a quiet *Split the check* opens the other two
@@ -1372,6 +1383,9 @@ export function checks(doc, oldDoc, user, ctx) {
1372
1383
  ctx.requireRole("owner");
1373
1384
  const priced = Array.isArray(doc.lines) && doc.lines.every((l) => typeof l.id === "string" && Number.isInteger(l.price) && l.price > 0);
1374
1385
  if (!priced) throw { forbidden: "each line has an id and a whole-cent price" };
1386
+ if (doc.payBy !== undefined && (!/^\d{4}-\d{2}-\d{2}$/.test(doc.payBy) || typeof doc.tz !== "string")) {
1387
+ throw { forbidden: "a pay-by date is YYYY-MM-DD, with the owner's time zone" };
1388
+ }
1375
1389
  if (oldDoc && oldDoc.lines.some((l) => !doc.lines.some((m) => m.id === l.id && m.price === l.price))) {
1376
1390
  throw { forbidden: "a check keeps the lines it opened with; add a new line instead" };
1377
1391
  }
@@ -1411,6 +1425,16 @@ import { Badge, Button, Field, Figure, Heading, Input, Metric, Row, Segmented, S
1411
1425
  import { Checkbox } from "@vibes.diy/ui/interactive";
1412
1426
 
1413
1427
  const money = (cents) => `$${(cents / 100).toFixed(2)}`;
1428
+ // A pay-by date is a YYYY-MM-DD in the owner's time zone, so every viewer sees the same day turn
1429
+ // over; past it with money left, the check is overdue.
1430
+ const today = (tz) => {
1431
+ try {
1432
+ return new Date().toLocaleDateString("en-CA", { timeZone: tz });
1433
+ } catch {
1434
+ return new Date().toLocaleDateString("en-CA");
1435
+ }
1436
+ };
1437
+ const overdue = (check, left) => Boolean(check?.payBy) && left > 0 && check.payBy < today(check.tz);
1414
1438
  const post = (body) => ({ method: "POST", headers: { "content-type": "application/json" }, body: JSON.stringify(body) });
1415
1439
  const TIPS = [
1416
1440
  { value: "0", label: "No tip" },
@@ -1510,8 +1534,9 @@ function CheckRow({ check, setup }) {
1510
1534
  <Row gap={2}>
1511
1535
  <Heading level={3}>{check.table}</Heading>
1512
1536
  {s.left === 0 ? <Badge tone="up">Paid in full</Badge> : <Badge tone="info">{money(s.left)} left</Badge>}
1537
+ {overdue(check, s.left) && <Badge tone="down">Overdue</Badge>}
1513
1538
  </Row>
1514
- <Text muted>{money(s.paid)} of {money(s.total)} paid · {link}</Text>
1539
+ <Text muted>{money(s.paid)} of {money(s.total)} paid{check.payBy ? ` · pay by ${check.payBy}` : ""} · {link}</Text>
1515
1540
  <Figure src={`https://api.qrserver.com/v1/create-qr-code/?size=200x200&data=${encodeURIComponent(link)}`} alt={`QR code for ${check.table}`} width={200} height={200} />
1516
1541
  </Stack>
1517
1542
  );
@@ -1525,6 +1550,7 @@ function Tables({ setup }) {
1525
1550
  const [lines, setLines] = useState([]);
1526
1551
  const [name, setName] = useState("");
1527
1552
  const [price, setPrice] = useState("");
1553
+ const [payBy, setPayBy] = useState(""); // optional
1528
1554
  const addLine = () => {
1529
1555
  const cents = Math.round(Number(price) * 100);
1530
1556
  if (!name.trim() || !(cents > 0)) return;
@@ -1533,13 +1559,15 @@ function Tables({ setup }) {
1533
1559
  setPrice("");
1534
1560
  };
1535
1561
  const openCheck = () => {
1536
- const check = { _id: "check-" + crypto.randomUUID(), type: "check", table: table.trim(), lines, currency: "usd", openedAt: Date.now() };
1562
+ const check = { _id: "check-" + crypto.randomUUID(), type: "check", table: table.trim(), lines, currency: "usd", openedAt: Date.now(), ...(payBy ? { payBy, tz: Intl.DateTimeFormat().resolvedOptions().timeZone } : {}) };
1537
1563
  // The form empties as the owner presses Open; the draft comes back only if the write is refused.
1538
1564
  setTable("");
1539
1565
  setLines([]);
1566
+ setPayBy("");
1540
1567
  database.put(check).catch(() => {
1541
1568
  setTable(check.table);
1542
1569
  setLines(check.lines);
1570
+ setPayBy(check.payBy ?? "");
1543
1571
  });
1544
1572
  };
1545
1573
  return (
@@ -1552,6 +1580,7 @@ function Tables({ setup }) {
1552
1580
  <Button variant="quiet" onClick={addLine}>Add item</Button>
1553
1581
  </Row>
1554
1582
  {lines.map((l) => <Text key={l.id}>{l.name} · {money(l.price)}</Text>)}
1583
+ <Field label="Pay by (optional)">{(id, describedBy) => <Input id={id} describedBy={describedBy} type="date" value={payBy} onChange={setPayBy} />}</Field>
1555
1584
  <Button onClick={openCheck} disabled={!table.trim() || lines.length === 0}>Open the check</Button>
1556
1585
  {checks.map((c) => <CheckRow key={c._id} check={c} setup={setup} />)}
1557
1586
  </Stack>
@@ -1644,6 +1673,12 @@ function TableCheck({ checkId, setup }) {
1644
1673
  <Metric label="Paid" value={money(s.paid)} />
1645
1674
  <Metric label="Left" value={money(s.left)} />
1646
1675
  </Row>
1676
+ {check.payBy && (
1677
+ <Row gap={2}>
1678
+ <Text muted>Pay by {check.payBy}</Text>
1679
+ {overdue(check, s.left) && <Badge tone="down">Overdue</Badge>}
1680
+ </Row>
1681
+ )}
1647
1682
  {check.lines.map((l) => (
1648
1683
  <Row key={l.id} gap={2}>
1649
1684
  <Text>{l.name}</Text>
@@ -1740,3 +1775,53 @@ A tip jar or a donation page keeps this shape with one standing check the
1740
1775
  owner opens once and amounts the backend prices from the page's own list, and
1741
1776
  no split. Staff who are not the owner open checks through a `staff` role, the
1742
1777
  way the access docs teach roles.
1778
+
1779
+ ## Invoices: a client pays a bill by link
1780
+
1781
+ An invoice a client pays online is the table's check with different words: the
1782
+ owner writes it with lines and amounts of their own choosing (no product
1783
+ catalog), the client opens its link and pays the whole balance on Stripe's
1784
+ page with no account, and the same ledger, `/confirm` read-back and sweep make
1785
+ *paid* a fact. Build it from the check recipe above and change only this:
1786
+
1787
+ - **The record is an invoice.** `type: "invoice"`, ids `inv-…`, and on top of
1788
+ the check's `lines` and `currency` it carries `client` (the name the owner
1789
+ bills, as the owner types it), `number` (the owner's invoice number, the
1790
+ next one after their highest prefilled in the form and theirs to change)
1791
+ and `payBy` with `tz`, both required here. `access.js` keeps the check's
1792
+ write rules: the owner writes it and the lines it opened with stay.
1793
+ - **An invoice is private; its link is the key.** A table's check sits on a
1794
+ public channel, which any visitor can list, and that is fine for a table's
1795
+ order but not for a client's name and bill. So an invoice and its ledgers go
1796
+ on an owner-only channel (`channels: ["invoices"]`,
1797
+ `grant: { roles: { owner: ["invoices"] } }`), and the client's page never
1798
+ queries the database: it asks backend.js, which reads unfiltered, through a
1799
+ `GET /invoice?id=` route that answers only about the invoice the id names —
1800
+ its client, number, lines, `payBy` and what is paid and left from its
1801
+ ledger — and `not-found` for anything else. The random `inv-<uuid>` id is
1802
+ the link's secret. The page asks on mount, on focus and on the way back from
1803
+ Stripe, in place of the check's live query; the owner's own screens keep
1804
+ their live queries.
1805
+ - **One payer, no tip, no split.** The client's page shows the invoice, its
1806
+ lines, *Pay by* and one *Pay $X* for what is left (`pay: "rest"`). Leave the
1807
+ tip choice and *Split the check* out; the backend keeps its `"rest"` path
1808
+ and its revision-checked reservation, so a client who opens the link twice
1809
+ still pays once.
1810
+ - **The owner sends the link.** The app stores no email address: each invoice
1811
+ on the owner's list has a *Copy link* button (`navigator.clipboard.writeText`
1812
+ of `…#invoice=<id>`) for the owner to paste into their own email or message,
1813
+ in place of the table's QR code. Stripe's page asks the client for their
1814
+ email and sends the receipt.
1815
+ - **Paid, open, overdue.** The owner's list reads each invoice's ledger: *Paid*
1816
+ at zero left, *Overdue* once today is past `payBy` with money left, *Open*
1817
+ otherwise, with a count of each above the list.
1818
+ - **Stripe's line item names the invoice**:
1819
+ `` `Invoice ${invoice.number} · ${invoice.client}` ``, and the session's
1820
+ `metadata` carries `invoiceId`, so the owner finds it in their Stripe
1821
+ Dashboard.
1822
+
1823
+ Every payment goes through Checkout like the rest of this page. Stripe's own
1824
+ Invoicing product is not part of this recipe: it needs Customer records with
1825
+ stored emails and charges a fee per paid invoice. An invoice maker that only
1826
+ records invoices and marks them paid by hand takes no payment and does not
1827
+ need this skill; offer `▸ [pay] Let clients pay invoices by card` instead.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vibes.diy/prompts",
3
- "version": "14.3.207",
3
+ "version": "14.3.209",
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.207",
43
- "@vibes.diy/call-ai-v2": "14.3.207",
44
- "@vibes.diy/identity": "14.3.207",
45
- "@vibes.diy/use-vibes-types": "14.3.207",
42
+ "@vibes.diy/api-types": "14.3.209",
43
+ "@vibes.diy/call-ai-v2": "14.3.209",
44
+ "@vibes.diy/identity": "14.3.209",
45
+ "@vibes.diy/use-vibes-types": "14.3.209",
46
46
  "arktype": "~2.2.8",
47
47
  "json-schema-faker": "~0.6.3"
48
48
  },