@jigs.design/prompt 0.1.1 → 0.1.2

package/README.md

@@ -2,7 +2,7 @@
 
 Renders the text the model reads: the system prompt from a host, and the repair text from diagnostics. `@jigs.design/server` uses it; you import it to read or test the prompt a host produces.
 
-The system prompt carries the app's `instructions`, then lists the host's procedures, components and recipes, and ends with the host's design guidance (`## Design`: shared, then the mode's) and situations (`## Situations`: how to choose, then each with its When line, guidance and example). It writes each procedure's input and output out as types, with each field's `.describe()` text and constraints as a comment, and shared enums declared once. It has two modes: `document`, where the whole reply is one UI, and `chat`, where the reply is Markdown with fenced `pickle` blocks.
+The system prompt carries the app's `instructions`, then lists the host's procedures, components and recipes, and ends with the host's design guidance (`## Design`: shared, then the mode's) and situations (`## Situations`: how to choose, then each with its When line, guidance and example). It writes each procedure's input and output out as types, with each field's `.describe()` text and constraints as a comment, and shared enums declared once. It has two modes: `document`, where the whole reply is one UI, and `chat`, where the reply is Markdown with fenced `jigs` blocks.
 
 ## Exports
 

package/dist/repair.d.ts

@@ -10,7 +10,7 @@ interface RepairAdvice {
 /**
  * The follow-up turn asking the model to fix the errors in its last answer,
  * and any design advice the app chose to repair. With advice alone, it says
- * the Pickle works and asks for the design change.
+ * the Jigs works and asks for the design change.
  */
 export declare function repairText(diagnostics: ReadonlyArray<Diagnostic>, advice?: ReadonlyArray<RepairAdvice>): string;
 /** An edit block that did not apply, as `applyEdits` and the server report it. */

package/dist/repair.js

@@ -7,7 +7,7 @@ function needsRepair(diagnostics) {
 /**
 * The follow-up turn asking the model to fix the errors in its last answer,
 * and any design advice the app chose to repair. With advice alone, it says
-* the Pickle works and asks for the design change.
+* the Jigs works and asks for the design change.
 */
 function repairText(diagnostics, advice = []) {
 	const seen = /* @__PURE__ */ new Set();
@@ -20,14 +20,14 @@ function repairText(diagnostics, advice = []) {
 	});
 	const lines = issues.slice(0, MAX_ISSUES).map((issue) => `- Line ${issue.span.line}: ${issue.message}`);
 	if (issues.length > MAX_ISSUES) lines.push(`- ...and ${issues.length - MAX_ISSUES} more`);
-	if (errors.length === 0) return `Your Pickle works, but its design can be better. Line numbers refer to your last answer.
+	if (errors.length === 0) return `Your jig works, but its design can be better. Line numbers refer to your last answer.
 ${lines.join("\n")}
 
-Change that and keep everything else as it is. Reply with edit blocks, or with the complete corrected Pickle if the change is large.`;
-	return `Your Pickle has problems. Line numbers refer to your last answer.
+Change that and keep everything else as it is. Reply with edit blocks, or with the complete corrected Jigs if the change is large.`;
+	return `Your jig has problems. Line numbers refer to your last answer.
 ${lines.join("\n")}
 
-Fix them and keep everything that already works. Reply with edit blocks, or with the complete corrected Pickle if the fix is large.`;
+Fix them and keep everything that already works. Reply with edit blocks, or with the complete corrected Jigs if the fix is large.`;
 }
 /** Letter pairs of a line without its indentation, for a rough similarity. */
 function pairs(line) {
@@ -126,7 +126,7 @@ const EDIT_ADVICE = {
 * the current UI it concerns, so the next edits land where they were meant.
 */
 function editRepairText(edit, source) {
-	return [...failureParts(edit, source), `${EDIT_ADVICE[edit.reason]}, or with the complete updated Pickle if the change is large.`].join("\n\n");
+	return [...failureParts(edit, source), `${EDIT_ADVICE[edit.reason]}, or with the complete updated Jigs if the change is large.`].join("\n\n");
 }
 /**
 * Asks for the whole document after an edit did not apply. It repeats what
@@ -134,7 +134,7 @@ function editRepairText(edit, source) {
 * SEARCH text, so the rewrite makes that change and nothing else.
 */
 function fullDocumentText(edit, source) {
-	return [...failureParts(edit, source), "Reply with the complete updated Pickle instead of edits: the current UI with this change made, and everything else kept as it is."].join("\n\n");
+	return [...failureParts(edit, source), "Reply with the complete updated Jigs instead of edits: the current UI with this change made, and everything else kept as it is."].join("\n\n");
 }
 //#endregion
 export { editRepairText, fullDocumentText, needsRepair, repairText };

package/dist/system-prompt.d.ts

@@ -13,9 +13,9 @@ export interface PromptOptions {
   mode?: PromptMode;
 }
 /**
- * The system prompt for writing Pickle against `host`. In document mode
+ * The system prompt for writing Jigs against `host`. In document mode
  * (the default) every reply is one UI, as a session expects; in chat mode a
- * reply is Markdown with UIs in fenced `pickle` blocks. Everything but the
+ * reply is Markdown with UIs in fenced `jigs` blocks. Everything but the
  * output section and the mode's design guidance is the same in both.
  *
  * What stays the same from turn to turn comes first, so a provider can

package/dist/system-prompt.js

@@ -3,7 +3,7 @@ import { sharedObjects, sharedTypes } from "./shared-types.js";
 import { recipeSignature } from "@jigs.design/compiler";
 import { dataSchema } from "@jigs.design/host";
 //#region src/system-prompt.ts
-const PICKLE = `Pickle is Markdown for prose, JSX-like tags for components from a fixed catalog, and \`{@body ...}\` lines of JavaScript for state and logic.`;
+const JIGS = `Jigs is Markdown for prose, JSX-like tags for components from a fixed catalog, and \`{@body ...}\` lines of JavaScript for state and logic.`;
 const EDIT_BLOCK = `<<<<<<< SEARCH
 exact lines from the current UI
 =======
@@ -11,23 +11,23 @@ the new lines
 >>>>>>> REPLACE
 - Copy SEARCH lines exactly, indentation included, with enough lines to be unique. Use one block per place you change, in document order. An empty SEARCH appends to the end.`;
 /** Every reply is one UI: the whole document, or edits to the last one. */
-const DOCUMENT_OUTPUT = `You write interactive user interfaces in Pickle. ${PICKLE}
+const DOCUMENT_OUTPUT = `You write interactive user interfaces in Jigs. ${JIGS}
 
 ## Output
-- Reply with Pickle only. No code fences, no explanation before or after it.
+- Reply with Jigs only. No code fences, no explanation before or after it.
 
 ## Changing an existing UI
 When asked to change a UI you wrote earlier:
 - For a focused change, reply with edit blocks only, no other text:
 ${EDIT_BLOCK}
-- If the change rewrites most of the UI, reply with the complete updated Pickle instead.`;
+- If the change rewrites most of the UI, reply with the complete updated Jigs instead.`;
 const OUTPUT = {
-	chat: `You reply in Markdown, and you can show interactive user interfaces in your replies by writing Pickle. ${PICKLE}
+	chat: `You reply in Markdown, and you can show interactive user interfaces in your replies by writing Jigs. ${JIGS}
 
 ## Output
 - Answer in Markdown, as in any chat. Most replies need no UI.
-- When a UI helps more than prose (live data, a form, a comparison, a chart, anything to click), write it in Pickle inside a fenced block that opens with \`\`\`pickle and a short kebab-case id, and closes with \`\`\`:
-\`\`\`pickle monthly-spending
+- When a UI helps more than prose (live data, a form, a comparison, a chart, anything to click), write it in Jigs inside a fenced block that opens with \`\`\`jigs and a short kebab-case id, and closes with \`\`\`:
+\`\`\`jigs monthly-spending
 # Spending this month
 ...
 \`\`\`
@@ -35,13 +35,13 @@ const OUTPUT = {
 - You never see what a query returns: the UI reads it when it runs, after your reply. So your prose must not state figures, totals or conclusions about the user's data; say what the UI shows instead.
 - Tags, recipes and \`{@body}\` lines work only inside a block. Outside one, write plain Markdown: no tags, no HTML and no tool-call markup, which would show as text.
 - A reply may hold several blocks, each with its own id. Each block is a separate UI: it cannot see another block's state.
-- Never put Pickle in any other fence, and never put a fence inside a block.
+- Never put Jigs in any other fence, and never put a fence inside a block.
 
 ## Changing an earlier UI
 - To change a UI from earlier in the conversation, write a block with the same id. It shows the new version in your reply; the old one stays where it was.
 - For a focused change, the block holds only edit blocks against that UI's latest version:
 ${EDIT_BLOCK}
-- If the change rewrites most of the UI, put the complete updated Pickle in the block instead.
+- If the change rewrites most of the UI, put the complete updated Jigs in the block instead.
 - A new id makes a new UI.`,
 	document: DOCUMENT_OUTPUT
 };
@@ -201,7 +201,7 @@ function actionSection(name, procedure, names) {
 	].join("\n");
 }
 const RECIPES_INTRO = `## Recipes
-Components written in Pickle for this app. Use them like any tag, with the props shown; a bare prop is required. They are already defined: never write their <define>. Prefer a recipe over building the same thing from components.`;
+Components written in Jigs for this app. Use them like any tag, with the props shown; a bare prop is required. They are already defined: never write their <define>. Prefer a recipe over building the same thing from components.`;
 function recipeSection(entry) {
 	const lines = [`### ${recipeSignature({
 		name: entry.name,
@@ -279,9 +279,9 @@ function typesSection(heading, intro, declarations) {
 	].join("\n")];
 }
 /**
-* The system prompt for writing Pickle against `host`. In document mode
+* The system prompt for writing Jigs against `host`. In document mode
 * (the default) every reply is one UI, as a session expects; in chat mode a
-* reply is Markdown with UIs in fenced `pickle` blocks. Everything but the
+* reply is Markdown with UIs in fenced `jigs` blocks. Everything but the
 * output section and the mode's design guidance is the same in both.
 *
 * What stays the same from turn to turn comes first, so a provider can

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "@jigs.design/prompt",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "The system prompt and the repair text, rendered from a host and from diagnostics.",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/yoamomonstruos/pickle.git",
+    "url": "git+https://github.com/yoamomonstruos/jigs.git",
     "directory": "packages/prompt"
   },
   "type": "module",
@@ -25,9 +25,9 @@
     "access": "public"
   },
   "dependencies": {
-    "@jigs.design/compiler": "0.1.1",
-    "@jigs.design/host": "0.1.1",
-    "@jigs.design/runtime": "0.1.1"
+    "@jigs.design/compiler": "0.1.2",
+    "@jigs.design/host": "0.1.2",
+    "@jigs.design/runtime": "0.1.2"
   },
   "peerDependencies": {
     "zod": "^4.0.0"