@bendyline/gilde 0.2.4 → 0.2.6

package/data/craftbook-templates/he/hero-image/versions/1.0.5/craftbook.json

@@ -0,0 +1,287 @@
+{
+  "id": "hero-image",
+  "name": "Marketing Hero Image",
+  "description": "Create a single high-impact marketing hero image from a brief and place it into a working hero section. Lock the brief FIRST — aspect ratio, subject, mood, palette, focal point, and crucially the safe zone where headline and CTA text will overlay — because a beautiful hero that has no room for copy (or whose focal point sits under the button) is useless. Then generate the image to the brief and place it behind real overlaid text to prove it works. Covers hero banners, marketing imagery, landing-page art, website headers, and key visuals.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Hero brief (visual-designer) — lock ratio, subject, mood, palette, focal point, text safe-zone → gated on artifact `{{workPath}}/brief.md` (markdown-notes)\n2. Generate the hero (image-generator) — render the hero image to the brief → gated on `assets` (image-set)\n3. Place in a hero section (developer) — build index.html with the hero behind real overlaid text → gated on `index.html` (html-marketing-site)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "brief",
+  "triggers": [
+    "make a hero image",
+    "marketing banner",
+    "landing page hero",
+    "website header image",
+    "key visual"
+  ],
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "brief",
+      "name": "Hero brief",
+      "description": "lock ratio, subject, mood, palette, focal point, text safe-zone",
+      "prompt": "1) Decide the aspect ratio and target use (e.g. 16:9 full-bleed web hero). 2) Lock the subject and scene, the mood/style, and the palette (hex) so the image will harmonize with the brand. 3) Define the FOCAL POINT and, critically, the TEXT SAFE ZONE — which third of the frame stays low-contrast/empty so an overlaid headline + CTA remains readable. 4) Note the headline and CTA copy that will sit on it (even placeholder) so placement is concrete. 5) Write an acceptance-criteria checklist: 'aspect ratio is <X>', 'focal point is off the text safe zone', 'palette matches <hex>', 'overlaid headline + CTA are readable against the image', 'image is delivered at usable resolution'. 6) Record brief + checklist via write_task_note AND to {{workPath}}/brief.md. No image yet.\n\nThe deliverable `{{workPath}}/brief.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "visual-designer",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "advanceWhen": {
+        "file": "{{workPath}}/brief.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/brief.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/brief.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "brief",
+        "maxAttempts": 3
+      },
+      "next": "generate"
+    },
+    {
+      "id": "generate",
+      "name": "Generate the hero",
+      "description": "render the hero image to the brief",
+      "prompt": "1) Read brief.md. 2) Using the image-generation capability (or a tasteful CSS/SVG composition if no image model is available), produce the hero at the locked aspect ratio and palette. 3) Compose so the focal point lands OUTSIDE the declared text safe zone and that zone stays calm enough for overlaid copy. 4) Match the mood and avoid clutter near where text goes. 5) Save it to assets/ (e.g. assets/hero.png or hero.svg) at usable resolution. 6) Generate at least one alternate framing if quick, so placement has options. Good looks like: a striking image with obvious clear space for the headline.",
+      "suggestedRole": "image-generator",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web"
+        ],
+        "outputMedium": "workspace"
+      },
+      "advanceWhen": {
+        "file": "assets",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "fileCount",
+            "ext": [
+              "png",
+              "jpg",
+              "jpeg",
+              "svg",
+              "webp"
+            ],
+            "min": 3,
+            "dir": "assets"
+          }
+        ],
+        "onReject": "generate",
+        "maxAttempts": 3
+      },
+      "next": "place"
+    },
+    {
+      "id": "place",
+      "name": "Place in a hero section",
+      "description": "build index.html with the hero behind real overlaid text",
+      "prompt": "1) Build a single index.html hero section that uses the generated image as a full-bleed background (object-fit: cover or background-size: cover) at the locked aspect ratio. 2) Overlay the real headline and CTA button positioned within the safe zone, with a subtle scrim/gradient ONLY if needed for contrast. 3) Make it responsive — the focal point must survive a mobile crop. 4) Reference the real assets/ file (relative path). 5) On a loop-back, fix only named gaps (unreadable text, focal point clipped, wrong ratio). 6) write_task_note the page path and image used. Good looks like: a hero you could ship, with crisp, readable copy over the art.",
+      "suggestedRole": "developer",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web"
+        ],
+        "outputMedium": "workspace",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "consumes": [
+        {
+          "file": "assets"
+        }
+      ],
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 1200
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          },
+          {
+            "name": "checkCssMinBytes",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html",
+              "minBytes": 600
+            }
+          }
+        ],
+        "onReject": "place",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "1) Confirm assets/ contains the hero image (PASS/FAIL). 2) Open index.html and verify the image renders full-bleed at the locked aspect ratio. 3) The decisive check: is the overlaid headline + CTA clearly READABLE against the image and is the focal point clear of the text (PASS/FAIL)? 4) Resize to a narrow viewport — does it survive the mobile crop? 5) Confirm the palette matches the brief. 6) Write PASS/FAIL per criterion. Unreadable/clashing text → loop back to place; bad image/focal point → note it for generate.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"place\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      },
+      "consumes": [
+        {
+          "file": "index.html"
+        }
+      ],
+      "next": "place"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      },
+      "terminal": true
+    }
+  ],
+  "version": "1.0.5",
+  "releasedAt": "2026-10-19T00:00:00Z",
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/he/hero-image/versions/1.0.5/test.json

@@ -0,0 +1,94 @@
+{
+  "schemaVersion": 1,
+  "mode": "workflow",
+  "title": "Marketing Hero Image workflow processability",
+  "objective": "Prove that a medium local model can parse and execute the Marketing Hero Image craftbook, satisfy its declared runtime gates, and reach a terminal step using only local fixtures.",
+  "tags": [
+    "media"
+  ],
+  "prompt": "Use the `hero-image` (Marketing Hero Image) craftbook for this self-contained local evaluation. Open `source/craftbook-eval-brief.md` first, then follow the craftbook's actual steps and gates through its terminal step. Complete this request: Create a single high-impact marketing hero image from a brief and place it into a working hero section. Lock the brief FIRST — aspect ratio, subject, mood, palette, focal point, and crucially the safe zone where headline and CTA text will overlay — because a beautiful hero that has no room for copy (or whose focal point sits under the button) is useless. Then generate the image to the brief and place it behind real overlaid text to prove it works. Covers hero banners, marketing imagery, landing-page art, website headers, and key visuals.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Hero brief (visual-designer) — lock ratio, subject, mood, palette, focal point, text safe-zone → gated on artifact `{{workPath}}/brief.md` (markdown-notes)\n2. Generate the hero (image-generator) — render the hero image to the brief → gated on `assets` (image-set)\n3. Place in a hero section (developer) — build index.html with the hero behind real overlaid text → gated on `index.html` (html-marketing-site)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n Produce `brief.md` in this task's artifact working folder, `assets`, `index.html`. Use only seeded project files and installed local simulators. Do not call a real external service, fetch live data, or claim an external side effect occurred; an explicit dry-run record is the correct result when a dependency is unavailable.",
+  "setup": {
+    "projectName": "Marketing Hero Image Workflow Eval",
+    "about": "A hermetic workflow evaluation for the Marketing Hero Image craftbook. No live dependency or external network is authorized.",
+    "missionObjectives": "Run the Marketing Hero Image craftbook end to end, use the local evaluation brief and fixtures as truth, produce its declared outputs, and reach a terminal step without fabricating external effects.",
+    "managedWorkspaceWritePolicy": "allow",
+    "files": [
+      {
+        "path": "source/craftbook-eval-brief.md",
+        "content": "# Marketing Hero Image — local evaluation brief\n\nThis is a hermetic processability evaluation of the `hero-image` craftbook.\nDo not contact real services, use real credentials, or fetch live data. Treat\nthe project fixtures and installed local simulators as authoritative. If a\ndependency is intentionally unavailable, document an honest dry run instead\nof claiming a real side effect.\n\n## Request\n\nCreate a single high-impact marketing hero image from a brief and place it into a working hero section. Lock the brief FIRST — aspect ratio, subject, mood, palette, focal point, and crucially the safe zone where headline and CTA text will overlay — because a beautiful hero that has no room for copy (or whose focal point sits under the button) is useless. Then generate the image to the brief and place it behind real overlaid text to prove it works. Covers hero banners, marketing imagery, landing-page art, website headers, and key visuals.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Hero brief (visual-designer) — lock ratio, subject, mood, palette, focal point, text safe-zone → gated on artifact `{{workPath}}/brief.md` (markdown-notes)\n2. Generate the hero (image-generator) — render the hero image to the brief → gated on `assets` (image-set)\n3. Place in a hero section (developer) — build index.html with the hero behind real overlaid text → gated on `index.html` (html-marketing-site)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n\n\n## Required workflow\n\n1. Hero brief\n2. Generate the hero\n3. Place in a hero section\n4. Evaluate\n5. Finish (terminal)\n\n## Declared outputs\n\n- `brief.md` in this task's artifact working folder\n- `assets`\n- `index.html`\n"
+      },
+      {
+        "path": "source/brief.md",
+        "content": "# Marketing Hero Image Eval Brief\n\nClient: Boreal Desk, a home-office accessories company.\nAudience: operations leads who need an artifact they can use this week.\n\nFixed source facts for grounding:\n- The returns desk pilot covered 18 SKUs.\n- Median first response improved from 18 hours to 6 hours.\n- Preventable refund leakage fell from 14.2% to 8.9%.\n- The top unresolved complaint is status silence after photo submission.\n- Required next actions are automated status emails, barcode-exception training, and a weekly Finance exception export.\n\nUse these facts when the task asks for prose, analysis, copy, UI content, or test data. Do not use live web services, real credentials, or current outside data.\n\nCraftbook under test: hero-image - Marketing Hero Image.\n"
+      },
+      {
+        "path": "source/media-index.csv",
+        "content": "filename,type,duration_or_size,notes\npilot-interview.wav,audio,00:02:15,mentions response time and status silence\nreturns-desk.png,image,1600x900,shows intake form and photo evidence step\nlaunch-clip.mp4,video,00:01:05,shows barcode exception handling\n"
+      }
+    ],
+    "worker": {
+      "name": "Craftbook Runner",
+      "role": "Workflow Operator",
+      "about": "Execute the assigned craftbook exactly. Read local fixtures, satisfy each runtime gate, record honest dry-run evidence for unavailable dependencies, and continue until a terminal step is active or the task is complete."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The attributed hero-image task satisfied its own gates, produced its declared outputs, and reached a terminal step without using external services.",
+    "deliverables": [
+      {
+        "path": "{{task.dir}}/brief.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 120
+      },
+      {
+        "path": "assets",
+        "kind": "generic-file",
+        "minBytes": 1
+      },
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 1200
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    }
+  },
+  "rubric": {
+    "artifact": {
+      "path": "{{task.dir}}/brief.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "workflow fidelity",
+        "description": "The result reflects the named craftbook sequence and its declared acceptance gates rather than a freehand substitute."
+      },
+      {
+        "name": "usefulness",
+        "description": "The deliverable is coherent, actionable, and suitable for the craftbook purpose stated in the local brief."
+      }
+    ],
+    "contextNote": "Advisory only. Deterministic pass/fail comes from the craftbook runtime gates, deliverable existence, attribution, and terminal progress."
+  },
+  "qualityFocus": [
+    "real hero-image craftbook task attribution",
+    "declared runtime gate satisfaction",
+    "terminal workflow progress",
+    "offline fixture and simulator discipline"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "hero-image-media-fixtures",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local media index replacing real audio, video, image generation, and external media metadata services."
+      }
+    ]
+  }
+}

package/data/craftbook-templates/ho/holiday-card-run/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "write-publish",
-  "accents": [
-    "muted terracotta",
-    "muted indigo",
-    "sage"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a folded greeting card with a small evergreen tree on it",
   "sourceSummary": "Make the December run a pleasure instead of a panic: sweep the address list while there is still time to fix it, settle the card message, and produce the print-ready card and the address sheet in one sitting.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s28",
+  "cell": 8,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/ho/hotfix-flow/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "plan-coordinate",
-  "accents": [
-    "ochre",
-    "sage",
-    "muted indigo"
-  ],
-  "sourceSummary": "Drive an expedited production hotfix from red to green: reproduce the live defect with a failing test, apply the smallest safe fix that makes it pass without scope-creeping into a refactor, and verify the fix plus a clean regression check before it ships out-of-band.",
-  "styleReference": "accessibility-audit-1910"
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a pipe with a bandage patch wrapped over a crack",
+  "sourceSummary": "Stop a live failure with the smallest change that fixes it at the real site: reproduce with the least machinery that demonstrates the failure, patch minimally with the proper repair recorded as follow-up, validate with a rollback path, and pass an enforced review of the blast radius.",
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s16",
+  "cell": 3,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/ht/html-arcade-game/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "design-media",
-  "accents": [
-    "muted terracotta",
-    "sage",
-    "muted indigo"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "an arcade joystick with a round ball top and one round button",
   "sourceSummary": "Build a playable single-file HTML/canvas arcade game (shooter, runner, dodger, etc.).",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s09",
+  "cell": 1,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/ht/html-puzzle-game/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "design-media",
-  "accents": [
-    "muted terracotta",
-    "sage",
-    "muted indigo"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a square sliding-tile puzzle frame with one empty slot",
   "sourceSummary": "Build a single-file HTML logic or puzzle game such as a match-3, sliding tile, Sokoban, 2048, minesweeper, or sudoku.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s09",
+  "cell": 2,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/ic/icon-pack/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "design-media",
-  "accents": [
-    "muted terracotta",
-    "sage",
-    "muted indigo"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a tidy three-by-three tray of small simple shape tiles",
   "sourceSummary": "Produce a coherent set of UI icons that look like they belong to one family — consistent grid, stroke weight, corner radius, optical sizing, and metaphor language — from a named list of concepts.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s20",
+  "cell": 7,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }