@mccaskie-labs/workbench-config 0.2.3 → 0.2.5

package/capabilities/images.json

@@ -7,8 +7,7 @@
   "status": "built",
   "delivery": {
     "choice": "built_in",
-    "intro": "Pictures made by AI from a description.",
-    "when": "The client wants a picture made by AI, such as an illustration, a hero image or a product mock-up, as a feature visitors use or once for the site."
+    "intro": "Pictures made by AI from a description."
   },
   "surfaces": {
     "gateway": [
@@ -209,5 +208,195 @@
       "refusal": "invalid_request",
       "cost_hint_usd": 0
     }
-  ]
+  ],
+  "offer": {
+    "pattern": "feature_or_content",
+    "when": "The client wants a picture made by AI, such as an illustration, a hero image or a product mock-up, as a feature visitors use or once for the site.",
+    "say": "I'll make this with Workbench pictures, made by AI through Workbench, so the app holds no image key and spending has a monthly cap.",
+    "answers_file": "workbench/images/<name>.json",
+    "per": "feature or picture",
+    "answers_format": "For a feature: `{ \"format\": 1, \"route\": \"feature\", \"name\", \"about\" (the client's words), \"who\", \"cap_usd\", \"job\" }`, where `job` is the `X-Workbench-Job` the feature's calls send (`<name>` with dots, such as `quotes.estimate`), so its spending shows on its own line in Control. Write it, then build the feature with the package. For a picture made once: `npx workbench-ai pick <name> <round>-<draft>` copies the picked picture to `public/images/<name>.png` (or .jpg) and writes the answers file with its prompt, model, request id and cost; never write one from nothing. Show it on the page from `/images/<name>.png`, with alt text that says what it shows. Drafts and their previews stay in `workbench/images/drafts/`, which isn't committed.",
+    "questions": [
+      {
+        "id": "images.route",
+        "sets": "route",
+        "ask": "Is this something visitors use on the site, or something made once for the site?",
+        "style": "cards",
+        "answers": [
+          {
+            "label": "Visitors use it",
+            "value": "feature",
+            "means": "A feature that makes a new picture each time someone uses it, such as a mock-up of their own design."
+          },
+          {
+            "label": "Made once for the site",
+            "value": "content",
+            "means": "A picture for the site, made once and kept: a hero image, an illustration for a page."
+          }
+        ],
+        "must_ask": true,
+        "note": "Ask it even when the client's words seem to say, as a quick check: the two routes are built and paid for differently."
+      },
+      {
+        "id": "images.who",
+        "sets": "feature.who",
+        "ask": "Who may use it?",
+        "style": "cards",
+        "answers": [
+          {
+            "label": "People who are signed in",
+            "value": "signed_in",
+            "means": "Anyone with an account. Each use is tied to a person, so misuse can be traced and stopped."
+          },
+          {
+            "label": "Admins only",
+            "value": "admins",
+            "means": "Only the business's own admins, for example a tool for writing their own posts."
+          },
+          {
+            "label": "Anyone visiting",
+            "value": "anyone",
+            "means": "No sign-in. The page checks for bots (Turnstile) and limits how often one visitor can use it."
+          }
+        ],
+        "when": {
+          "id": "images.route",
+          "is": [
+            "feature"
+          ]
+        },
+        "note": "Signed in means `requireUser` and admins means `app_admins`, as the workbench-sign-in skill says. For anyone, check Turnstile on every use and keep a per-visitor limit; say plainly that strangers can run up the cost. Pass `subject` on every call so the Gateway can tell people apart: `user:<id>` for a signed-in person, and for anyone a random id kept in a cookie (`visitor:<id>`), never an email address or name."
+      },
+      {
+        "id": "images.cap",
+        "sets": "feature.cap_usd",
+        "ask": "How much may it spend in a month, at most? When it's reached, the feature stops until next month.",
+        "style": "cards",
+        "answers": [
+          {
+            "label": "US$5 a month",
+            "value": 5,
+            "means": "A small trial, or light use."
+          },
+          {
+            "label": "US$20 a month",
+            "value": 20,
+            "means": "Steady use by a small business's visitors."
+          },
+          {
+            "label": "US$50 a month",
+            "value": 50,
+            "means": "Heavy use. It can be raised later."
+          }
+        ],
+        "other": {
+          "kind": "money",
+          "min": 1,
+          "max": 1000,
+          "description": "US dollars a month, whole or with cents."
+        },
+        "must_ask": true,
+        "when": {
+          "id": "images.route",
+          "is": [
+            "feature"
+          ]
+        },
+        "note": "Say roughly what one use costs (about US$0.07 a picture with image-default) so the owner can judge. The cap is the project's production cap for the `images` tool in the Gateway, shared by every feature that uses it: set it with Workbench Control's `gw_budget_set` (env production, tool images, monthly_usd). Raising a cap waits for the owner's approval on Control's approval page. When it is reached, calls fail with `budget_exceeded`: the page says the feature is resting until next month, never an error."
+      },
+      {
+        "id": "images.what",
+        "sets": [
+          "content.name",
+          "content.about"
+        ],
+        "ask": "What picture do you need?",
+        "style": "cards",
+        "answers": [
+          {
+            "label": "A hero image",
+            "value": "hero",
+            "means": "The large picture across the top of a page."
+          },
+          {
+            "label": "An illustration",
+            "value": "illustration",
+            "means": "A drawing for a page or a section."
+          },
+          {
+            "label": "A product mock-up",
+            "value": "mockup",
+            "means": "A product shown in use or in a setting."
+          }
+        ],
+        "other": {
+          "kind": "text",
+          "min": 3,
+          "max": 200,
+          "description": "What the picture is, in a few words."
+        },
+        "when": {
+          "id": "images.route",
+          "is": [
+            "content"
+          ]
+        },
+        "note": "Name the picture after where it goes (home_hero): lower case and underscores. The client's own words about what it shows and the feel they want go in --about."
+      },
+      {
+        "id": "images.shape",
+        "sets": "content.aspect",
+        "ask": "What shape should it be?",
+        "style": "cards",
+        "answers": [
+          {
+            "label": "Landscape (3:2)",
+            "value": "3:2",
+            "means": "Wider than tall, the usual shape for a page."
+          },
+          {
+            "label": "Wide banner (16:9)",
+            "value": "16:9",
+            "means": "For a picture across the top of a page."
+          },
+          {
+            "label": "Square (1:1)",
+            "value": "1:1",
+            "means": "For cards and social posts."
+          },
+          {
+            "label": "Portrait (2:3)",
+            "value": "2:3",
+            "means": "Taller than wide."
+          }
+        ],
+        "when": {
+          "id": "images.route",
+          "is": [
+            "content"
+          ]
+        },
+        "note": "Recommend the banner for a hero image. Pass it to the drafts command as --aspect."
+      }
+    ],
+    "not_asked": [
+      {
+        "sets": "model",
+        "why": "Drafts and features use image-default. image-pro costs about twice as much for finer detail and image-openai is cheapest; suggest one only when the client asks about quality or cost."
+      },
+      {
+        "sets": "references",
+        "why": "A reference picture (to make something like it) is only for a feature that needs one, and works with Google aliases only; offer it when the client mentions one."
+      }
+    ],
+    "drafts": {
+      "of": "pictures",
+      "surface": "images",
+      "alias": "image-default",
+      "count": 3,
+      "max_rounds": 3,
+      "job": "images.drafts",
+      "command": "npx workbench-ai drafts image <name> --about \"<what it shows, in the client's words>\" --aspect <shape>"
+    }
+  }
 }

package/capabilities/ui.json

@@ -7,8 +7,7 @@
   "status": "built",
   "delivery": {
     "choice": "optional",
-    "intro": "A ready-made look for the pages only you and your admins see.",
-    "when": "The client wants a page only the owner or the app's admins see: a dashboard, a list, a settings page or a status page."
+    "intro": "A ready-made look for the pages only you and your admins see."
   },
   "surfaces": {
     "package": [
@@ -95,5 +94,31 @@
   ],
   "styles": {
     "prefix": "wb-ui-"
+  },
+  "offer": {
+    "pattern": "switch_on",
+    "when": "The client wants a page only the owner or the app's admins see: a dashboard, a list, a settings page or a status page.",
+    "say": "I'll build this with the Workbench owner-page look, the same top bar, cards and pills as the other admin pages, so it's quick to build and consistent. Your customers never see it.",
+    "answers_file": "workbench/ui.json",
+    "answers_format": "`{ \"format\": 1, \"pages\": [{ \"path\": \"/admin/orders\", \"what\": \"every order this month, newest first\", \"who\": \"admins\" }] }`. Build each page with `shell`, `topBar`, `card` and `pill`. An `admins` page lives under `/admin/` and checks `requireUser` and `app_admins` (the workbench-sign-in skill); an `owner` page lives under `/owner/` and is behind Access in production.",
+    "questions": [
+      {
+        "id": "ui.pages",
+        "sets": "pages",
+        "ask": "Which admin pages should the app have?",
+        "style": "table",
+        "note": "Propose the pages the request needs, each with its path, what it shows or lets them change in the client's words, and who sees it: `admins` (the business's people, who sign in to the app) or `owner` (whoever runs the app's Workbench, through Access). Recommend `admins` unless the page is about running the app itself, such as a status page. The client accepts, removes or adds pages."
+      }
+    ],
+    "not_asked": [
+      {
+        "sets": "look",
+        "why": "Every admin page has the same Workbench look, so the business's people learn it once. Restyle it in project.css (see Restyling) if the client wants their colours."
+      },
+      {
+        "sets": "formats",
+        "why": "Times, amounts and durations on these pages come from workbench-ui's `when`, `money` and `duration`. What customers see uses the readers' formats (the workbench-country skill)."
+      }
+    ]
   }
 }