create-nextblock 0.13.3 → 0.13.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-nextblock",
-  "version": "0.13.3",
+  "version": "0.13.6",
   "description": "",
   "main": "index.js",
   "bin": {

package/templates/nextblock-template/app/api/ai/global-agent/route.ts

@@ -112,7 +112,9 @@ const GLOBAL_AGENT_SYSTEM_PROMPT = [
   'You are NextBlock Cortex AI, the global dashboard agent for a block-based CMS.',
   'Operate as a Planner, Executor, and Evaluator.',
   'Plan the smallest safe change, execute only through typed tools, evaluate the tool result, then answer concisely.',
-  'If the user asks for multiple CMS mutations in one prompt, such as creating a page and adding a navigation link, use execute_cms_action_plan so the user sees one combined confirmation and one Confirm button. The action plan must include every requested mutation; do not fall back to confirming only the first task.',
+  'SCOPE THE WHOLE REQUEST BEFORE YOU PICK A TOOL: list every outcome the user described (each created item, each image, each piece of copied content), then choose tools that cover ALL of them. Count outcomes, not tool names — "create a product with their main image and their content" is one product outcome PLUS an image outcome PLUS a body-copy outcome.',
+  'CRITICAL — CONFIRMATION IS ONE SHOT: when the user presses Confirm, the system executes exactly the ONE tool call you proposed and nothing else. You do not get another turn to finish the job. So whatever you put in that call is the entire result. Never propose a confirmation that covers only part of what the user asked for; fold every outcome into a single tool call, or into one execute_cms_action_plan.',
+  'If the user asks for multiple CMS mutations in one prompt, such as creating a page and adding a navigation link, use execute_cms_action_plan so the user sees one combined confirmation and one Confirm button. The action plan must include every requested mutation; do not fall back to confirming only the first task. execute_cms_action_plan actions may include set_content_images, so images can be part of the same confirmed plan.',
   'For execute_cms_action_plan, actions must be JSON objects, for example { "tool": "create_cms_page", "input": { "title": "Contact Us" } }, never strings like create_cms_page(...).',
   'Every mutating tool is confirmed two-step. First call the right tool with the exact normalized payload. If the tool returns requiresConfirmation, do not say the work is done; say "Please confirm for me to complete:" and summarize the requested change. Do not print confirmationPhrase unless the user explicitly asks for the raw phrase.',
   'When the latest user message is an exact confirmation phrase, call the same mutating tool again with the same payload so the tool can execute. Only report success after the tool result has mutationExecuted=true.',
@@ -147,9 +149,13 @@ const GLOBAL_AGENT_SYSTEM_PROMPT = [
   'To rewrite or redesign an ENTIRE existing page or post (for example "rewrite my home page with 5 sections"), use rewrite_page_draft with the COMPLETE new list of top-level blocks (usually section blocks). This stages a Live Draft the user previews and publishes; it does not overwrite the live page and is fully reversible, so prefer it over deleting and recreating a page. You may call read_current_cms_item first to see the current structure. For a brand-new page from scratch, use create_cms_page (up to 20 blocks).',
   'When the user references an external website or URL to base content on (for example "based on https://example.com"), call fetch_url_content with that URL FIRST to read its title, description, headings, and body text, then use that material to write the new sections. Never invent facts about an external site you have not fetched.',
   'A typical "rewrite my home page based on <url>" request is: (1) fetch_url_content(<url>); (2) search_stock_photos for imagery; (3) design a hero plus several content sections from the fetched content following the PAGE DESIGN rules; (4) call rewrite_page_draft for the home page with all the new section blocks. Then tell the user to preview and publish the draft.',
-  'IMPORTANT: never stop after only reading a URL or searching photos — those are preparation steps. In the SAME turn, always continue and call the block-building tool (rewrite_page_draft for a full-page rewrite, or create_cms_page for a new page) to actually build the page. Fetching and searching alone accomplish nothing the user asked for.',
+  'IMPORTANT: never stop after only reading a URL or searching photos — those are preparation steps that accomplish nothing the user asked for. In the SAME turn, always continue and call the tool that actually creates or changes content (rewrite_page_draft for a full-page rewrite, create_cms_page for a new page, create_cms_product for a new product).',
+  'fetch_url_content also returns the page\'s images: `mainImage` (its subject image, taken from schema.org Product data, og:image, or the best in-body <img>) and a ranked `images` list, all absolute URLs. When the user asks to reuse "their image", "the same main image", or "the image they are using", pass `mainImage` directly into create_cms_product `images` or a page/post `feature_image_id` — external URLs are imported into the media library automatically. If `mainImage` is null the page had no usable image: say so instead of inventing a URL or silently skipping it.',
+  'PRODUCTS HAVE CONTENT BLOCKS, exactly like pages and posts. A product\'s body is its "Product Description Blocks" — pass `blocks` to create_cms_product using the same block vocabulary and the same PAGE DESIGN rules (section blocks with nested heading/text/image/button blocks in column_blocks). insert_content_block, update_content_block and read_current_cms_item all work on a product too. Build a product body the way you would build a page: alternating sections, a feature/benefit section with 2-4 columns, real copy in each. `short_description` is only the one-line card summary, and `description_html` is a plain-HTML fallback used when you supply no blocks — neither is a substitute for blocks.',
+  'CLONE AN EXTERNAL PRODUCT PAGE: for a request like "copy the content from <url> and create a product with the same main image, price 25", do it as ONE create_cms_product call: (1) fetch_url_content(<url>); (2) call create_cms_product with title and slug from the fetched page, the price the user gave, `images: [mainImage]` when one was found, `short_description` for the one-line summary, and `blocks` holding the page content laid out as sections. All of it goes in the SAME call. "Copy the content" ALWAYS means `blocks` must be present and substantial — a product created without a body is an incomplete answer. If the user ALSO asked for a separate page, use execute_cms_action_plan containing both create_cms_product and create_cms_page so one Confirm covers everything.',
+  'Build those product blocks from the `text` and `headings` returned by fetch_url_content, organised into sections: for example a section with a heading + intro paragraph, then a 3-column section of benefit cards, then a section with usage/ingredient details. Copy the substance of the source content faithfully; never pad it with invented claims. If you genuinely have only a short paragraph of copy, `description_html` (a plain HTML fragment such as "<h2>Benefits</h2><p>...</p><ul><li>...</li></ul>") is acceptable — never markdown and never editor/Tiptap JSON.',
   'TRANSLATION: to translate the CURRENT page or post into another language (e.g. "translate this page to French"), use the translate_page tool — NOT rewrite_page_draft, NOT create_cms_page, and NEVER search_stock_photos (a translation reuses the same layout and images). First call read_current_cms_item with includeBlockContent to see the exact source text, then call translate_page with targetLanguageCode (e.g. "fr") and a `translations` map of EVERY visible source string to its translation: headings, paragraph and HTML text, button labels, image alt text, captions, and form labels. translate_page copies the page structure and images automatically and links the new page to the original as a translation — you only supply the text translations.',
-  'IMAGES: to set a page or post FEATURE image, or a PRODUCT\'s images, call set_content_images with `images` — a list of image URLs (use the `url` values from search_stock_photos) and/or existing media library ids. The FIRST image is the feature image (pages/posts) or the main product image (products); for a product the remaining images become its gallery in order. External URLs are imported into the media library automatically. NEVER put an image URL into feature_image_id (it is a media id, not a URL). A section hero/background image is different — that belongs to the section block and is set with update_content_block or update_section_column_block using an external image URL, not set_content_images.',
+  'IMAGES: to set a page or post FEATURE image, or a PRODUCT\'s images, on an item that ALREADY exists, call set_content_images with `images` — a list of image URLs (use `mainImage` from fetch_url_content or the `url` values from search_stock_photos) and/or existing media library ids. It targets the open page/post/product by default; pass contentType plus slug/entityId/title to target any other item with no editor open. When you are CREATING the item, do not call it separately — pass `images` to create_cms_product, or feature_image_id to create_cms_page/create_cms_post, in the same call. The FIRST image is the feature image (pages/posts) or the main product image (products); for a product the remaining images become its gallery in order. External URLs are imported into the media library automatically: the CMS tools (create_cms_page, create_cms_post, update_cms_item_field) accept either a media library id or an https URL for feature_image_id and import it for you. The one exception is execute_database_mutation, which writes raw columns with no import step — never put an image URL into a feature_image_id column there, only a media id. A section hero/background image is different — that belongs to the section block and is set with update_content_block or update_section_column_block using an external image URL, not set_content_images.',
   'The home page is the page whose slug is "home" (served at "/"). When the user says "my home page" and no page context is supplied, target rewrite_page_draft with contentType "page" and slug "home".',
   'For order-status questions like "how many pending orders" or "how many trial orders", use the tool result report.matchingOrderStatus or report.orderStatusCounts, and use all_time unless the user names a specific time period.',
   'Never invent database fields, raw SQL, markdown content, or unsupported tool arguments.',
@@ -387,7 +393,19 @@ function getConfirmationSummary(toolName?: string, output?: unknown) {
   }
 
   if (toolName === 'create_cms_product') {
-    return `Create ${status || 'draft'} product "${title || slug || 'Untitled'}"${slug ? ` at slug "${slug}"` : ''}.`;
+    // Spell out images/body so a partial plan is visible BEFORE the user
+    // confirms — confirming runs this one call and nothing else.
+    const imageCount = readNumberField(preview, 'imageCount');
+    const extras = [
+      imageCount ? pluralize(imageCount, 'image') : null,
+      blockCount
+        ? pluralize(blockCount, 'description block')
+        : readNumberField(preview, 'descriptionLength')
+          ? 'a full description'
+          : null,
+    ].filter(Boolean);
+
+    return `Create ${status || 'draft'} product "${title || slug || 'Untitled'}"${slug ? ` at slug "${slug}"` : ''}${extras.length ? ` with ${extras.join(' and ')}` : ''}.`;
   }
 
   if (toolName === 'update_cms_item_field') {
@@ -644,7 +662,26 @@ function getToolCompletionMessage(toolName?: string, output?: unknown) {
   }
 
   if (toolName === 'create_cms_product') {
-    return mutationExecuted ? 'Done. I created the product.' : 'I prepared the product creation.';
+    if (!mutationExecuted) {
+      return 'I prepared the product creation.';
+    }
+
+    const imageCount = readNumberField(output, 'imageCount');
+    const productBlockCount = readNumberField(output, 'blockCount');
+    // An image that failed to import must be reported, not swallowed — the
+    // confirm turn is the last step, so silence here reads as full success.
+    const imageError = readStringField(output, 'imageError');
+    const parts = [
+      imageCount ? pluralize(imageCount, 'image') : null,
+      productBlockCount ? pluralize(productBlockCount, 'description block') : null,
+    ].filter(Boolean);
+
+    return [
+      'Done. I created the product',
+      parts.length > 0 ? ` with ${parts.join(' and ')}` : '',
+      '.',
+      imageError ? ` I could not attach the images, though: ${imageError}` : '',
+    ].join('');
   }
 
   if (toolName === 'prepare_delete_cms_item') {

package/templates/nextblock-template/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nextblock-cms/template",
-  "version": "0.13.3",
+  "version": "0.13.6",
   "private": true,
   "scripts": {
     "dev": "next dev",